-
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: unexpected error from lease detach #6133
Comments
@imkira Is it a fresh cluster from 3.0.4? Or it was an old cluster upgraded to 3.0.4? Are you able to reproduce the issue? |
@imkira Can you send the data dirs of the 3 nodes to me at [email protected]? |
@xiang90 it is a fresh new 3.0.4 cluster. |
@imkira Do you have data dirs for other members? Do other member also panic? |
@xiang90 Yes I do have the data dirs. No, they don't panic. I will send them right away. |
@xiang90 just sent you the data dirs now. Thanks in advance |
Do you still have the etcd server log before crashing? |
@xiang90 Yes I do. I have just sent you. Please take a look. Thanks |
I looked into the data dirs, and I can confirm you that your issue is fixed by #6098. For the huge memory usage issue, can you please open another issue? |
Thanks a lot! I have just filed issue #6134 to address the memory usage problem. |
I am using etcd v3.0.4 (release) with a 3 node cluster using the following config:
For another reason the cluster crashed and now when I try to boot up node 2, I get this:
Is this supposed to be fixed by #6098 ?
The text was updated successfully, but these errors were encountered: