[SERVER-54810] Do not acquire the dist lock in CSRS on RefineShardKey after 5.0 Created: 26/Feb/21  Updated: 29/Oct/23  Resolved: 02/Aug/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Tommaso Tocci
Resolution: Fixed Votes: 0
Labels: 5.0-cleanup, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Participants:

 Description   

After 5.0 has branched out, the ConfigsvrRefineCollectionShardKeyCommand will just be receivable from the primary shard already holding the lock, hence the changes introduced in SERVER-54809 can be thrown away.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 02/Aug/21 ]

Author:

{'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}

Message: SERVER-54810 Do not acquire the dist lock in CSRS on RefineShardKey after 5.0
Branch: master
https://github.com/mongodb/mongo/commit/def8791009754e0705937815a4bea7ed2e94e4e0

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