[SERVER-59221] OCSPFetcher should rapidly retry on network error Created: 10/Aug/21 Updated: 29/Oct/23 Resolved: 07/Sep/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Spencer Jackson | Assignee: | Erwin Pe |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Security 2021-09-06, Security 2021-09-20 | ||||
| Participants: | |||||
| Linked BF Score: | 15 | ||||
| Description |
|
The OCSPFetcher after every fetch-and-staple job, the OCSPFetcher schedules when the next next job should be using a method called getPeriodForStapleJob. If the fetch failed, this will be 5 minutes. We should probably start with a small value, and gradually build up, so that we can quickly recover from transient outages, and our JSTests will be able to recover from races where we try to fetch while the responder is offline for reconfiguration. |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 07/Sep/21 ] |
|
Author: {'name': 'Erwin Pe', 'email': 'erwin.pe@mongodb.com', 'username': 'erwee'}Message: |