Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cluster does not survive a vernemq restart of one server. #58

Closed
lbthomsen opened this issue Oct 21, 2015 · 1 comment
Closed

Cluster does not survive a vernemq restart of one server. #58

lbthomsen opened this issue Oct 21, 2015 · 1 comment

Comments

@lbthomsen
Copy link

From IRC discussion:

[18:01] Steps to provoke:
[18:02] 1. clean out /var/lib/vernemq completely on both systems with vernemq stopped
[18:02] 2. Start vernemq on both systems
[18:02] 3. One mosquitto_sub subscribed to a topic on first server
[18:02] 4. One mosquitto_sub susscribed to same topic on second server
[18:03] 5. Do the cluster join and verify both nodes report ok
[18:03] 6. Do a mosquitto_pub to one server - both subscribed servers receive
[18:03] 7. Do a mosquitto_pub to second server - both subscribed servers receive
[18:04] 8. Restart second server (vernemq restart)
[18:04] 9 Repeat 6-7
[18:04] Now it only works from server 2 to server 1
[18:04] Both servers still report ok on the cluster
[18:05] And it has not recovered in the time it took to write the above :)

@ioolkos
Copy link
Contributor

ioolkos commented Oct 21, 2015

Confirmed this. Looks like a bug in the re-connect logic from server1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants