Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 6.1.0-rc0
Affects Version/s: None
Component/s: None
Labels:
- PM-2227-M3

Backwards Compatibility:
Fully Compatible
Sprint:
Execution Team 2022-04-18, Execution Team 2022-05-02
Linked BF Score:
135
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

Switch the TTL monitor to batched deletions. Add a server parameter to switch back to the previous document-by-document deletion behaviour.

depends on

SERVER-64972 Generate change stream events for batched deletes

Closed

is depended on by

SERVER-56194 Make TTL deletes fair

Closed

related to

SERVER-66919 Batched TTL deletions can cause out-of-order oplog application for tenant migration state docs and that messes up tenant access blocker entries.

Closed

SERVER-102168 TTL Index Deletion Speed is Extremely Slow

Investigating

SERVER-67334 Accessing the opCtx decoration 'tenantIdToDeleteDecoration' from the on-commit hook of TenantMigrationRecipientOpObserver::onDelete() is not safe after the ttl batch deletion feature.

Closed

Assignee:: Yujin Kang Park
Reporter:: Josef Ahmad
Participants:: Githook User, Josef Ahmad, Yujin Kang Park
Votes:: 0 Vote for this issue
Watchers:: 5 Start watching this issue

Created:: Jan 27 2022 03:43:40 PM UTC
Updated:: Apr 28 2025 05:21:26 PM UTC
Resolved:: Apr 29 2022 08:02:44 AM UTC
Confidence Status Last Update:: 25/Apr/22 7:44 AM

Details

Description

Attachments

Issue Links

Activity

People

Dates