[Bugs] [Bug 1263090] 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=1263090

            Bug ID: 1263090
           Summary: glusterd: add brick command should re-use the port for
                    listening which is freed by remove-brick.
           Product: Red Hat Gluster Storage
           Version: 3.1
         Component: glusterfs
     Sub Component: core
          Assignee: rhs-bugs at redhat.com
          Reporter: ggarg at redhat.com
        QA Contact: annair at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com,
                    sasundar at redhat.com
        Depends On: 1221623



+++ This bug was initially created as a clone of Bug #1221623 +++

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.

--- Additional comment from Anand Avati on 2015-05-14 09:06:27 EDT ---

REVIEW: http://review.gluster.org/10785 (glusterd: newly added brick should use
the port which is freed by remove-brick) posted (#1) for review on master by
Gaurav Kumar Garg (ggarg at redhat.com)

--- Additional comment from Anand Avati on 2015-05-15 09:54:15 EDT ---

REVIEW: http://review.gluster.org/10785 (glusterd: newly added brick should use
the port which is freed by remove-brick) posted (#2) for review on master by
Gaurav Kumar Garg (ggarg at redhat.com)

--- Additional comment from Anand Avati on 2015-08-11 09:13:37 EDT ---

REVIEW: http://review.gluster.org/10785 (glusterd: newly added brick should use
the port which is freed by remove-brick) posted (#3) for review on master by
Gaurav Kumar Garg (ggarg at redhat.com)

--- Additional comment from Vijay Bellur on 2015-09-11 04:35:05 EDT ---

REVIEW: http://review.gluster.org/10785 (glusterd: newly added brick should use
the port which is freed by remove-brick) posted (#4) for review on master by
Gaurav Kumar Garg (ggarg at redhat.com)


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1221623
[Bug 1221623] glusterd: add brick command should re-use the port for
listening which is freed by remove-brick.
-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=qdFFxKmJ69&a=cc_unsubscribe