[SERVER-24214] Validate shardIdentity document of proposed shard when adding a shard that already exists Created: 19/May/16  Updated: 26/Oct/23

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

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: PM-108, oldshardingemea
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-22660 OpObserver on config server for inser... Closed
is related to SERVER-24213 Make addShard return success if attem... Closed
Assigned Teams:
Catalog and Routing
Participants:

 Description   

After SERVER-24213 we will be returning success when running addShard for a shard that already exists. Rather than just accepting the shard name and replica set name matching an existing shard, we should also contact the proposed shard, read its shardIdentity document, and verify that the relevant information matches what we expect for the existing shard (clusterId, shardId, etc)


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