Bug 1805097 - Changes to self-heal logic w.r.t. detecting metadata split-brains
Summary: Changes to self-heal logic w.r.t. detecting metadata split-brains
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: replicate
Version: 6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Karthik U S
QA Contact:
URL:
Whiteboard:
Depends On: 1717819
Blocks: 1806846
TreeView+ depends on / blocked
 
Reported: 2020-02-20 09:06 UTC by Karthik U S
Modified: 2020-03-02 07:57 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1717819
Environment:
Last Closed: 2020-02-25 07:07:48 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 24155 0 None Merged Cluster/afr: Don't treat all bricks having metadata pending as split-brain 2020-02-25 07:07:47 UTC

Description Karthik U S 2020-02-20 09:06:17 UTC
+++ This bug was initially created as a clone of Bug #1717819 +++

Description of problem:

We currently don't have a roll-back/undoing of post-ops if quorum is not met. Though the FOP is still unwound with failure, the xattrs remain on the disk. Due to these partial post-ops and partial heals (healing only when 2 bricks are up), we can end up in metadata split-brain purely from the afr xattrs point of view i.e each brick is blamed by atleast one of the others for metadata. These scenarios are hit when there is frequent connect/disconnect of the client/shd to the bricks.

Comment 1 Worker Ant 2020-02-20 09:19:46 UTC
REVIEW: https://review.gluster.org/24155 (Cluster/afr: Don't treat all bricks having metadata pending as split-brain) posted (#1) for review on release-6 by Karthik U S

Comment 2 Worker Ant 2020-02-25 07:07:48 UTC
REVIEW: https://review.gluster.org/24155 (Cluster/afr: Don't treat all bricks having metadata pending as split-brain) merged (#2) on release-6 by hari gowtham


Note You need to log in before you can comment on or make changes to this bug.