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

Honor read preference after replica fail-over in 2.4

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • 2.4.9
    • Sharding
    • None
    • Sharding
    • ALL

    Description

      If you read from a secondary through a mongos, and the underlying replica set has a fail-over, such that the secondary becomes a primary, mongos will still keep reading from that node, even though it is now in violation of the read preference. (Connections are pinned.)

      This behavior is fixed in 2.6, but not in the 2.4.x branch. It is suggested to backport the fix, or create a different fix in 2.4 such that read preferences are honored even in the face of replica fail-overs.

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            andre.spiegel@mongodb.com Andre Spiegel
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: