hi,
When glusterfs mount process is coming up all cluster xlators wait
for at least one event from all the children before propagating the
status upwards. Sometimes client xlator takes upto 2 minutes to
propogate this
event(https://bugzilla.redhat.com/show_bug.cgi?id=1054694#c0) Due to
I agree that a generic solution for all cluster xlators would be good.
Only question I have is whether parallel notifications are specially
handled somewhere.
For example, if client xlator sends EC_CHILD_DOWN after a timeout, it's
possible that an immediate EC_CHILD_UP is sent if the brick
Pranith,
I understand the bug and a more generic layer solution would be
desirable and apt, rather than repeating things at each xlator.
However, I am always confused about notifications and its processing, so
cannot state with conviction that this is fine and will work elegantly.
Will
On 07/02/2015 07:04 PM, Pranith Kumar Karampuri wrote:
hi,
When glusterfs mount process is coming up all cluster xlators wait
for at least one event from all the children before propagating the
status upwards. Sometimes client xlator takes upto 2 minutes to
propogate this
