letsencrypt / letsencrypt/boulder
va: use only half the available timeout on primary validation
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
If we assume a primary validation and the MPIC validations take approximately the same amount of time, and the overall timeout for an RA->VA request is 90s, then a request that takes 50s for primary validation will fail secondary validation because not enough time is left.
We can reflect this more accurately by having the VA look at the remaining time on its context object, cut that time in half, and putting that number as a timeout for primary validation specifically. This can allow us to drop failing requests a little earlier. This can also allow us to confidently put a shorter timeout on the VA->RVA connection.
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 locating the VA code that performs primary validation and reads the request context's remaining time. Trace how the timeout is passed to primary validation and how the VA-to-RVA request is timed. Done means primary validation uses half the remaining context time and the shorter downstream timeout can be applied without breaking secondary validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100