-
Type:
Bug
-
Resolution: Works as Designed
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
ALL
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The command abortReshardCollection calls abort on the resharding coordintor. The abort function takes in a param called "skipQuiescePeriod" which allows the caller to specify if the coordinator should transition to kQuiesced or kDone upon completion. The distinction between the two is that kQuiesced will retain the coordinator state doc on disk whereas kDone will remove the state doc. Note: despite this param, a coordinator can only enter the kQuiesced state if the reshardCollection request provided a reshardingUUID.
Currently, abortReshardCollection does not specify "skipQuiescePeriod" when calling abort on the coordinator leading it to default to false. As a result, abortReshardCollection leaves the coordinator doc in a quiesced state, which is incorrect behavior. The abortReshardCollection should be setting skipQuiescePeriod to true because there is no need to quiesce the coordinator doc after an user issued abort.
This bug also exists in ConfigsvrCleanupReshardCollectionCommand as the
ReshardingCoordinatorCleaner also aborts the coordinator without specifying "skipQuiescePeriod".