- 
    Type:Task 
- 
    Resolution: Fixed
- 
    Priority:Major - P3 
- 
    Affects Version/s: None
- 
    Component/s: None
- 
        Fully Compatible
- 
        Sharding 2022-09-19, Sharding 2022-10-03
- 
        3
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
Currently if we add a new shard with the same replica set name and configuration as an existing shard, addShard does not report that as an error and does a no-op. To give a better user experience, we should give users some indication that an existing shard with the same name/config is already part of the cluster.