[SERVER-29728] Fix distributed locking on movePrimary Created: 19/Jun/17  Updated: 27/Oct/23  Resolved: 28/Aug/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.5.8
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Jessica Yu Assignee: Jessica Yu
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Sprint: Sharding 2017-07-10, Sharding 2017-07-31
Participants:

 Description   

Currently, the movePrimary command takes a distlock identified by database name and command name. This ticket makes it take the database name distlock to avoid concurrency issues with other metadata commands.



 Comments   
Comment by Jessica Yu [ 13/Jul/17 ]

Keeping distributed lock as is in movePrimary for backwards compatibility; see SERVER-30019 for planned locking changes.

Generated at Thu Feb 08 04:21:40 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.