[Bugs] [Bug 1243642] New: GF_CONTENT_KEY should not be handled unless we are sure no other operations are in progress

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1243642

            Bug ID: 1243642
           Summary: GF_CONTENT_KEY should not be handled unless we are
                    sure no other operations are in progress
           Product: GlusterFS
           Version: 3.7.3
         Component: disperse
          Assignee: bugs at gluster.org
          Reporter: pkarampu at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com
        Depends On: 1226279



+++ This bug was initially created as a clone of Bug #1226279 +++

Description of problem:
GF_CONTENT_KEY aggregation requires that the fragments on the bricks belong to
same data i.e. no operations are modifying the content while lookup is
performed on it. The only way to know it is to get at least ec->fragments+1
number of responses and see that two different sets of ec->fragments number of
fragments give same data. But at the moment we feel that this slows down
ec-lookup. So removing handling of this for now.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Anand Avati on 2015-05-29 07:21:31 EDT ---

REVIEW: http://review.gluster.org/11003 (cluster/ec: Do not handle
GF_CONTENT_KEY) posted (#1) for review on master by Pranith Kumar Karampuri
(pkarampu at redhat.com)

--- Additional comment from Anand Avati on 2015-06-03 22:46:15 EDT ---

REVIEW: http://review.gluster.org/11003 (cluster/ec: Do not handle
GF_CONTENT_KEY) posted (#2) for review on master by Pranith Kumar Karampuri
(pkarampu at redhat.com)

--- Additional comment from Anand Avati on 2015-06-23 05:13:43 EDT ---

COMMIT: http://review.gluster.org/11003 committed in master by Xavier Hernandez
(xhernandez at datalab.es) 
------
commit 653d3c1406e372aabcf694bfead2d695f84ee0f8
Author: Pranith Kumar K <pkarampu at redhat.com>
Date:   Thu May 28 15:33:18 2015 +0530

    cluster/ec: Do not handle GF_CONTENT_KEY

    GF_CONTENT_KEY aggregation requires that the fragments on the bricks belong
to
    same data i.e. no operations are modifying the content while lookup is
    performed on it. The only way to know it is to get at least ec->fragments+1
    number of responses and see that two different sets of ec->fragments number
of
    fragments give same data. But at the moment we feel that this slows down
    ec-lookup. So removing handling of this for now.

    Change-Id: I2da5087f1311d5cdde999062607b143b48c17713
    BUG: 1226279
    Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
    Reviewed-on: http://review.gluster.org/11003
    Reviewed-by: Xavier Hernandez <xhernandez at datalab.es>
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Tested-by: NetBSD Build System <jenkins at build.gluster.org>


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1226279
[Bug 1226279] GF_CONTENT_KEY should not be handled unless we are sure no
other operations are in progress
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.