-
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
failed to recover v3 backend from snapshot ,failed to find database snapshot file #14569
Comments
Why do you configure such a small value (about 268MB) ? Please check the db size. I suspect it ran out of the quota. If yes, then most likely the same issue as #14382.
It's included in the 3.5.5 changelog. |
Thanks for confirming. I must have searched it incorrectly. |
Hi @ahrtr Thanks, |
What happened?
We have a ETCD cluster of kubernetes which has one member with ETCD version - 3.5.3 and it was up and running from a long time of 25 days. Suddendly something happended in ETCD and getting restarted frequently,ETCD is throwing the error below as "panic: failed to recover v3 backend from snapshot"
"message" : "{"level":"panic","ts":"2022-10-06T09:18:02.022-0500","caller":"etcdserver/server.go:515","msg":"failed to recover v3 backend from snapshot","error":"failed to find database snapshot file (snap: snapshot file doesn'
"message" : "
{"level":"info","ts":"2022-10-06T09:18:01.910-0500","caller":"etcdserver/server.go:508","msg":
{*}
"recovered v2 store from snapshot{*}","snapshot-index":3420684,"snapshot-size":"23 kB"}",
"Restarting ETCD",
"message" : "{"level":"warn","ts":"2022-10-06T09:18:02.022-0500","caller":"snap/db.go:88","msg":"failed to find [SNAPSHOT-INDEX].snap.db","snapshot-index":3420684,"snapshot-file-path":"/data/member/snap/000000000034320c.snap.db","error":"snap: snapshot file doesn't exist"}",
"message" : "panic: failed to recover v3 backend from snapshot"
What did you expect to happen?
There should not be any issue in ETCD service and ETCD should be up and running instead of complaining about the missing snapshot file.
Is there any specific reason due to that ETCD had missed the snapshot file , Could you please help us to find the root cause of the issue ?
How can we reproduce it (as minimally and precisely as possible)?
We don't know the steps to reproduce it as it is not reproducible.
Anything else we need to know?
No response
Etcd version (please run commands below)
Etcd configuration (command line flags or environment variables)
ETCD_AUTO_COMPACTION_RETENTION: 100
ETCD_CERT_FILE: /run/sec/certs/server/srvcert.pem
ETCD_PEER_AUTO_TLS: true
ETCD_INITIAL_CLUSTER: etcd-0=https
ETCD_INITIAL_CLUSTER_TOKEN: etcd
ETCD_LISTEN_CLIENT_URLS: https
ETCD_MAX_SNAPSHOTS: 3
ETCD_MAX_WALS: 3
ETCD_ADVERTISE:CLIENT_URLS: https
ETCD_ENABLE_V2 false:
ETCD_KEY_FILE: /run/sec/certs/server/srvprivkey.pem
ETCD_SNAPSHOT_COUNT: 5000
ETCD_AUTO_COMPACTION_MODE: revision
ETCD_CLIENT_CERT_AUTH: true
ETCD_ELECTION_TIMEOUT: 1000
ETCD_HEARTBEAT_INTERVAL: 100
ETCD_INITIAL_CLUSTER_STATE: new
ETCD_NAME: etcd-0
ETCD_QUOTA_BACKEND_BYTES: 268435456
ETCD_TRUSTED_CA_FILE: /data/combinedca/cacertbundle.pem
ETCD_DATA_DIR: /data
ETCD_INITIAL_ADVERTISE_PEER_URLS: https
ETCD_LISTEN_PEER_URLS: https
ETCD_METRICS: basic
Etcd debug information (please run commands blow, feel free to obfuscate the IP address or FQDN in the output)
Relevant log output
The text was updated successfully, but these errors were encountered: