Bug 763205 (GLUSTER-1473) - reuse the ports while starting 'glusterfsd'
Summary: reuse the ports while starting 'glusterfsd'
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-1473
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Amar Tumballi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-29 12:25 UTC by Amar Tumballi
Modified: 2015-12-01 16:45 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:
Embargoed:


Attachments (Terms of Use)

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)


Note You need to log in before you can comment on or make changes to this bug.