[SERVER-72073] Ensure TTL deletes don't fall too far behind Created: 13/Dec/22 Updated: 29/Oct/23 Resolved: 14/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Haley Connelly | Assignee: | Haley Connelly |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Execution Team 2023-02-20, Execution Team 2023-02-06 |
| Participants: |
| Description |
|
While TTL deletes are lower priority than user operations in most cases, add a failsafe that the TTL deletes for a given collection will not fall so far behind they lose the ability to recover |
| Comments |
| Comment by Githook User [ 14/Feb/23 ] |
|
Author: {'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}Message: |