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 17, 2018. It is now read-only.
Right now it's possible for an inactive connection to RaftNetworkClient to persist forever. While this isn't a serious issue, it would be better to have a timeout that closes the channel if there is no network activity greater than a timeout..
The text was updated successfully, but these errors were encountered:
I wonder if I need heartbeats at the RaftNetworkClient level. Also, in the interest of bounding work, it would probably be useful for RaftAlgorithm to know that it can't reach peers in the cluster to avoid the work of looking up log entries and serializing heartbeats. The downside is that suddenly I have the concept of online/offline state associated with each cluster member. Ugh.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Right now it's possible for an inactive connection to RaftNetworkClient to persist forever. While this isn't a serious issue, it would be better to have a timeout that closes the channel if there is no network activity greater than a timeout..
The text was updated successfully, but these errors were encountered: