letsencrypt / letsencrypt/boulder
Reconcile RA "background" task timeouts.
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
We will have three separate timeouts that govern drainable work:
- ra.finalizeTimeout
- the VA's configured RPC timeout (x2, for CAA and DCV), plus the SA's configured RPC timeout
- revokeAuthorizations, 5s hardcoded
We should cover all three drainable work sites with a consistent timeout so we know how long to wait between kill -TERM and kill -KILL for clean shutdown.
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
Start by tracing the RA drainable work sites involving ra.finalizeTimeout, the VA and SA configured RPC timeouts, and the hardcoded 5s revokeAuthorizations timeout. Determine how each timeout affects the interval between kill -TERM and kill -KILL. Done means all three sites use a consistent timeout for clean shutdown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, distributed-systems
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100