We observed a few failures in our CI system with this assertion message from ReshardingRecipientService::RecipientStateMachine::commit(). We had to inspect the state of the data directory to determine the actual recipient state at the time of the assertion. The proposed improvement here is to add the recipient state to the message.
Additionally, there is a similar assertion in the commit operation for the donor state.
- is related to
-
SERVER-57953 _flushReshardingStateChange attempts to refresh shard version while another refresh already pending, leading to invariant failure
-
- Closed
-