zhangyihong commented on issue #282:
URL:
https://github.com/apache/apisix-helm-chart/issues/282#issuecomment-1125877086
> @zhangyihong我很好奇ETCD实例异常打印的错误日志。您还保留任何相关日志吗？
>
之前出现问题的时候，故障的etcd实例只有一个警告日志，如下：
{"level":"warn","ts":"2022-05-12T06:48:47.594Z","caller":"clientv3/retry_interceptor.go:62","msg":"retrying
of unary invoker
failed","target":"endpoint://client-cfa2c90d-8acd-4633-86ea-aaf91758985e/apisix-etcd-0.apisix-etcd-headless.ingress-apisix.svc.cluster.local:2379","attempt":0,"error":"rpc
error: code = NotFound desc = etcdserver: member not found"}
Error: etcdserver: member not found
```
kubectl logs apisix-etcd-1 -n ingress-apisix
etcd 06:48:47.33
etcd 06:48:47.33 Welcome to the Bitnami etcd container
etcd 06:48:47.34 Subscribe to project updates by watching
https://github.com/bitnami/bitnami-docker-etcd
etcd 06:48:47.34 Submit issues and feature requests at
https://github.com/bitnami/bitnami-docker-etcd/issues
etcd 06:48:47.34
etcd 06:48:47.34 INFO ==> ** Starting etcd setup **
etcd 06:48:47.36 INFO ==> Validating settings in ETCD_* env vars..
etcd 06:48:47.37 WARN ==> You set the environment variable
ALLOW_NONE_AUTHENTICATION=yes. For safety reasons, do not use this flag in a
production environment.
etcd 06:48:47.38 INFO ==> Initializing etcd
etcd 06:48:47.38 INFO ==> Generating etcd config file using env variables
etcd 06:48:47.40 INFO ==> Detected data from previous deployments
etcd 06:48:47.50 INFO ==> Updating member in existing cluster
{"level":"warn","ts":"2022-05-12T06:48:47.594Z","caller":"clientv3/retry_interceptor.go:62","msg":"retrying
of unary invoker
failed","target":"endpoint://client-cfa2c90d-8acd-4633-86ea-aaf91758985e/apisix-etcd-0.apisix-etcd-headless.ingress-apisix.svc.cluster.local:2379","attempt":0,"error":"rpc
error: code = NotFound desc = etcdserver: member not found"}
Error: etcdserver: member not found
```
--
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]
