Red Hat Bugzilla – Bug 764296
replace brick fails on master
Last modified: 2011-06-10 08:10:14 EDT
Because the stop glusterfs is resetting the port, the restart brick is starting the brick on some other port because of which the client is not connecting.
PATCH: http://patches.gluster.com/patch/6521 in master (mgmt/glusterd: Dont reset the port on brick stop)
Replace brick succeeded from the master.