[SERVER-50584] Serialize resharding errors into a new abortReason field Created: 27/Aug/20  Updated: 29/Oct/23  Resolved: 28/Jan/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.9.0

Type: Task Priority: Major - P3
Reporter: Blake Oler Assignee: Haley Connelly
Resolution: Fixed Votes: 0
Labels: PM-234-M3, PM-234-T-error-flow
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-54000 Make errors propagate from the Reshar... Closed
Related
related to SERVER-49909 Error if resharding's oplog applicati... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2021-01-25, Sharding 2021-02-08
Participants:
Story Points: 2

 Description   

What needs to be done:

  • Serialize caught errors in the run()::onError handler and persist to config.localReshardingOperations.
  • Add an error field to recipient/donor array on entries on the coordinator document idl. This error field should be able to hold an error code and the string associated with it. When a donor/recipient receives an error that is unrecoverable, it will indefinitely attempt to majority write the error, along with a change to the error state, to its own array entry on the coordinator's config.reshardingOperations document.

 

Also:



 Comments   
Comment by Githook User [ 28/Jan/21 ]

Author:

{'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}

Message: SERVER-50584 Serialize resharding errors into a new abortReason field
Branch: master
https://github.com/mongodb/mongo/commit/3d60f67f2086e93403bada5c0ced25b4bad62782

Generated at Thu Feb 08 05:23:02 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.