Add integration tests for timeouts and retries
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11.5k
- Forks
- 1.4k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 53
Description
We should add integration tests that exercise timeouts and retries individually any together.
Some behaviors to verify include:
* Failures on retryable routes are retried
* Retries do not exceed retry budget
* Route request actual stats reflect actual requests sent
* Route request stats reflect logical requests
* Long requests are timed out when a timeout is sent
* Server receives a cancellation when a request times out
* Client receives a 504 when request times out
* Retries stop after the timeout is reached
* Timed out responses have `err=timeout` label
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.
Research direction
No file or test entry point is identified. Start by locating Linkerd's existing integration-test harness and the timeout and retry paths it exercises. Done means adding coverage for the listed retry budgets, request statistics, timeout responses, cancellation, and timeout labeling behaviors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100