Description of problem: ------------------- if a volume is mounted using a server IP, and if the server is being detached from the trusted pool, it can lead to data inconsistencies as explained in BZ#1639566 To avoid this, we must throw a warning prompt, when peer detach is issued , like below: "first make sure that all clients mounted using the node being detached, are remounted using the ip of another server in the trusted pool, to avoid inconsistencies", if you have done that then only proceed{y/n} Version-Release number of selected component (if applicable): ============= mainline
REVIEW: https://review.gluster.org/21572 (glusterd: add a warning/confirmation message in peer detach code path) posted (#1) for review on master by Atin Mukherjee
REVIEW: https://review.gluster.org/21572 (cli: add a warning/confirmation message in peer detach code path) posted (#5) for review on master by Atin Mukherjee
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-6.0, please open a new bug report. glusterfs-6.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] https://lists.gluster.org/pipermail/announce/2019-March/000120.html [2] https://www.gluster.org/pipermail/gluster-users/