[SERVER-41871] Provide a mechanism to remove a shard and also abandon its chunks Created: 21/Jun/19  Updated: 06/Dec/22  Resolved: 03/Jan/20

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

Type: Improvement Priority: Major - P3
Reporter: Mira Carey Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-40118 Allow users to initiate the replica s... Closed
Assigned Teams:
Sharding
Sprint: Sharding 2019-09-09
Participants:

 Description   

Currently there is no way to remove a shard from a cluster without migrating the chunks on that shard away to other shards. This makes it impossible to remove a shard which is entirely lost (because we can't move the chunks away because we don't have them). We also can't introduce a new repl set on top of that shard, because it'll have the wrong term.

We should provide a mechanism to update the routing table such that:

  • A given shard is removed
  • Chunk info for chunks on that shard is removed
  • key space for sharded collections on that shard are re-allocated to other shards (so as to avoid leaving gaps in the routing table)
  • the shard in question is completely unavailable

We will add a new option to the removeShard command that puts a shard into forced draining mode in order to provide the above.



 Comments   
Comment by Sheeri Cabral (Inactive) [ 03/Jan/20 ]

We have abandoned this project.

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