[Bugs] [Bug 1760791] New: afr: support split-brain CLI for replica 3
bugzilla at redhat.com
bugzilla at redhat.com
Fri Oct 11 10:42:26 UTC 2019
https://bugzilla.redhat.com/show_bug.cgi?id=1760791
Bug ID: 1760791
Summary: afr: support split-brain CLI for replica 3
Product: GlusterFS
Version: 7
Status: NEW
Component: replicate
Keywords: Triaged
Assignee: bugs at gluster.org
Reporter: ravishankar at redhat.com
CC: bugs at gluster.org
Depends On: 1756938
Blocks: 1759875
Target Milestone: ---
Classification: Community
+++ This bug was initially created as a clone of Bug #1756938 +++
Description of problem:
Ever since we added quorum checks for lookups in afr via commit
bd44d59741bb8c0f5d7a62c5b1094179dd0ce8a4, the split-brain resolution
commands would not work for replica 3 because there would be no
readables for the lookup fop.
The argument was that split-brains do not occur in replica 3 but we do
see (data/metadata) split-brain cases once in a while which indicate that
there are a few bugs/corner cases yet to be discovered and fixed.
Fortunately, commit 8016d51a3bbd410b0b927ed66be50a09574b7982 added
GF_CLIENT_PID_GLFS_HEALD as the pid for all fops made by glfsheal. If we
leverage this and allow lookups when pid is GF_CLIENT_PID_GLFS_HEALD,
split-brain resolution commands will work for replica 3 volumes too.
Attempting a patch which does this.
--- Additional comment from Worker Ant on 2019-09-30 09:15:59 UTC ---
REVIEW: https://review.gluster.org/23502 (afr: support split-brain CLI for
replica 3) posted (#1) for review on master by Ravishankar N
--- Additional comment from Worker Ant on 2019-10-09 06:36:39 UTC ---
REVIEW: https://review.gluster.org/23502 (afr: support split-brain CLI for
replica 3) merged (#5) on master by Krutika Dhananjay
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1756938
[Bug 1756938] afr: support split-brain CLI for replica 3
https://bugzilla.redhat.com/show_bug.cgi?id=1759875
[Bug 1759875] afr: support split-brain CLI for replica 3
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list