[SERVER-54007] Perform TTL deletions on clustered indexes Created: 25/Jan/21  Updated: 29/Oct/23  Resolved: 01/Mar/21

Status: Closed
Project: Core Server
Component/s: Index Maintenance
Affects Version/s: None
Fix Version/s: 4.9.0

Type: New Feature Priority: Major - P3
Reporter: Gregory Wlodarek Assignee: Louis Williams
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-53984 Add metadata for clustered indexes in... Closed
depends on SERVER-54008 Generalize CollectionScan node so it ... Closed
is depended on by SERVER-54627 re-enable timeseries_expire.js Closed
Related
related to SERVER-56676 improve handling of large/NaN values ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2021-02-22, Execution Team 2021-03-08
Participants:

 Description   

The TTL monitor only works on index specifications with the expireAfterSeconds option present. Because collections with clustered indexes do not have an _id index entry, the TTL monitor will skip them. The TTL monitor will have to be updated to handle clustered indexes. The TTL monitor only performs deletions on ranged index scans. The TTL monitor should perform deletions using ranged collection scans on collections with clustered indexes.



 Comments   
Comment by Githook User [ 01/Mar/21 ]

Author:

{'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}

Message: SERVER-54007 Support TTL deletions on time-series clustered indexes
Branch: master
https://github.com/mongodb/mongo/commit/4b95014f05755a197d81f97879a24c9a6e5c535d

Comment by Louis Williams [ 01/Feb/21 ]

Delete the default control.min.time TTL index.

Generated at Thu Feb 08 05:32:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.