Loading...

XML

Word

Printable

JSON

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

Assigned Teams:

Sharding NYC
Story Points:
3
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

The coordinator observer will see the write to config.reshardingOperations and see that the write changes a shard to error. The coordinator will then update itself to the error state. Then it will refresh all shards. After all shards have returned that they've updated to the error state, the coordinator should indefinitely attempt to remove all resharding metadata that currently exists.

Also take care of all TODOS linked in ~~SERVER-53006~~ in this ticket, then close both in one commit. These TODOS are currently tied to the duplicated ticket ~~SERVER-51800~~.

duplicates

SERVER-54000 Make errors propagate from the ReshardingCoordinator to participants

Closed

has to be finished together with

SERVER-53006 Complete TODO listed in SERVER-51800

Closed

is duplicated by

SERVER-51800 Refresh both donor and recipient shards in case of resharding error state

Closed

Assignee:: [DO NOT USE] Backlog - Sharding NYC
Reporter:: Blake Oler
Participants:: [DO NOT USE] Backlog - Sharding NYC, Blake Oler
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Jul 16 2020 06:42:33 PM UTC
Updated:: Dec 06 2022 02:17:45 AM UTC
Resolved:: Mar 31 2021 11:44:47 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates