Details
-
Task
-
Resolution: Fixed
-
Major - P3
-
6.1.1, 6.2.0-rc6
-
Fully Compatible
-
v6.0, v5.0, v4.4
-
Sharding EMEA 2022-11-28, Sharding EMEA 2022-12-12, Sharding EMEA 2022-12-26, Sharding EMEA 2023-01-09, Sharding EMEA 2023-01-23, Sharding EMEA 2023-02-06
-
(copied to CRM)
-
3.33
Description
Database metadata refresh should not take the database lock in MODE_X. Instead, we should be able to do it under MODE_IX. This prevents database metadata refreshes from blocking behind ongoing transactions. This is similar to what SERVER-40258 did for collection metadata refreshes.
Attachments
Issue Links
- is caused by
-
SERVER-64209 Push the DatabaseShardingState state to the Storage Catalog
-
- Closed
-
- related to
-
SERVER-73345 Cancel ongoing refresh on DB metadata cleanup
-
- Closed
-
-
SERVER-40258 Relax locking requirements for sharding metadata refresh on shards
-
- Closed
-