-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
ALL
-
-
Sharding NYC 2022-10-31, Sharding NYC 2022-11-14
-
20
_configsvrReshardCollection returns early and does not check for ongoing resharding operations if the new shard key is the same as the old shard key. The resharding coordinator service updates the shard key to the new shard key as part of persisting the commit decision.
This means that a _configsvrReshardCollection will return as if resharding has already completed as soon as the shard key for the collection is updated, even though the resharding operation is still ongoing. This resulted in BF-26453, where a config server stepdown after persisting the commit decision caused the ReshardCollectionCoordinator to retry the _configsvrReshardCollection command after step up and return immediately, before the state document could be deleted. This caused the ReshardingTestFixture to check for the state document too soon, and fail an assertion.
This issue was introduced by 08a4e5e as part of SERVER-62720, which coincides with the first time this issue was seen. Prior to this commit, the check for an existing resharding instance was performed before the check for a different shard key.
- is caused by
-
SERVER-62720 _configsvrReshardCollection can fail to join existing operation
- Closed