-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
None
-
ALL
-
Sharding 2019-02-25
Even if you specify a 'secondary' read preference, we still try to call setShardVersion on the primary when running count, agg, m/r, etc. If the replica set monitor has already detected that the primary is unreachable then we skip the setShardVersion call and it works. If we have not yet detected that the node we knew to once be primary has since become unreachable, we'll try to send setShardVersion to it, and that will hang forever.
- duplicates
-
SERVER-35679 General Interruption Facility
- Closed
- is related to
-
SERVER-24457 Some commands fail when a shard they need to talk to has no primary, even when they are okay to run on secondaries
- Closed
- related to
-
SERVER-23427 Add test to ensure that read-only operations against the config db continue to work if the config server primary is unreachable from mongos
- Closed
-
SERVER-17825 Remove setShardVersion from shard version protocols
- Closed
-
SERVER-21005 Consistent maxTimeMs / timeout / interruption support
- Closed