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

Add an upgradeCheck for 3.0 upgrade to validate any breaking changes

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Diagnostics, Usability
    • None
    • Sharding

      It would be useful to have an upgradeCheck command similar to one that exists for 2.4 to 2.6 upgrade just for documents. Having an automated way to perform the pre-requisite validations for an upgrade across major versions is a better end-user experience than going through the compatibility list to validate what will break. A few samples from compatibility list that can be incorporated into the upgradeCheck are:

      • Auth schema pre-requisite
      • Collection name validation
      • Platform support
      • Background index check
      • dropDups checks for any of the index
      • SSL setting changes
      • Replica-set oplog format check

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            anil.kumar Anil Kumar
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: