Description of problem:
With brick multiplexing enabled, bricks getting assigned to different pids depending on whether brick path is IP or hostname based.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1) Enable brick-mux.
2) Create a volume with server hostnames as below,
gluster v create hostname replica 3 <hostname1:/brickpath> <hostname2:/brickpath> <hostname3:/brickpath> ...
3) Start the volume and make a note of glusterfsd pid
4) Now, create a new volume with server IP as below,
gluster v create IP replica 3 <IP1:/brickpath> <IP2:/brickpath> <IP3:/brickpath> ...
5) Start the volume and make a note of glusterfsd pid.
For the two volumes, two different pids are getting assigned.
As brick-mux is enabled, the two volumes should get the same brick process.
REVIEW: https://review.gluster.org/19601 (glusterd: compare uuid instead of hostname while finding compatible brick) posted (#1) for review on master by Atin Mukherjee
COMMIT: https://review.gluster.org/19601 committed in master by "Amar Tumballi" <email@example.com> with a commit message- glusterd: compare uuid instead of hostname while finding compatible brick
If the above is not done, bricks created with different IP/hostname will
not be compatible with brick multiplexing.
Signed-off-by: Atin Mukherjee <firstname.lastname@example.org>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-v4.1.0, please open a new bug report.
glusterfs-v4.1.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.