Loading...

XML

Word

Printable

JSON

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

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding 2021-02-22, Sharding 2021-03-08
Linked BF Score:
18
Story Points:
2
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

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

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.

depends on

SERVER-50584 Serialize resharding errors into a new abortReason field

Closed

is duplicated by

SERVER-49578 Handle reported unrecoverable errors from donors/recipients in the coordinator

Closed

is related to

SERVER-54457 Resharding state transition log messages show misleading oldState attribute

Closed

related to

SERVER-52770 Add abortReshardCollection command for users to cancel the resharding operation

Closed

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

Closed

SERVER-54704 Remove processAbortReasonNoDonorMachine() and processAbortReasonNoRecipientMachine() methods in resharding

Closed

(1 related to)

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

Created:: Jan 22 2021 10:54:41 PM UTC
Updated:: Oct 29 2023 09:58:28 PM UTC
Resolved:: Feb 24 2021 04:47:42 PM UTC
Confidence Status Last Update:: 25/Jan/21 6:23 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates