diff options
| author | Pranith Kumar K <pkarampu@redhat.com> | 2015-05-28 15:33:18 +0530 |
|---|---|---|
| committer | Xavier Hernandez <xhernandez@datalab.es> | 2015-06-23 02:13:40 -0700 |
| commit | 653d3c1406e372aabcf694bfead2d695f84ee0f8 (patch) | |
| tree | 44f8318978f2ca57629e627a061c661d5e8047a9 /xlators/cluster/dht/src/dht-linkfile.c | |
| parent | e8847bd0ba03616bf80f242fda22e104ff2ea0e3 (diff) | |
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@redhat.com>
Reviewed-on: http://review.gluster.org/11003
Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Tested-by: NetBSD Build System <jenkins@build.gluster.org>
Diffstat (limited to 'xlators/cluster/dht/src/dht-linkfile.c')
0 files changed, 0 insertions, 0 deletions