-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: 2.5.4
-
Component/s: None
-
Labels:None
-
ALL
I provisioned a MongoDB 2.2.6 cluster with the following configuration :
- 2 shards with 3 nodes each
- 1 config server
- 1 mongos
I sharded some collections but didn't add any users or text/geospatial indexes.
I followed the upgrade instructions list 2.2 to 2.4 and 2.4 to 2.6.
When running through the downgrade process, I reversed the steps, that is :
- start a 2.4.9 mongos with --upgrade
- restarted the original mongos at 2.4.9
- restarted a downgraded config server
- did a rolling downgrade on the 3 nodes in the 2 shards
The 2.5.4 to 2.4.9 worked.
When I went to downgrade from 2.4.9 to 2.2.6, the steps failed at the mongos --upgrade step with the following error :
Wed Jan 22 21:49:04 warning: running with 1 config server should be done only for testing purposes and is not recommended for production Wed Jan 22 21:49:04 [mongosMain] MongoS version 2.2.6 starting: pid=46242 port=47017 64-bit host=jimoleary.local (--help for usage) Wed Jan 22 21:49:04 [mongosMain] git version: d626379119a6de9f2fb390780cf2fc336dfd540d Wed Jan 22 21:49:04 [mongosMain] build info: Darwin bs-osx-106-x86-64-2.10gen.cc 10.8.0 Darwin Kernel Version 10.8.0: Tue Jun 7 16:32:41 PDT 2011; root:xnu-1504.15.3~1/RELEASE_X86_64 x86_64 BOOST_LIB_VERSION=1_49 Wed Jan 22 21:49:04 [mongosMain] options: { configdb: "jimoleary.local:27024", logpath: "/Users/joleary/Documents/Support/2014-01-22/CS-10348/data/mongos2.4.9.log", port: 47017, upgrade: true } Wed Jan 22 21:49:04 [mongosMain] don't know how to upgrade 4 to 3 Wed Jan 22 21:49:04 [mongosMain] config server error: -8
Have I missed a step, the documentation is pretty sparse on this process.
I retried the steps again with 2.4.8 to see if that made any difference, unfortunately I got the same result.
Regards,
-Jim
- related to
-
-
- Closed
-