-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
ALL
-
Sharding EMEA 2022-06-13, Sharding EMEA 2022-06-27
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
The multi DB locking capability does not correctly cooperate with sharding DB primary placement since it doesn't check whether the current shard is primary for the same database, and furthermore it is never correct to use if all the primaries are not placed on the same node.
Since currently there are no consumers of that capability, we should remove it and if it is needed, we should design it work properly with sharding.
- causes
-
-
- Closed
-
- has to be done before
-
-
- Backlog
-
- is related to
-
SERVER-64121 Add an enum flag to AutoGet* paths that disables multi-database locking unless specifically enabled
-
- Closed
-