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.