Description of problem: Geo-replication session folder doesn't sync to the new node after a peer probe. Why is it necessary? --------------------- Taking a snapshot of the master requires the geo-replication session folder to be present. If the session folder is missing then glusterd assumes that something has went bad, and because of that snapshot create command will fail. Version-Release number of selected component (if applicable): How reproducible: 1/1 Steps to Reproduce: 1) Create a master volume on node1 and slave volume on node2 2) Starte the session between master volume and slave volume. 3) peer probe to a new node (say node3) 4) check /var/lib/glusterd/geo-replication on node3, session folders are missing in newly probed node (node3). Actual results: session folders does not sync after a peer probe. Expected results: Session folders needs to be synced as-well. Additional info:
Have not heard about this in a long time. Will be closing it as WORKSFORME. If anyone finds the issue feel free to reopen. I recommend upgrading to glusterfs-6.x releases or above for trying out these things.