-
Type: Improvement
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Internal Client
-
None
-
Environment:2.2.0
2 node replica set in shard s2. Take down the primary so there's no longer a majority. It's possible to connect to the remaining node and do slaveOk() reads. It is not possible, however, to read from the secondary using mongos, even when you set read preference to "secondary":
mongos> db.nov1.find().readPref("secondary") error: { "$err" : "socket exception [CONNECT_ERROR] for s2/localhost:47017,localhost:47018", "code" : 11002 }
This is related, but think overall a different issue than the startup problem.
- duplicates
-
SERVER-6664 mongos won't create a new connection to a replica set with the primary down
- Closed
-
SERVER-7246 Mongos cannot do slaveOk queries when primary is down
- Closed
- is related to
-
SERVER-2478 can't start usable mongos if replSet shard lacks a master
- Closed