Hi
a) documentation says "All operations that do not modify the file
or directory are sent to all the subvolumes and the first successful
reply is returned to the application", why is blocking then ?
it's suposed that the reply from the non blocked server will
come first and nothing will block, but clients are blocking on
a simple ls operation
The calls (as you have seen in the logs as well) which are hanging are
lookup calls, which have to be sent to all subvolumes to ensure all
the copies are in sync.
ok, then the most simple fix will be to add a timeout for lookup
calls, altough i will prefer to optionally also have the first reply
to the lookup being sent to the application and then wait in the
background for the other ones so gluster can keep files in sync,
this will eliminate this hang and also make the system more responsive.
BTW, will switching off some of the self heal options in the client
make glusterfs use only the first reply received to the lookup call ?
--
Thanx & best regards ...
----------------------------------------------------------------
David Saez Padros http://www.ols.es
On-Line Services 2000 S.L. telf +34 902 50 29 75
----------------------------------------------------------------
_______________________________________________
Gluster-users mailing list
[email protected]
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
