[SERVER-66869] Get rid of the multi DB locking capability Created: 31/May/22 Updated: 29/Oct/23 Resolved: 20/Jun/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | LFR-BUG, PM-2144-Milestone-0 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||
| Sprint: | Sharding EMEA 2022-06-13, Sharding EMEA 2022-06-27 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
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. |
| Comments |
| Comment by Githook User [ 20/Jun/22 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: |
| Comment by Githook User [ 20/Jun/22 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: |