Skip to content
This repository has been archived by the owner on Dec 17, 2018. It is now read-only.

Channels with no activity should be closed #26

Open
allengeorge opened this issue Jan 12, 2014 · 1 comment
Open

Channels with no activity should be closed #26

allengeorge opened this issue Jan 12, 2014 · 1 comment
Assignees

Comments

@allengeorge
Copy link
Owner

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..

@ghost ghost assigned allengeorge Jan 12, 2014
@allengeorge
Copy link
Owner Author

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant