Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

no reconnection #3

Closed
laforge49 opened this Issue Jan 10, 2013 · 3 comments

Comments

Projects
None yet
1 participant
Owner

laforge49 commented Jan 10, 2013

When a host is disconnected/reconnected from the network, the node on that host does not reconnect to the cluster.

Owner

laforge49 commented Jan 11, 2013

This might just be a 3-host issue. Or at least, it is not showing up today in 2-host testing.

Owner

laforge49 commented Jan 11, 2013

After a connection is restored, occasionally, one side times out the connection and the other side reports that the socket is closed. After that each side sees the other node but not the servers on that node. Moderately difficult to reproduce.

Owner

laforge49 commented Jan 11, 2013

The bug became easily reproducible by reducing the socket read timeout from 10 to 3 seconds.

A duplicate channel was being created which, on timeout, was being taken too seriously--its closure should not have been significant since it was a duplicate!

@laforge49 laforge49 closed this Jan 11, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment