-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
v5.0
-
Sharding 2021-07-12
-
28
-
1
If one of the recipient-only shards happens to be chosen as the primary shard, and then the collection is sharded, subsequent movePrimary command leaves behind an empty source collection on the recipient shard. This can lead to ReshardingTest#_checkRecipientPostState() failing when the resharding operation isn't expected to succeed.
Running the movePrimary command before the shardCollection command avoids the issue described in SERVER-54231.
- is related to
-
SERVER-54231 Resharding can leave behind local collection on former primary shard that doesn't own any chunks
- Closed