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

explicit primary read pref does not work well with shard versioning

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 2.3.1
    • 2.2.2, 2.3.1
    • Internal Client, Sharding
    • None
    • ALL

    Description

      The problem here is that when using replica set connections it is possible for mongos to use a different connection when setting the shard version and actually performing the query because of read preference. This means that the actual connection used when performing a query will be completely unversioned, totally bypassing the stale config version checking in the shard.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-7089 connection churn from mongos to mongod

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-6989 mongodump segfaults when host is passed a replSet string

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-10904 Possible for _master and _slaveConn to be pointing to different connections even with primary read pref

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              randolph@mongodb.com Randolph Tan
              randolph@mongodb.com Randolph Tan
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: