Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-2227 create upgrade guide for mongodb-2.6
  3. DOCS-2070

Add notes about 2.6 --upgrade on a sharded cluster

    XMLWordPrintableJSON

Details

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • mongodb-2.6
    • None
    • Server
    • None

    Description

      It's pretty much the same with 2.4 with the following changes:

      1. Turning off the balancer is not actually required, but we probably want to train our users to always do this during upgrades.
      2. There are no actual changes other than the config.version document.
      3. Mongos should be upgraded first (important!) before mongod. Order does not matter if the user can ensure that no collections will be dropped while upgrading all mongos to 2.6.
      4. No 2.2 process can be in the cluster to run --upgrade. And no new processes older than 2.4 should join after the upgrade completes.

      Attachments

        Activity

          People

            zack.brown@10gen.com Zack Brown
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              10 years, 18 weeks, 6 days ago