[SERVER-20456] mongos find command should detect if a primary is down. Created: 17/Sep/15  Updated: 07/Oct/15  Resolved: 21/Sep/15

Status: Closed
Project: Core Server
Component/s: Querying, Sharding
Affects Version/s: None
Fix Version/s: 3.1.9

Type: Bug Priority: Major - P3
Reporter: Misha Tyulenev Assignee: David Storch
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Steps To Reproduce:

Running jstest/sharding/mongos_rs_shard_failure_tolerance.js with useClientClusterCursor = true will produce the error

"$err" : "network error while attempting to run command 'find' on host <host:port>

Sprint: QuInt A (10/12/15)
Participants:

 Description   

Currently if primary or shard goes down when a query is executed then the exception bubbles up on mongos with useClientClusterCursor = true.
Instead it should be:
a) find command: caught and retried according to read preferences
b) getMore command: return an error. This is a change from the current behavior where getMore returns no documents.



 Comments   
Comment by Githook User [ 21/Sep/15 ]

Author:

{u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}

Message: SERVER-20456 inform ReplicaSetMonitor of unreachable host and re-target in new mongos read path
Branch: master
https://github.com/mongodb/mongo/commit/4e3f36d5e1c4d55e3c950456cef6da531ab72eff

Generated at Thu Feb 08 03:54:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.