Some read-only operations (eg count,aggregate) hang indefinitely if the primary for the shard is unreachable from mongos

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • ALL
    • Sharding 2019-02-25
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

        1. primary_shard_server_blackholed_from_mongos.js
          2 kB

            Assignee:
            Blake Oler
            Reporter:
            Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: