-
Type:
Bug
-
Resolution: Done
-
Priority:
Critical - P2
-
Affects Version/s: 2.0.7, 2.1.2
-
Component/s: Admin, Replication, Sharding
-
None
-
ALL
-
None
-
0
-
None
-
None
-
None
-
None
-
None
-
None
-
None
If mongos starts but fails to connect, or has errors connecting to, to any replica members in the set, meaning none of them, it will update the shard config and remove the existing seed members. We should not persist the seed list if it is empty.
>db.shards.find()
{_id:"shard1", host:"shard1/"}
- is related to
-
-
- Closed
-
-
SERVER-5058 mongos should update config seed based on rs version
-
- Closed
-