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

Fix shardingtest upgradeCluster function to reflect 3.2 upgrade process

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • Sharding
    • ALL
    • Sharding 10 (02/19/16)

    Description

      Shardingtest upgradeCluster upgrades mongos first and this hence the two step upgrade process is needed in jstests because mongos can not connect to mongod 3.0 or less.
      Need to fix the upgradeCluster to choose the upgrade order depending of the version it upgrades to.

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            misha.tyulenev@mongodb.com Misha Tyulenev
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: