Skip to content
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

We are running Namerd & Consul cluster in our environment ,getting below error frequently and that break application communication #2442

Open
rajredison opened this issue Jan 17, 2022 · 0 comments

Comments

@rajredison
Copy link

We are running following Namerd & Consul version.

Namerd Version: 1.3.0
Consul Version: 1.0.1

Error :
Namerd-01 namerd: E 0114 06:30:29.851 UTC THREAD31: Retrying Consul request ‘GET /v1/health/service/xxxx?dc=x&passing=true’ on NonFatal error: com.twitter.finagle.ChannelWriteException: com.twitter.finagle.ChannelClosedException: null at remote address: consul.service.x.x.internal.prod/x.x.x.x:8500. Remote Info: Not Available from service: client. Remote Info: Upstream Address: Not Available, Upstream id: Not Available, Downstream Address: consul.x.x.x.internal/x.x.x.x:8500, Downstream label: client, Trace Id: 6d298c434b2d50b7.6d298c434b2d50b7<:6d298c434b2d50b7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant