[SERVER-30814] removeShard returns ShardNotFound if step-up/step-down occurs Created: 24/Aug/17  Updated: 06/Dec/22  Resolved: 05/Jan/18

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

Type: Bug Priority: Major - P3
Reporter: Hugh Han Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-32553 The `removeShard` command is not idem... Backlog
Assigned Teams:
Sharding
Operating System: ALL
Sprint: Sharding 2017-09-11
Participants:

 Description   

When removeShard is called during a step-up/step-down, the primary config node could finish removing the shard, but not return the response.

In this case, the next time removeShard is called, the new primary config node will return ShardNotFound instead of DrainingStatus::Completed, since the shard has already been removed.


Generated at Thu Feb 08 04:25:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.