-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
请教etcd连接错误的问题 #3448
Comments
遇到同样问题, 请问如何解决的? |
Encountered the same problem, how to solve it? |
所以这个问题有解决么,我也遇到过 |
So is there any solution to this problem? I have encountered it too. |
怎么解决呢?一直遇到这个问题 |
How to solve it? Always encountered this problem |
etcd是跑在k8s中通过nodeport暴露出来的,测试发现go-zero rpc项目跑起来后,有注册到etcd中(可以看到key),
但没过一会,控制台就会报错:
{"level":"warn","ts":"2023-07-28T10:35:11.907167+0800","logger":"etcd-client","caller":"[email protected]/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc000632000/192.168.1.125:30279",
"attempt":0,"error":"rpc error: code = DeadlineExceeded desc = latest balancer error: last connection error: connection error: desc = "transport: Error while dialing: dial tcp: lookup apisix-release-etcd-0.apisix-release-etc
d-headless.default.svc.cluster.local: no such host""}
{"level":"info","ts":"2023-07-28T10:36:16.909427+0800","logger":"etcd-client","caller":"[email protected]/client.go:210","msg":"Auto sync endpoints failed.","error":"context deadline exceeded"}
注: apisix-release-etcd-0.apisix-release-etcd-headless.default.svc.cluster.local是之前安装apisix一起安装etcd时注册的svc,我也奇怪为何go-zero会对这个内网service发起请求?
报错之后没多久,在etcd中的key就不见了,也就是go-zero rpc项目下线了,请问可能是什么原因呀?
附配置:
注:
30279是etcd在k8s中暴露出来的nodeport
使用的go-zero版本是v1.5.4
The text was updated successfully, but these errors were encountered: