-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Sharding EMEA
-
Fully Compatible
-
Sharding EMEA 2023-02-20, Sharding EMEA 2023-03-06, Sharding EMEA 2023-03-20, Sharding EMEA 2023-04-03
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Different phases of the resilient movePrimary need specific cleanup procedures in the event a non-retryable error. On the other hand, in the event a retryable error, the failed phase must be always retried.
The goal of this ticket is to rely on the resilient cleanup infrastructure (SERVER-74185) and on the _mustAlwaysMakeProgress flag to properly handle movePrimary's failures.
- causes
-
SERVER-79189 Move primary coordinator silently exit on errors
-
- Closed
-