[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:
Depends
is depended on by SERVER-52616 Create the _shardsvrCreateCollection ... Closed
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: SERVER-53077 Change the DistLock initialization so all nodes within a shard have the same ID
Branch: master
https://github.com/mongodb/mongo/commit/a6b7feddd72d9a9aa4daf5d1198ab051ca4afd40

Generated at Thu Feb 08 05:29:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.