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

Config server meta-data upgrade from 2.2.3 to 2.4.0 fails with "could not create new collection"

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Environment:
      CentOS 6/64-bit. Three virtual machines (mongo-a1, mongo-a2, mongo-a3) each running a shard instance, config server instance, and mongos instance.
    • Linux
    • Hide

      Start with a 2.2.3 mongodb cluster. Try running "mongos --upgrade" using a 2.4.0 version of mongos.

      Show
      Start with a 2.2.3 mongodb cluster. Try running "mongos --upgrade" using a 2.4.0 version of mongos.
    • None
    • 0
    • None
    • None
    • None
    • None
    • None
    • None

      I'm trying to upgrade a 2.2.3 cluster to 2.4.0 (final) following the "Upgrade a Sharded Cluster from MongoDB 2.2 to MongoDB 2.4" instructions here: http://docs.mongodb.org/manual/release-notes/2.4-upgrade/

      See SERVER-9036 for more info

            Assignee:
            Unassigned Unassigned
            Reporter:
            mike@cloudmeter.com Michael Dickey
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: