Red Hat Bugzilla – Bug 1489876
cli must throw a warning to discourage use of x2 volume which will be deprecated
Last modified: 2018-09-20 01:07:57 EDT
Description of problem: rhgs roadmap going forward is to discourage and then deprecate x2 configurations to avoid split brains. we have updated the document, but the same needs to be even seen on cli (ref doc bug#1482352 - Discourage replica 2 configurations ) update cli to warn x2 creations in all below cases: 1)while creating x2 volume 2)while converting distribute only to x2 3)while removing bricks from x3 to convert to x2 4)while adding/removing bricks in x2 configurations Version-Release number of selected component (if applicable): ========== 3.8.4-40 Additional info:
ravi, we need to take this bug for sure in 3.4.0 to be in sync with documentation
Agreed. Karthik's patch https://review.gluster.org/16899 is already merged upstream to address this issue and will automatically make it to 3.4.0. downstream. Here is the sample output: [root@vm4 ~]# gluster v create testvol replica 2 192.168.122.10:/bricks/brick{1..2} force Replica 2 volumes are prone to split-brain. Use Arbiter or Replica 3 to avoid this. See: https://gluster.readthedocs.io/en/latest/Administrator%20Guide/Split%20brain%20and%20ways%20to%20deal%20with%20it/. Do you still want to continue? (y/n) Nag, request you to add this bug to the spreadsheet you created to keep track of the 3.4.0 bugs.
Since patch is there upstream moving to POST state.
Update: =========== Verified with build : glusterfs-server-3.12.2-5.el7rhgs.x86_64 > Able to see warning while creating x2 volume # gluster vol create 12 replica 2 10.70.35.61:/bricks/brick1/b0 10.70.35.174:/bricks/brick1/b1 Replica 2 volumes are prone to split-brain. Use Arbiter or Replica 3 to avoid this. See: http://docs.gluster.org/en/latest/Administrator%20Guide/Split%20brain%20and%20ways%20to%20deal%20with%20it/. Do you still want to continue? (y/n) y volume create: 12: success: please start the volume to access data # > Didn't see any warnings for below scenario's - while converting distribute only to x2 - while removing bricks from x3 to convert to x2 - while adding/removing bricks in x2 configurations Changing status to Verified and will raise new bz for the above scenario's
Have updated the doc text. Kindly review the technical accuracy.
LGTM.
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