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

Test that 3.2 mongos fails to join a featureCompatibilityVersion("3.4") cluster

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.4.0-rc1
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Query 2016-10-10, Query 2016-10-31

      Description

      Once SERVER-26264 is complete, a 3.2 mongos process will quickly exit with an error status if you point it at 3.4 config servers with featureCompatibilityVersion "3.4". We should write a test in the multiVersion suite to verify this behavior. The test should perform the following steps:

      1. Start an all 3.4 sharded cluster.
      2. Verify that the feature compatibility version is "3.4".
      3. Assert that a new 3.2 mongos fails to start up when joining the cluster.
      4. Set the feature compatibility version to "3.2".
      5. Assert that a 3.2 mongos can now start up against the cluster and can perform reads and writes to the shards.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              maria.vankeulen Maria van Keulen
              Reporter:
              david.storch David Storch
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: