-
Type:
New Feature
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
None
-
Catalog and Routing
-
🟩 Routing and Topology
-
None
-
None
-
None
-
None
-
None
-
None
Today, shard servers will loop in their startup until at least one of the config server members is available to read from. It would be better for replication purposes if a mongod --shardsvr secondary could continue applying oplog entries even if the entire config server replica set is unavailable to it.
- is depended on by
-
SERVER-111849 MongoD can be unable to start up if all nodes of the CSRS are replaced
-
- Closed
-
- is duplicated by
-
SERVER-111849 MongoD can be unable to start up if all nodes of the CSRS are replaced
-
- Closed
-
- related to
-
SERVER-112250 Add test that omitting --shardsvr enables mongod to continue applying oplog entries with zero connectivity to config server replica set
-
- Closed
-