[SERVER-31351] rolling back a collection drop with long index names may not restore all the indexes Created: 02/Oct/17  Updated: 30/Oct/23  Resolved: 13/Oct/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.6.0-rc1

Type: Bug Priority: Major - P3
Reporter: Benety Goh Assignee: Benety Goh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-31060 Two phase drops with too long MMAPv1 ... Closed
is related to SERVER-29747 Two phase drops: drop indexes before ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2017-10-23
Participants:

 Description   

In SERVER-29747, we drop indexes with names that are too long for the MMAPv1 index catalog before renaming the collection to the system.drop namespace. In a mixed cluster with a WiredTiger primary and a MMAPv1 secondary, the collection drop on the secondary would be executed with the indexes (with long index names), dropped implicitly. In the event of a rollback on the MMAPv1 secondary, these dropped indexes will not be restored.



 Comments   
Comment by Githook User [ 13/Oct/17 ]

Author:

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

Message: SERVER-31351 fix ordering of index and collection drop oplog entries under two phase collection drops
Branch: master
https://github.com/mongodb/mongo/commit/be8ac18c74ce91021543dd0afe4eae86018c7e30

Comment by Githook User [ 13/Oct/17 ]

Author:

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

Message: SERVER-31351 drop indexes with long index names under any storage engine during collection drops
Branch: master
https://github.com/mongodb/mongo/commit/2fb512941c0742d85cdb69c91372cdbba211a885

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