|Summary:||[RFE] Need a way to resolve gfid split brains|
|Product:||Red Hat Gluster Storage||Reporter:||Nag Pavan Chilakam <nchilaka>|
|Component:||replicate||Assignee:||Karthik U S <ksubrahm>|
|Status:||CLOSED ERRATA||QA Contact:||Vijay Avuthu <vavuthu>|
|Version:||rhgs-3.2||CC:||amukherj, ksubrahm, ravishankar, rhinduja, rhs-bugs, sheggodu, srmukher, storage-qa-internal|
|Target Milestone:||---||Keywords:||FutureFeature, RFE, ZStream|
|Target Release:||RHGS 3.4.0|
|Fixed In Version:||glusterfs-3.12.2-1||Doc Type:||Enhancement|
WIth this release, GFID split-brains can be resolved from the CLI using any of the policies: choice of brick, mtime or size. You need to provide the absolute path of the file which needs GFID heal.
|:||1459530 1531934 (view as bug list)||Environment:|
|Last Closed:||2018-09-04 06:29:55 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
|Bug Depends On:||1459530|
|Bug Blocks:||1503132, 1531934|
Description Nag Pavan Chilakam 2017-01-17 12:44:46 UTC
Description of problem: ===================== Currently there is no way for the admin from CLI to resolve gfid split brain based on some policy like choice of the brick, mtime or size or a way to retain both files The only option is for the admin to work on the files from backend ie bricks We should be having a way to resolve gfid split brain Version-Release number of selected component (if applicable): ============ 3.8.4-11
Comment 8 Vijay Avuthu 2018-03-13 12:29:13 UTC
Update ========= Verified with below scenario's scenario 1: 1) created gfid split-brain 2) resolved split-brain using "bigger-file" option 3) wait for heal to complete scenario 2: 1) created gfid split-brain 2) resolved split-brain using "mtime" option 3) wait for heal to complete scenario 3: 1) created gfid split-brain 2) resolved split-brain using "source-brick" option 3) wait for heal to complete Observation: After issuing split-brain command using policy, observed healing is not done immediately. Its taking few minutes to complete healing ( even with single file ) but from back end its clearing the dirty tag immediately.
Comment 9 Karthik U S 2018-03-13 12:50:28 UTC
Once you run this command it will immediately resolve the gfid split-brain but there might be some data heal pending on the entry after this. So you can see the entry in the heal info output until that is cleared by explicitly running the heal or by doing any update operations on the file or the shd kicks in at the regular interval. Once the heal completes the entry will be removed from the heal info.
Comment 10 Vijay Avuthu 2018-03-13 13:27:37 UTC
Changing status to Verified. See #comment 8 for more details.
Comment 11 Srijita Mukherjee 2018-09-03 15:35:21 UTC
Have updated the doc text. Kindly review and confirm.
Comment 12 Karthik U S 2018-09-03 16:04:46 UTC
Comment 13 errata-xmlrpc 2018-09-04 06:29:55 UTC
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/RHSA-2018:2607