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

Await replication after setting the featureCompatibilityVersion to 3.2 on the CSRS started by ShardingTest

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 3.3.15
    • None
    • Querying
    • None
    • Fully Compatible
    • ALL
    • TIG 2016-10-10
    • 0

    Description

      mongos uses the ReadPreference::Nearest read preference when initializing the config version on start-up. This leaves a window open where we've set the featureCompatibilityVersion to 3.2 on a majority of our config server nodes, but mongos chooses to read from a node that hasn't applied the update the admin.system.version collection and fails sees that the featureCompatibilityVersion is 3.4.

      We should update ShardingTest to await replication of the CSRS after setting the featureCompatibilityVersion of the CSRS to 3.2. This will ensure that mongos can connect to any of the nodes in the CSRS because they will all have featureCompatibilityVersion=3.2.

      Attachments

        Activity

          People

            max.hirschhorn@mongodb.com Max Hirschhorn
            max.hirschhorn@mongodb.com Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: