[SERVER-11266] Error on capped collection TTL deletes blocks other collection deletes (in same db) Created: 18/Oct/13  Updated: 20/Jan/16  Resolved: 21/Jan/15

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

Type: Bug Priority: Minor - P4
Reporter: Scott Hernandez (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: ttl, ttlmonitor
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-16749 Unhandled DBException in TTLMonitor t... Closed
related to SERVER-769 Validate top-level & index spec field... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

If you create a TTL index on a capped collection, which should not be allowed, then when documents are found to delete a user assertion is generated, exception thrown, and all unprocessed collections in db are skipped.

2013-10-18T11:47:14.719-0400 [TTLMonitor] ERROR: error processing ttl for db: test 10101 can't remove from a capped collection



 Comments   
Comment by Scott Hernandez (Inactive) [ 21/Jan/15 ]

fixed with SERVER-16749 – really a dup since this issue changed from an error to fassert due to how unhandled exceptions were treated by background jobs.

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