[SERVER-54000] Make errors propagate from the ReshardingCoordinator to participants Created: 22/Jan/21  Updated: 29/Oct/23  Resolved: 24/Feb/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: Haley Connelly 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
depends on SERVER-50584 Serialize resharding errors into a ne... Closed
Duplicate
is duplicated by SERVER-49578 Handle reported unrecoverable errors ... Closed
Related
related to SERVER-52770 Add abortReshardCollection command fo... Closed
related to SERVER-53611 Handle errors on donor before donor d... Closed
related to SERVER-54704 Remove processAbortReasonNoDonorMachi... Closed
is related to SERVER-54457 Resharding state transition log messa... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2021-02-22, Sharding 2021-03-08
Participants:
Linked BF Score: 18
Story Points: 2

 Description   

While SERVER-50584 will introduce the abortReason field and propagates errors from the shard back to the main CoordinatorDocument.recipient/donorShards[shard].abortReason on the configsvr, onReshardingFieldsChanges() for the participant state machines do not propagate errors sent from the coordinator yet.



 Comments   
Comment by Githook User [ 23/Feb/21 ]

Author:

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

Message: SERVER-54000 Make errors propagate from the ReshardingCoordinator to participants

SERVER-54457 Resharding state transition log messages use correct 'oldState'
Branch: master
https://github.com/mongodb/mongo/commit/6abf5d917e5f5aac880c3201c17bf6749ddd2f55

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