-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[Bug]: "caller":"backend/backend.go:189","msg":"failed to open database","path":"/bitnami/etcd/data/member/snap/db" #33026
Comments
I think you hit some etcd data issue. If you only deployed 1 etcd replica, then I'm not sure you can still recover your data. |
/assign @erigo /unassign |
The issue is likely with etcd; my Kubernetes (k8s) is running on the Docker engine, with version v26.1.2. I have also seen this issue in the official issue tracker, but I didn't quite understand it. |
full logs: |
It should be a bug caused by storage, and the specific location should be an issue with the op_lock stored in NFS. |
It is recommended that the official provide a best practice for setting up etcd, mq, and minio storage and recommend using local pv for these highly available components. |
we don't encourage anything, including minio, etcd and kafka to running on nfs or nas. |
tks for your advise, we will try to deploy the components that Milvus depend on as expected. |
Is there an existing issue for this?
Environment
Current Behavior
{"level":"panic","ts":"2024-05-13T12:10:12.697Z","caller":"backend/backend.go:189","msg":"failed to open database","path":"/bitnami/etcd/data/member/snap/db","error":"errno 524","stacktrace":"go.etcd.io/etcd/server/v3/mvcc/backend.newBackend\n\t/tmp/etcd-release-3.5.5/etcd/release/etcd/server/mvcc/backend/backend.go:189\ngo.etcd.io/etcd/server/v3/mvcc/backend.New\n\t/tmp/etcd-release-3.5.5/etcd/release/etcd/server/mvcc/backend/backend.go:163\ngo.etcd.io/etcd/server/v3/etcdserver.newBackend\n\t/tmp/etcd-release-3.5.5/etcd/release/etcd/server/etcdserver/backend.go:55\ngo.etcd.io/etcd/server/v3/etcdserver.openBackend.func1\n\t/tmp/etcd-release-3.5.5/etcd/release/etcd/server/etcdserver/backend.go:76"}
panic: failed to open database
goroutine 52 [running]:
go.uber.org/zap/zapcore.(*CheckedEntry).Write(0xc0005be300, 0xc0004ca000, 0x2, 0x2)
/usr/local/google/home/siarkowicz/.gvm/pkgsets/go1.16.15/global/pkg/mod/go.uber.org/zap@v1.17.0/zapcore/entry.go:234 +0x58d
go.uber.org/zap.(*Logger).Panic(0xc0000d40a0, 0x12301ac, 0x17, 0xc0004ca000, 0x2, 0x2)
/usr/local/google/home/siarkowicz/.gvm/pkgsets/go1.16.15/global/pkg/mod/go.uber.org/zap@v1.17.0/logger.go:227 +0x85
go.etcd.io/etcd/server/v3/mvcc/backend.newBackend(0xc000130a80, 0x21, 0x5f5e100, 0x2710, 0x121f689, 0x7, 0x119999999, 0xc0000d40a0, 0x0, 0x139f320, ...)
/tmp/etcd-release-3.5.5/etcd/release/etcd/server/mvcc/backend/backend.go:189 +0x3b3
go.etcd.io/etcd/server/v3/mvcc/backend.New(...)
/tmp/etcd-release-3.5.5/etcd/release/etcd/server/mvcc/backend/backend.go:163
go.etcd.io/etcd/server/v3/etcdserver.newBackend(0xc0000420ca, 0x16, 0x0, 0x0, 0x0, 0x0, 0xc0001bfa70, 0x1, 0x1, 0xc00014e5a0, ...)
/tmp/etcd-release-3.5.5/etcd/release/etcd/server/etcdserver/backend.go:55 +0x1f8
go.etcd.io/etcd/server/v3/etcdserver.openBackend.func1(0xc0004cc060, 0xc0000fa300, 0x139f320, 0xc0003687e0)
/tmp/etcd-release-3.5.5/etcd/release/etcd/server/etcdserver/backend.go:76 +0xc5
created by go.etcd.io/etcd/server/v3/etcdserver.openBackend
/tmp/etcd-release-3.5.5/etcd/release/etcd/server/etcdserver/backend.go:75 +0x145
Expected Behavior
No response
Steps To Reproduce
Milvus Log
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: