Bug 764296 (GLUSTER-2564)

Summary: replace brick fails on master
Product: [Community] GlusterFS Reporter: Pranith Kumar K <pkarampu>
Component: glusterdAssignee: Pranith Kumar K <pkarampu>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3.1-alphaCC: gluster-bugs, rabhat
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:

Description Pranith Kumar K 2011-03-20 04:52:39 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.

Pranith.
Comment 1 Vijay Bellur 2011-03-20 06:01:38 EDT
PATCH: http://patches.gluster.com/patch/6521 in master (mgmt/glusterd: Dont reset the port on brick stop)
Comment 2 Raghavendra Bhat 2011-06-10 05:10:14 EDT
Replace brick succeeded from the master.