Some commands fail when a shard they need to talk to has no primary, even when they are okay to run on secondaries

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • ALL
    • Sharding 16 (06/24/16), Sharding 2020-04-20
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Some query-like commands (such as distinct) will fail when one of the shards it targets has no primary, even when using 'secondary' read preference.

        1. repro.js
          1 kB

            Assignee:
            Randolph Tan
            Reporter:
            Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: