[SERVER-73929] Improve the resilient movePrimary's error handling Created: 13/Feb/23  Updated: 29/Oct/23  Resolved: 23/Mar/23

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 7.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Antonio Fuschetto Assignee: Antonio Fuschetto
Resolution: Fixed Votes: 0
Labels: PM-2144-Milestone-0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
causes SERVER-79189 Move primary coordinator silently exi... Closed
Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-02-20, Sharding EMEA 2023-03-06, Sharding EMEA 2023-03-20, Sharding EMEA 2023-04-03
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 23/Mar/23 ]

Author:

{'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}

Message: SERVER-73929 Improve the resilient movePrimary's error handling
Branch: master
https://github.com/mongodb/mongo/commit/a0c9ffb2cee79bffb071c877d39272efad293e76

Generated at Thu Feb 08 06:26:01 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.