explicit primary read pref does not work well with shard versioning

XMLWordPrintableJSON

    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

        1. unshard.js
          1 kB
          Randolph Tan

              Assignee:
              Randolph Tan
              Reporter:
              Randolph Tan
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: