[Bugs] [Bug 1233151] rm command fails with "Transport end point not connected" during add brick

bugzilla at redhat.com bugzilla at redhat.com
Thu Jun 18 11:06:14 UTC 2015


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



--- Comment #1 from Sakshi <sabansal at redhat.com> ---
The main issue is that, irrespective of whether the newly added brick received
a port or not the volume file change happens. So consider a scenario where the
newly added brick requested for a new port but has not received a port, however
volume file change happens. Hence fops are now sent to the newly added brick as
well. The newly added brick still does not have a port yet hence the fop fails
on that brick with "Transpor endpoint not connected". Also instead of glusterd
creating and notifying the volfile immediately, it can notify the client once
the brick is added. 

The fix would be to notify volume file change only after a new brick is added
and has gets a port.

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


More information about the Bugs mailing list