diff options
| author | Ravishankar N <ravishankar@redhat.com> | 2015-11-18 08:30:48 +0530 |
|---|---|---|
| committer | Jeff Darcy <jdarcy@redhat.com> | 2015-11-18 11:34:37 -0800 |
| commit | 4b8249a35aba28621ed59155ab27fb5bfa5f113f (patch) | |
| tree | 9522217dd2ece5d244efd563a2bdaa31c8d56af4 /xlators/mount/fuse | |
| parent | 5bb3c521431cc27b2826acd889bffb2f90ae7f73 (diff) | |
afr: Drop compatibility lock for data self-heal
In glusterfs 3.4 and older, AFR did not take locks in self-heal domain
during data self-heal. So this compat lock in data domain was added to prevent
older clients from trying to heal a file while an existing self-heal was going
on by a newer client. But the side effect was that all appending writes (which
take full locks in data domain) from mounts would be stalled until self-heal
was complete.
Since glusterfs 3.4 is not supported anymore, remove the compat lock.
Change-Id: I31c8e4d7f3364f769a14eec295154e3c40d9f78e
BUG: 1283032
Signed-off-by: Ravishankar N <ravishankar@redhat.com>
Reviewed-on: http://review.gluster.org/12602
Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
Tested-by: NetBSD Build System <jenkins@build.gluster.org>
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Diffstat (limited to 'xlators/mount/fuse')
0 files changed, 0 insertions, 0 deletions