-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
Sharding 2020-10-19, Sharding 2020-11-02, Sharding 2020-11-16
-
40
Every time the coordinator wants a set of shards (donor/recipient) to be aware of changes, it should:
- Take one chunk from every shard for a collection (original/temporary)
- Set that chunk version to currentMaxVersion + 1
So that every shard will have a "shard version" of [currentMaxVersion + 1], where a "shard version" is the maximum chunk version existing on that shard for a collection.
This can be done in the update methods in the ReshardingCoordinatorService
- is depended on by
-
SERVER-51209 Fill in missing gaps in Resharding workflow to complete Milestone 1
- Closed
- related to
-
SERVER-52600 Reduce the amount of resharding code that gets included in the oplog library
- Closed