[SERVER-25972] Usability testing for ANSA when shards have an existing incorrect shardIdentity document Created: 06/Sep/16  Updated: 19/Nov/16  Resolved: 20/Sep/16

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

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Esha Maharishi (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File ansa_usability_script.js    
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2016-09-19, Sharding 2016-10-10
Participants:

 Description   

There are two scenarios where an incorrect shardIdentity document can matter.
1) When adding a new shard, if there is already a shardIdentity document on the shard, and it doesn't match the one that is attempted to be added during the addShard process.

2) When the shard is already a part of a sharded cluster, but somehow the shardIdentity document is incorrect and doesn't match what is sent by mongos in setShardVersion.

For both cases we should manually double-check that things fail the way we expect them to, and with reasonable error messages that would be clear to a user and to our support team if a user somehow got themselves into one of those states.


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