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 Dec 19, 2017. It is now read-only.
Currently, clients submit keep-alive requests on a fixed schedule to ensure their session isn't expired. However, for clusters that are fairly active, these keep-alives represent unnecessary overhead as they require a commit within the Copycat cluster. When commands are being submitted within the session timeout, the commands can serve the same purpose as keep-alives. Thus, clients should track timers for commands submitted to the cluster and only submit keep-alives when necessary to reset indexes or to keep the session alive.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently, clients submit keep-alive requests on a fixed schedule to ensure their session isn't expired. However, for clusters that are fairly active, these keep-alives represent unnecessary overhead as they require a commit within the Copycat cluster. When commands are being submitted within the session timeout, the commands can serve the same purpose as keep-alives. Thus, clients should track timers for commands submitted to the cluster and only submit keep-alives when necessary to reset indexes or to keep the session alive.
The text was updated successfully, but these errors were encountered: