Description of problem: Right now geo-rep stop succeeds when there is a node/glusterd down. Running geo-rep stop will stop all the gsync processes in the nodes which are up, but when the node which was down comes back online, the gsync in that node would still be running. geo-rep stop force needs to be run again to stop the process. Version-Release number of selected component (if applicable): glusterfs-3.4.0.32rhs-1.el6rhs.x86_64 How reproducible: Always Steps to Reproduce: 1. Create and start a geo-rep session between 2 clusters 2. Now bring down a node (or kill glusterd in that node) 3. Run geo-rep stop on the master node. Actual results: [root@spitfire ]# gluster v geo master falcon::slave stop Stopping geo-replication session between master & falcon::slave has been successful But when the node which was down comes back online, [root@spitfire ]# gluster v geo master falcon::slave status NODE MASTER SLAVE HEALTH UPTIME ---------------------------------------------------------------------------- spitfire.blr.redhat.com master falcon::slave Stopped N/A mustang.blr.redhat.com master falcon::slave Stopped N/A harrier.blr.redhat.com master falcon::slave Stable 01:52:26 typhoon.blr.redhat.com master falcon::slave Stopped N/A Expected results: Stop should fail or warn in case when the node is down. Additional info:
Somehow this got raised twice in my browser. Closing it as duplicate *** This bug has been marked as a duplicate of bug 1005478 ***