[SERVER-26675] Remove 3.2 shard compatibility from MigrationManager in 3.6 Created: 18/Oct/16  Updated: 06/Dec/22  Resolved: 16/Mar/18

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

Type: Task Priority: Minor - P4
Reporter: Dianna Hohensee (Inactive) Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Duplicate Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-27390 Remove MoveChunkRequest::_takeDistLoc... Closed
Assigned Teams:
Sharding
Sprint: Sharding 2018-02-26
Participants:

 Description   

This should simplify the MigrationManager logic.

There is probably some clean up that could happen on the MigrationSourceManager, as well, like the takeDistLock parameter in the shard moveChunk command.


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