[SERVER-9184] Cleanup TTL logic/locking Created: 29/Mar/13  Updated: 30/Dec/14  Resolved: 30/Dec/14

Status: Closed
Project: Core Server
Component/s: Index Maintenance, Internal Code
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Minor - P4
Reporter: Scott Hernandez (Inactive) Assignee: Scott Hernandez (Inactive)
Resolution: Done Votes: 0
Labels: ttl
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-10727 Cleanup TTL internals Closed
related to SERVER-11732 TTL indexes should imply usePowersOf2... Closed
is related to SERVER-9053 TTL index asserts on 2.4 secondary Closed
is related to SERVER-12186 TTLMonitor error Closed
Participants:

 Description   

Do full cleanup for TTL thread wrt locking.

This is the cleanup related to SERVER-9053, but in a non-back-portable way.



 Comments   
Comment by Matt Dannenberg [ 15/Oct/13 ]

After looking at this, it seems the only thing we can do is grab the NamespaceDetails a bit earlier to check if the namespace still exists and is not empty. This would add a lock upgrade in the normal case (where the collection exist and isn't empty), but would avoid acquiring an unneeded write lock in the case of a missing or empty collection.

If anyone would like to pursue this, that is what can be done.

Generated at Thu Feb 08 03:19:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.