[SERVER-33197] implement joining behavior for movePrimary on shards Created: 08/Feb/18  Updated: 29/Oct/23  Resolved: 27/Feb/18

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

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Blake Oler
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-02-12, Sharding 2018-02-26, Sharding 2018-03-12
Participants:

 Description   

If a shard gets additional movePrimary commands while it is already processing a movePrimary command, the later movePrimary commands should "join" the first one.

This should mirror the way moveChunks 'join' an existing moveChunk.

It will involve creating a new ActiveMovePrimariesRegistry class that mirrors ActiveMigrationsRegistry and installing an ActiveMovePrimariesRegistry on ShardingState.

Add testing that if multiple movePrimary's are sent to a shard, only the first one actually executes.



 Comments   
Comment by Githook User [ 27/Feb/18 ]

Author:

{'email': 'blake.oler@mongodb.com', 'name': 'Blake Oler', 'username': 'BlakeIsBlake'}

Message: SERVER-33197 Implement joining behavior for movePrimary on shards
Branch: master
https://github.com/mongodb/mongo/commit/cbe3e978d9fd41b85f2f394ce6182e6579667fd1

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