Bug 763205 (GLUSTER-1473)

Summary: reuse the ports while starting 'glusterfsd'
Product: [Community] GlusterFS Reporter: Amar Tumballi <amarts>
Component: glusterdAssignee: Amar Tumballi <amarts>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: low    
Version: mainlineCC: gluster-bugs, vraman
Target Milestone: ---   
Target Release: ---   
Hardware: All   
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:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Amar Tumballi 2010-08-29 12:25:44 UTC 
as of now, ports are reused, but there is a chance that after stop/start, same brick may get different port number. This is good if a brick starts in same port as long as same glusterd instance is present. There is no need to keep this brick port info persistent, but surely for one instance of glusterd, brick should be having a port.
Comment 1 Vijay Bellur 2010-08-29 15:37:29 UTC 
PATCH: http://patches.gluster.com/patch/4359 in master (mgmt/glusterd: handle port allocation so ports are reused for same brick)