Bug 1260779
| Summary: | Value of `replica.split-brain-status' attribute of a directory in metadata split-brain in a dist-rep volume reads that it is not in split-brain | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Shruti Sampat <ssampat> | |
| Component: | distribute | Assignee: | Mohit Agrawal <moagrawa> | |
| Status: | CLOSED ERRATA | QA Contact: | Prasad Desala <tdesala> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | rhgs-3.1 | CC: | amukherj, asriram, asrivast, moagrawa, nbalacha, pkarampu, rhinduja, rhs-bugs, sankarshan, smohan, storage-qa-internal | |
| Target Milestone: | --- | |||
| Target Release: | RHGS 3.3.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | glusterfs-3.8.4-19 | Doc Type: | Bug Fix | |
| Doc Text: |
The 'getfattr -n replica.split-brain-status <path-to-dir>' command now shows accurate split brain status.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1368312 1375098 1375099 (view as bug list) | Environment: | ||
| Last Closed: | 2017-09-21 04:25:52 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 1448833 | |||
| Bug Blocks: | 1255689, 1368312, 1375098, 1375099, 1417147 | |||
|
Description
Shruti Sampat
2015-09-07 17:40:22 UTC
Hi Pranith, Could you please review the edited doc text and sign off to be included in the Known Issues chapter. Regards, Anjana hi Anjana,
This feature is Anuradha's baby. I changed Needinfo to Anuradha.
Pranith
downstream patch : https://code.engineering.redhat.com/gerrit/#/c/101282/ Verified this BZ on glusterfs version 3.8.4-27.el7rhgs.x86_64. Followed the same steps as in the description, `replica.split-brain-status' attribute of the directory in metadata split-brain now reports that the file is in split-brain. Hence, moving this BZ to Verified. Console outputs: ================ [root@dhcp43-49 ~]# gluster v heal distrep info Brick 10.70.43.49:/bricks/brick0/b0 /bug_1 - Is in split-brain Status: Connected Number of entries: 1 Brick 10.70.43.41:/bricks/brick0/b0 /bug_1 - Is in split-brain Status: Connected Number of entries: 1 Brick 10.70.43.35:/bricks/brick0/b0 Status: Connected Number of entries: 0 Brick 10.70.43.37:/bricks/brick0/b0 Status: Connected Number of entries: 0 Brick 10.70.43.31:/bricks/brick0/b0 Status: Connected Number of entries: 0 Brick 10.70.43.49:/bricks/brick1/b1 Status: Connected Number of entries: 0 Brick 10.70.43.41:/bricks/brick1/b1 Status: Connected Number of entries: 0 Brick 10.70.43.35:/bricks/brick1/b1 Status: Connected Number of entries: 0 Brick 10.70.43.37:/bricks/brick1/b1 Status: Connected Number of entries: 0 Brick 10.70.43.31:/bricks/brick1/b1 Status: Connected Number of entries: 0 Brick 10.70.43.49:/bricks/brick2/b2 /bug_1 - Is in split-brain Status: Connected Number of entries: 1 Brick 10.70.43.41:/bricks/brick2/b2 /bug_1 - Is in split-brain Status: Connected Number of entries: 1 Brick 10.70.43.35:/bricks/brick2/b2 Status: Connected Number of entries: 0 Brick 10.70.43.37:/bricks/brick2/b2 Status: Connected Number of entries: 0 [root@dhcp41-254 fuse]# getfattr -n replica.split-brain-status bug_1/ # file: bug_1/ replica.split-brain-status="data-split-brain:no metadata-split-brain:yes Choices:distrep-client-10,distrep-client-11,distrep-client-0,distrep-client-1" Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2774 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2774 |