Red Hat Bugzilla – Bug 1461792
lk fop succeeds even when lock is not acquired on at least quorum number of bricks
Last modified: 2017-09-05 13:34:18 EDT
Description of problem:
When testing gluster-block we are seeing that even when just one of the bricks is up lk fop is succeeding. This can lead to problems. Fix AFR behavior where lk fop considers quorum count to decide if lk fop succeeds or not.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
REVIEW: https://review.gluster.org/17524 (cluster/afr: Implement quorum for lk fop) posted (#3) for review on master by Pranith Kumar Karampuri (email@example.com)
REVIEW: https://review.gluster.org/17524 (cluster/afr: Implement quorum for lk fop) posted (#4) for review on master by Pranith Kumar Karampuri (firstname.lastname@example.org)
COMMIT: https://review.gluster.org/17524 committed in master by Pranith Kumar Karampuri (email@example.com)
Author: Pranith Kumar K <firstname.lastname@example.org>
Date: Mon Jun 12 22:06:18 2017 +0530
cluster/afr: Implement quorum for lk fop
At the moment when we have replica 3 or arbiter setup, even when
lk succeeds on just one brick we give success to application which
Consider quorum-number of successes as success when quorum is enabled.
Signed-off-by: Pranith Kumar K <email@example.com>
Smoke: Gluster Build System <firstname.lastname@example.org>
NetBSD-regression: NetBSD Build System <email@example.com>
CentOS-regression: Gluster Build System <firstname.lastname@example.org>
Reviewed-by: Ravishankar N <email@example.com>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.12.0, please open a new bug report.
glusterfs-3.12.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.