-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
Fully Compatible
-
ALL
-
v7.3, v7.0, v6.0, v5.0
-
Cluster Scalability 2024-3-18, Cluster Scalability 2024-4-1
-
120
In the case a failover occurs while the reshardingRecipientService is aborting but hasn't deleted its state document yet, we hit this invariant here on stepUp. (Check BF-32038 for more details)
Reassess the behavior of the recipient during stepUp for this edge case.
- related to
-
SERVER-89161 Refactor state transition handling for resharding participants
- Closed
-
SERVER-88938 Make resharding unittest AbortAfterStepUpWithAbortReasonFromCoordinator more robust
- Closed