Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 5.0.0-rc0
Affects Version/s: None
Component/s: Sharding
Labels:
- PM-234-M3
- PM-234-T-error-flow

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding 2021-04-19, Sharding 2021-05-03
Story Points:
2
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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.

is related to

SERVER-54000 Make errors propagate from the ReshardingCoordinator to participants

Closed

SERVER-54513 Create new resharding recipient state kAwaitingFetchTimestamp

Closed

related to

SERVER-53611 Handle errors on donor before donor document is initially inserted

Closed

SERVER-56288 Don't wait for participant machine creation in resharding_abort_command.js

Closed

Assignee:: Haley Connelly
Reporter:: Haley Connelly
Participants:: Githook User, Haley Connelly
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Feb 22 2021 06:02:54 PM UTC
Updated:: Oct 29 2023 09:57:11 PM UTC
Resolved:: Apr 22 2021 07:19:53 PM UTC
Confidence Status Last Update:: 22/Mar/21 7:06 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates