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

Using read preference causes stale version info

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: 2.2.4
    • Fix Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Operating System:
      ALL

      Description

      For a sharded setup there are stale config version issues when read preference primary is used.
      This problem appears to go away when read preference is removed. The logs when this problem happens indicate that when a stale config is detected mongos is using a different connection when calling setShardVersion and then doing the query.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                charlie.page@10gen.com Charlie Page
                Participants:
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: