You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 21, 2021. It is now read-only.
As we know, the timeou passed to zk.Connect() is not necessarily to be the final one. Hence the client should have some way to tell the final timeout after authenticating between server.
This timeout value is necessary when zk is used to implement lock. In this case, when client holding the lock disconnect, it should behave conservatively to try to stop all the outstanding tasks before client expires. If client couldn't guarantee this, then it should just quit (so as to avoid brain split).
The text was updated successfully, but these errors were encountered:
As we know, the
timeou
passed tozk.Connect()
is not necessarily to be the final one. Hence the client should have some way to tell the final timeout after authenticating between server.This timeout value is necessary when zk is used to implement lock. In this case, when client holding the lock disconnect, it should behave conservatively to try to stop all the outstanding tasks before client expires. If client couldn't guarantee this, then it should just quit (so as to avoid brain split).
The text was updated successfully, but these errors were encountered: