Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-23625

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

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • ALL
    • Sharding 2019-02-25

    Description

      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.

      Attachments

        Activity

          People

            blake.oler@mongodb.com Blake Oler
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: