Section Number and Name:
14.6. Disaster Recovery
Describe the issue and suggestion:
Performing a Failover and Failback:
When original master comes back, it will have existing geo-rep session which would become Online. Hence the first step should be to stop the existing geo-rep session:
1. Stop the existing geo-rep session from original master to orginal slave using:
gluster volume geo-replication ORIGINAL_MASTER_VOL ORIGINAL_SLAVE_HOST::ORIGINAL_SLAVE_VOL stop <force>
2. Mention specifically to use force.
Create a new geo-replication session with the original slave as the new master, and the original master as the new slave with force option. For more information on setting and creating geo-replication session, see Section 188.8.131.52, “Setting Up your Environment for Geo-replication Session”.
I have updated the documentation based on the bug description.
Link to the latest doc :http://jenkinscat.gsslab.pnq.redhat.com:8080/view/Gluster/job/doc-Red_Hat_Gluster_Storage-3.1.3-Administration_Guide%20%28html-single%29/lastBuild/artifact/tmp/en-US/html-single/index.html#Failover_and_Failback
Documentation changes mentioned in comment 2 looks good to me. Moving the bz to verified state