[SERVER-46216] The dropIndexes command should not hold the global lock throughout the duration of the command Created: 18/Feb/20  Updated: 29/Oct/23  Resolved: 18/Feb/20

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

Type: Bug Priority: Major - P3
Reporter: Gregory Wlodarek Assignee: Gregory Wlodarek
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: Execution Team 2020-02-24
Participants:
Linked BF Score: 37

 Description   

This is problematic when other threads need to take a stronger RSTL lock (MODE_S/MODE_X) for other server operations while the dropIndexes command is waiting for index builds to abort. Instead of holding the global lock throughout the duration of the dropIndexes command, we can check the replica set state when reacquiring the locks.



 Comments   
Comment by Githook User [ 18/Feb/20 ]

Author:

{'name': 'Gregory Wlodarek', 'username': 'GWlodarek', 'email': 'gregory.wlodarek@mongodb.com'}

Message: SERVER-46216 The dropIndexes command should not hold the global lock throughout the duration of the command
Branch: master
https://github.com/mongodb/mongo/commit/c18271eaf8bf8a85549ffec363748b40e57b9392

Generated at Thu Feb 08 05:10:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.