[SERVER-29459] Two Phase Drops: add option to listCollections command to include drop-pending collections Created: 06/Jun/17  Updated: 30/Oct/23  Resolved: 08/Jun/17

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: 3.5.8
Fix Version/s: 3.5.9

Type: Task Priority: Major - P3
Reporter: Benety Goh Assignee: William Schultz (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-29272 Two Phase Drops: listCollections shou... Closed
depends on SERVER-29274 Two Phase Drops: rename collection to... Closed
Related
related to SERVER-29649 Add startupWarning when a replset nod... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2017-06-19
Participants:
Linked BF Score: 0

 Description   

In order to support the work in SERVER-29274, the listCollections command was modified in SERVER-29272 to exclude drop-pending collections. These collections are meant to be removed eventually by the DropPendingCollectionReaper when the drop command has been propagated to the rest of the replica set.

It will be useful, for testing, to extend the listCollections command with an option to include these drop-pending collections.



 Comments   
Comment by William Schultz (Inactive) [ 08/Jun/17 ]

We don't need to formally document the 'includePendingDrops' command flag since it is mainly used for internal use i.e. there wouldn't be a need for customers to directly use this feature.

Comment by Githook User [ 08/Jun/17 ]

Author:

{u'username': u'will62794', u'name': u'William Schultz', u'email': u'william.schultz@mongodb.com'}

Message: SERVER-29459 Add 'includePendingDrops' option to listCollections command
Branch: master
https://github.com/mongodb/mongo/commit/9ffb2d67eae9c5361437b641e4a5542f32eaf737

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