[SERVER-53077] Change DistLock initialization so each node in a shard will have the same ID when locking Created: 25/Nov/20 Updated: 29/Oct/23 Resolved: 25/Nov/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Marcos José Grillo Ramirez | Assignee: | Marcos José Grillo Ramirez |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-1965-Milestone-1-Create | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding 2020-11-30 | ||||||||
| Participants: | |||||||||
| Description |
|
When initializing the shard components, a new ID is generated for the distributed lock, however, if a primary node holds a lock and a stepdown happens, then when trying to hold a lock over the same resource (when retrying the operation) will fail. As part of the PM-1965 project, the shardCollection command will be moved to the primary, and the current behavior will not allow this necessary change. |
| Comments |
| Comment by Githook User [ 25/Nov/20 ] |
|
Author: {'name': 'Marcos José Grillo Ramírez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}Message: |