[Bugs] [Bug 1221623] New: glusterd: add brick command should re-use the port for listening which is freed by remove-brick.

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1221623

            Bug ID: 1221623
           Summary: glusterd: add brick command should re-use the port for
                    listening which is freed by remove-brick.
           Product: GlusterFS
           Version: mainline
         Component: glusterd
          Assignee: bugs at gluster.org
          Reporter: ggarg at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Description of problem:

If volume having 4 brick then listening port for that brick will be
49152-49155.
if user perform any remove-brick operation then one of the brick port from
49152-49155 will free (port on which user performing remove brick operation).
after this if user perform add-brick operation then glusterd will assign port
after 49155, it is not reusing the port which is freed by remove-brick
operation.


Version-Release number of selected component (if applicable):

Mainline

How reproducible:

Always 

Steps to Reproduce:
1. Create and start volume having 2 or more than 2 brick.
2. perform remove-brick operation on any brick.
3. execute gluster volume status command.
3. perform add-brick operation.
4. execute gluster volume status command.


you will see that the brick which you have recently added will use new port.



Actual results:

 brick which you have recently added will use new port

Expected results:

we should re-use the port which is free by remove-brick command.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.