[SERVER-30019] Implement LockManager locks for moved metadata commands Created: 06/Jul/17 Updated: 27/Oct/23 Resolved: 23/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jessica Yu | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Participants: |
| Description |
|
Begin introducing LockManager hierarchical locks into the metadata commands that have been already moved to mongos, including to date shardCollection and movePrimary. Start with coarsest locking scheme to first achieve viable locking; can improve upon this later. For backwards compatibility, will not remove distributed locking in this ticket. |
| Comments |
| Comment by Kaloian Manassiev [ 23/Feb/18 ] |
|
Closing this ticket until we have fleshed-out the design of multi-statement transactions on shards. |
| Comment by Kaloian Manassiev [ 15/Sep/17 ] |
|
No, this doesn't make sense doing until we have moved all commands to the config server, so moving it to the Backlog. |
| Comment by Gregory McKeon (Inactive) [ 14/Sep/17 ] |
|
kaloian.manassiev is this still 3.5 required? |