-
Notifications
You must be signed in to change notification settings - Fork 285
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
Can a bad state NATS cluster be bootstrapped with new config? #1277
Comments
In order to help you better, would you please clarify if you are talking about NATS Streaming or JetStream? There is no meta.json in NATS Streaming... But I believe that the solution would be quite similar: you need to start a 4th node to allow election (and then deletion of the old nodes). |
I am talking about "NATS Streaming" and I have found the existence of meta.json in it. |
Again, not sure what that file is. Could you display the content of it? I do not believe that NATS Streaming is creating this file. |
The following is the content of meta.json (located at log/442e19d3-faca-41e5-a32c-803a72d0e4ab/snapshots/12926-115914-1666846843907/ ):
|
I see. Well, my previous answer stands. Try to start an extra node so that quorum can be reached and a leader be elected. |
My NATS cluster of 3 nodes is in bad state. Previously it was a 6-node cluster and recently it has been trimmed down to 3-node. The meta.json still shows the 6 members. The leader election fails as it expects 4 votes but gets only 3 votes, though other 3 staled nodes don't have NATS running. All the 3 active members are either in Follower or Candidate state. So attempting to remove the 3 staled nodes does not work.
Is there anyway to bootstrap this new cluster with the newer configuration?
The text was updated successfully, but these errors were encountered: