[SERVER-71290] configure ttlIndexDeleteTargetTimeMS in TTLTest Created: 11/Nov/22 Updated: 29/Oct/23 Resolved: 14/Nov/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Benety Goh |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Sprint: | Execution Team 2022-11-28 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 35 | ||||||||||||
| Description |
|
The TTL index deletion tests disable most throttling limits related to batched deletes to ensure the tests are not constrained by the wall clock. We should add ttlIndexDeleteTargetTimeMS to the current list of time-based limits to disable. |
| Comments |
| Comment by Githook User [ 14/Nov/22 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: |