[SERVER-54704] Remove processAbortReasonNoDonorMachine() and processAbortReasonNoRecipientMachine() methods in resharding Created: 22/Feb/21  Updated: 29/Oct/23  Resolved: 22/Apr/21

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

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:
Related
related to SERVER-53611 Handle errors on donor before donor d... Closed
related to SERVER-56288 Don't wait for participant machine cr... Closed
is related to SERVER-54000 Make errors propagate from the Reshar... Closed
is related to SERVER-54513 Create new resharding recipient state... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2021-04-19, Sharding 2021-05-03
Participants:
Story Points: 2

 Description   

Prior to SERVER-54513, it was possible for a donor/recipient machine to not exist by the time the coordinator decides to abort - and the coordinator needed participants to report that they had seen the operation was being aborted. 

With SERVER-54513, the coordinator should know whether participant state machines have been made and whether it needs to wait for the participants to acknowledge the abort before completing.



 Comments   
Comment by Githook User [ 22/Apr/21 ]

Author:

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

Message: SERVER-54704 Remove processAbortReasonNoDonorMachine() and processAbortReasonNoRecipientMachine() methods in resharding
Branch: master
https://github.com/mongodb/mongo/commit/bc7b5da3d0d91eeb945f103d81f2cebd97f7d9f3

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