[Bugs] [Bug 1547068] Bricks getting assigned to different pids depending on whether brick path is IP or hostname based

[bugzilla at redhat.com]

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



--- Comment #1 from Atin Mukherjee <amukherj at redhat.com> ---
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):
mainline

How reproducible:
always

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.

Actual results:
===============
For the two volumes, two different pids are getting assigned.

Expected results:
=================
As brick-mux is enabled, the two volumes should get the same brick process.

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