[SERVER-57114] Make refineShardKey use the new ShardingCoordinator infrastructure Created: 21/May/21  Updated: 29/Oct/23  Resolved: 11/Jun/21

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

Type: Task Priority: Major - P3
Reporter: Tommaso Tocci Assignee: Marcos José Grillo Ramirez
Resolution: Fixed Votes: 0
Labels: PM-1965-Cleanup
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Problem/Incident
causes SERVER-64651 Issue with refineCollectionShardKey Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v5.0
Sprint: Sharding EMEA 2021-06-14
Participants:

 Description   

The refine shard key coodinator is still using the old ShardingDDLCoordinator_NORESILIENT interface. The goal of this ticket is to integrate it with the new ShardingDDLCoordinator infrastructure. For the moment we won't make it resilient, so it won't persist its state on disk.



 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 [ 11/Jun/21 ]

Author:

{'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}

Message: SERVER-57114 Change refine collection shard key command to use ShardingDDLCoordinator

... instead of ShardinDDLCoordinator_NORESILIENT
Branch: master
https://github.com/mongodb/mongo/commit/7679fadf823e027a30ac81d7a1ec397fe97a0fde

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