[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: |