Details
-
Improvement
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
Sharding EMEA
-
Fully Compatible
-
Sharding EMEA 2023-04-17
Description
As part of SERVER-71198 we found that ShardingInitializationMongoD::updateShardIdentityConfigString is taking a database MODE_X lock and then replacing a single document in a collection underneath it without holding any collection locks.{{{}
{}}}
Ideally in this situation we should only acquire a MODE_IX lock using AutoGetCollection for the target collection as we already provide document-level locking with WiredTiger. This would avoid the unnecessary strong lock on the database.
Attachments
Issue Links
- related to
-
SERVER-71198 Assert that unkillable operations that take X collection locks do not hold the RSTL
-
- Backlog
-