Description of problem:When node goes down and come back in master cluster, that particular session will be defunct. This is actually result not bringing back the monitor process when the node come back . Version-Release number of selected component (if applicable):glusterfs-3.4.0.33rhs-1.el6rhs.x86_64 How reproducible: happens everytime, Steps to Reproduce: 1.create and start a geo-rep relationship between master and slave. 2.bring down one of the node from master cluster and bring it back 3.Check the geo-rep status. Actual results: Particular geo-rep session goes defunct Expected results: When node goes down and comes back, it should be restarted properly Additional info:
Actually for me it went to "faulty" state also. Out of the two times I did this test session went to "faulty" once and "defunct" other time.
*** Bug 1022614 has been marked as a duplicate of this bug. ***
Patch sent upstream at http://review.gluster.org/6130
verified on glusterfs-3.4.0.37rhs-1
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. http://rhn.redhat.com/errata/RHBA-2013-1769.html