[SERVER-52837] Gracefully shut down resharding state machines on stepdown/shutdown Created: 12/Nov/20  Updated: 06/Dec/22  Resolved: 31/Mar/21

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

Type: Task Priority: Major - P3
Reporter: Blake Oler Assignee: [DO NOT USE] Backlog - Sharding NYC
Resolution: Duplicate Votes: 0
Labels: PM-234-M3, PM-234-O-unspecialized, PM-234-T-error-flow
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-54460 Resharding may delete the state docum... Closed
Assigned Teams:
Sharding NYC
Participants:
Story Points: 1

 Description   

The distributed algorithms underpinning resharding should be fine to pick up on another replica set node after a stepdown/shutdown. Accordingly, the only thing that needs to be done when one of these error types is thrown is to catch the error in an onError handler in the run function, log, and silently return.

It's possible that tenant migration has already solved this. Check in with their team/code.


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