[Bugs] [Bug 1226279] 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=1226279

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



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:

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.