-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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
Panic occurs when etcd (ver 3.5.13) new node joins the cluster #17855
Labels
Comments
node1 log:
|
node2 log:
|
chenyang8094
changed the title
tocommit(21) is out of range [lastIndex(0)]. Was the raft log corrupted, truncated, or lost?
Panic occurs when etcd new node joins the cluster
Apr 23, 2024
chenyang8094
changed the title
Panic occurs when etcd new node joins the cluster
Panic occurs when etcd (ver 3.5.13) new node joins the cluster
Apr 23, 2024
A known issue etcd-io/raft#18 |
Also refer etcd-io/raft#29 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug report criteria
What happened?
My operation process is as follows: I start an etcd node (called node1) first, and wait for it to become the Leader, and write a small amount of data to node1. Then, I start another etcd node (called node2) and have node2 join node1 to form a Raft cluster. In my tests, there are occasional instances where node2 panics, with the error message: "panic: tocommit(21) is out of range [lastIndex(0)]. Was the raft log corrupted, truncated, or lost?". Although I have seen several similar issues, I believe it is unreasonable for a newly started etcd node to encounter this situation. I am using the latest release version 3.5.13.
What did you expect to happen?
node2 should not crash.
How can we reproduce it (as minimally and precisely as possible)?
start an etcd node (called node1) first, and wait for it to become the Leader, and write a small amount of data to node1. Then, Istart another etcd node (called node2) and have node2 join node1 to form a Raft cluster. In my tests, there are occasional instances where node2 panics, with the error message: "panic: tocommit(21) is out of range [lastIndex(0)].
To be clear, the probability of recurrence is really low。
Anything else we need to know?
No response
Etcd version (please run commands below)
3.5.13
Etcd configuration (command line flags or environment variables)
node1:
node2:
Relevant log output
See the comments below
The text was updated successfully, but these errors were encountered: