Improve handling of Consul failures
See original GitHub issueFiling a linkerd issue
Issue Type:
- Bug report
- Feature request
What happened: Upon Consul failure (in this case, unexpected 403 response) Namerd produced Addr.Fail and wasn’t able to resolve any names. Presumably Namerd saw valid responses from Consul before Consul entered failed state.
What you expected to happen:
- Produce a human-friendly message about namer/dtab-store failures in logs/admin-ui rather than just stacktraces
- Stabilize Consul-related activities so that once there was a successful result never return failure again
Environment:
Linkerd/Namerd v1.1.3
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Fault Tolerance in Consul - HashiCorp Developer
Fault tolerance is a system's ability to operate without interruption despite component failure. Learn how a set of Consul servers provide fault tolerance ......
Read more >Inside the migration from Consul to memberlist at Grafana Labs
An in-depth analysis of how the Grafana Labs database teams went from using Consul to embedded memberlist.
Read more >The Consul outage that never happened - GitLab
Sometimes a good plan is the best tool for the job.
Read more >Service discovery for Docker containers using Consul and ...
If a client receives an RPC request, it forwards it to a server node for handling. When a client joins your consul cluster...
Read more >Consul in Kubernetes — Pushing to Production - Medium
Steps to improve Consul cluster · In daily operation, there is little to none logs from consul server containers and client containers ·...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Great, thanks! I think this definitely should improve stability in face of Consul failures and give us more perspective on what exactly is happening! Looking forward to seeing this in next release. 😃
C’mon, there is nothing you should be sorry about. 😉 That’s in fact my fault not giving enough details within the original issue description. And having stabilization for DtabStore is also important IMO. Thanks for looking into the issue!