diff options
| author | Ravishankar N <ravishankar@redhat.com> | 2015-11-18 08:30:48 +0530 |
|---|---|---|
| committer | Vijay Bellur <vbellur@redhat.com> | 2015-11-23 10:59:36 -0800 |
| commit | f46a54326871bed28c64cd5312b250c7c8207e4f (patch) | |
| tree | 85adda5bc0ef1a2209718cc26beb345b176aefde /tests | |
| parent | 164a8dda2cbf10862483e0333ebf7e727fc87f07 (diff) | |
afr: Drop compatibility lock for data self-heal
Backport of http://review.gluster.org/#/c/12602/
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: I20bb2edf7527ce5d8291d13eb8b9149e66e9bcac
BUG: 1283478
Signed-off-by: Ravishankar N <ravishankar@redhat.com>
Reviewed-on: http://review.gluster.org/12653
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Tested-by: NetBSD Build System <jenkins@build.gluster.org>
Reviewed-by: Vijay Bellur <vbellur@redhat.com>
Diffstat (limited to 'tests')
0 files changed, 0 insertions, 0 deletions