Retries, Timeouts and Other New Stability Features in Linkerd2
@adleong is already working on this.
Since Feb 14, 2019.
- Dominant language
- JavaScript
- Stars
- 60
- Forks
- 221
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 1
Description
### What is the purpose of the post?
The purpose of this post is to explain what Retries and Timeouts are on Linkerd and how they are different than other similar implementations (relationship to Service Profiles)
### What should it talk about?
This post will discuss the basic architecture and functionality of Timeouts and Retries, why they are important for improving reliability, and then provide a tutorial on how to use them.
### Who is the target audience?
* [X ] Architect
* [X] SRE
* [X] Developers
### Are there any assets?
Yes. We will need screenshot / code snippets / gifs showing how to make these two features work
### What are the dependencies?
No
### Relevant Examples / References
https://istio.io/docs/concepts/traffic-management/ (although we want something much briefer)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.