[SERVER-29685] Two Phase Drops: ttl indexes produce error messages when run on a dropping collection Created: 16/Jun/17  Updated: 30/Oct/23  Resolved: 05/Jul/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.5.10

Type: Bug Priority: Minor - P4
Reporter: James O'Leary Assignee: Benety Goh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2017-07-10
Participants:
Linked BF Score: 0

 Description   

The implementation of Two Phase drops is causing error messages in the logs, see the following:

2017-06-15T15:23:00.151+0000 E INDEX    [TTLMonitor] namespace 'ttlTest.system.drop.1497540178i1t1.ttl_coll' doesn't allow deletes, skipping ttl job for: { v: 2, key: { ttl: 1.0 }, name: "ttl_1", ns: "ttlTest.system.drop.1497540178i1t1.ttl_coll", expireAfterSeconds: 0.0 }

Should these messages be tagged as warnings or should ttl deletes be stopped for dropping collections? (Or both).



 Comments   
Comment by Githook User [ 05/Jul/17 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-29685 do not process ttl indexes on drop-pending collections
Branch: master
https://github.com/mongodb/mongo/commit/3c9d91f8e408339ba2ecfdf1c34cb93b4ed6a926

Generated at Thu Feb 08 04:21:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.