[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. |
| 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: |