-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
Sharding 2020-12-28, Sharding 2021-01-11
-
35
-
1
During the teardown of the resharding fixture, we find that the donor document still exists when we expect it to have been already deleted. Because the ReshardingCoordinatorService will complete after waiting for donors to transition to kDone and we don't remove the donor document until after the donor transitions to kDone, it is possible that the donor document removal may not be seen immediately after the reshardCollection completes.
We can fix this issue if we change the failing assertion to an assert.soon. We also need to change the recipient document deletion assertion to an assert.soon as well.
- related to
-
SERVER-52620 Update resharding_replicate_updates_as_insert_delete.js to use reshardCollection command
- Closed