mongos find command should detect if a primary is down.

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 3.1.9
    • Affects Version/s: None
    • Component/s: Querying, Sharding
    • None
    • Fully Compatible
    • ALL
    • Hide

      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>

      Show
      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>
    • QuInt A (10/12/15)
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            David Storch
            Reporter:
            Misha Tyulenev (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: