Bug 764296 (GLUSTER-2564) - replace brick fails on master
Summary: replace brick fails on master
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-2564
Product: GlusterFS
Classification: Community
Component: glusterd
Version: 3.1-alpha
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Pranith Kumar K
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-20 08:52 UTC by Pranith Kumar K
Modified: 2011-06-10 12:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Pranith Kumar K 2011-03-20 08:52:39 UTC 
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 10:01:38 UTC 
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 09:10:14 UTC 
Replace brick succeeded from the master.
Note You need to log in before you can comment on or make changes to this bug.