MongoDB | 2591352

Info

Consider the following scenario to transitionToDedicatedConfigServer. 1. config shard is marked to start draining 2. The last chunk is moved out from the config shard 3. The last orphan is cleaned up 4. Once all the chunks/orphans are cleaned, all the dbs are dropped. 5. Remove entry from (config.shards) If a ddl operation(drop or rename) is received before step 5, we will send drop/rename to all shards which takes a critical section lock on all the shards. And if the ddl operation completes after step 5, we will leave a lingering lock on config server since the release is sent to all shard (config server isn't a shard anymore). This ticket is to add a workaround fix where when the critical section is released for drop/rename - include configServer in all shards list. Also, consider/evaluate other DDLs as time permits

Top User Comments

xgen-internal-githook commented on Tue, 12 Mar 2024 17:11:22 +0000: Author: {'name': 'Randolph Tan', 'email': 'randolph@10gen.com', 'username': 'renctan'} Message: SERVER-87137 Make drop and rename coordinator always include the config server when releasing the critical section (#19648) GitOrigin-RevId: f8e6173fe093a06258ec1cc8a0740d0d427fa867 Branch: master https://github.com/mongodb/mongo/commit/595cfb0af7d3a2deac2913b8690ed14158b1527a

Steps to Reproduce