heresie opened a new issue, #506:
URL: https://github.com/apache/apisix-helm-chart/issues/506
Hello everybody 👋
We are currently having problems with the current APISIX Helm Chart
(`1.1.1`) deployment on our kubernetes cluster.
In fact, we are encountering numerous `etcd` errors like that, making `etcd`
component instable :
```
{"level":"panic","ts":"2023-03-09T08:17:11.675Z","caller":"etcdserver/server.go:515","msg":"failed
to recover v3 backend from snapshot","error":"failed to find database snapshot
file (snap: snapshot file doesn't
exist)","stacktrace":"go.etcd.io/etcd/server/v3/etcdserver.NewServer\n\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/server.go:515\ngo.etcd.io/etcd/server/v3/embed.StartEtcd\n\t/go/src/go.etcd.io/etcd/release/etcd/server/embed/etcd.go:245\ngo.etcd.io/etcd/server/v3/etcdmain.startEtcd\n\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdmain/etcd.go:228\ngo.etcd.io/etcd/server/v3/etcdmain.startEtcdOrProxyV2\n\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdmain/etcd.go:123\ngo.etcd.io/etcd/server/v3/etcdmain.Main\n\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdmain/main.go:40\nmain.main\n\t/go/src/go.etcd.io/etcd/release/etcd/server/main.go:32\nruntime.main\n\t/go/gos/go1.16.15/src/runtime/proc.go:225"}
panic: failed to recover v3 backend from snapshot
```
An Issue was raised on `etcd` Repository in late 2022 :
https://github.com/etcd-io/etcd/issues/14749
The error was fixed in `etcd` in version `>= 3.5.6`.
I made several tests upgrading APISIX Helm Chart `etcd` dependency to the
latest `bitnami/etcd` Helm Chart version (`8.7.7`), and errors disappeared.
`etcd` service is now stable.
Can you consider updating the `etcd` dependency in current APISIX Helm Chart
?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
