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 leave others to chime in with the same.
Shyam
On 07/02/2015 09:34 AM, 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
event(https://bugzilla.redhat.com/show_bug.cgi?id=1054694#c0) Due to
this xavi implemented timer in ec notify where we treat a child as down
if it doesn't come up in 10 seconds. Similar patch went up for review
@http://review.gluster.org/#/c/11113 for afr. Kritika raised an
interesting point in the review that all cluster xlators need to have
this logic for the mount to not hang, and the correct place to fix it
would be client xlator itself. i.e. add the timer logic in client
xlator. Which seems like a better approach. I just want to take inputs
from everyone before we go ahead in that direction.
i.e. on PARENT_UP in client xlator it will start a timer and if no rpc
notification is received in that timeout it treats the client xlator as
down.
Pranith
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
