[SERVER-69934] TTLDeletes should be deprioritized Created: 23/Sep/22 Updated: 29/Oct/23 Resolved: 28/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Haley Connelly | Assignee: | Jordi Olivares Provencio |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Execution Team 2022-10-03 |
| Participants: |
| Description |
|
When the server is under heavy load, TTL deletes should be deprioritized and run secondary to user operations |
| Comments |
| Comment by Githook User [ 13/Oct/22 ] |
|
Author: {'name': 'Jordi Olivares Provencio', 'email': 'jordi.olivares-provencio@mongodb.com', 'username': 'jordiolivares'}Message: PERF-3049 Add workload for Background TTL deletions (#737)
|
| Comment by Githook User [ 28/Sep/22 ] |
|
Author: {'name': 'Jordi Olivares Provencio', 'email': 'jordi.olivares-provencio@mongodb.com', 'username': 'jordiolivares'}Message: |
| Comment by Haley Connelly [ 23/Sep/22 ] |
|
This should be done concurrently with a performance test |