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
I think this is because when you brought down server 2, you deleted the data (and Raft log). So when you brought it back up, server 1 started sending data that server 2 missed while it was down. But server 2 didn't have any config or know any of this stuff.
The right way would be to down server 2, kill all the data, then remove the server from the cluster in the admin UI (which you can't currently do). Then when you bring it up it should join the cluster successfully.
If you kill all the data on a server, it won't just automatically get everything copied over. Issue #67 will add functionality for you to do this.
Not sure if I did this right, but wanted to try a scenario when one of the servers in 2 node cluster dies.
server2 crashes immediately with:
http://pastebin.com/4hrdM0JS
Every time i start server2 (db01 in this case) it gets added to the list of servers in cluster:
When i start server2 in the log of server1 I see:
Once I stopped server1 and server2, deleted /data and /tmp on both servers and started them again, both servers connected and worked fine.
I was able to reproduce it second time.
The text was updated successfully, but these errors were encountered: