[SERVER-9044] Config server meta-data upgrade from 2.2.3 to 2.4.0 fails with "could not create new collection" Created: 21/Mar/13 Updated: 10/Dec/14 Resolved: 21/Mar/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Michael Dickey | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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. |
||
| Operating System: | Linux |
| Steps To Reproduce: | Start with a 2.2.3 mongodb cluster. Try running "mongos --upgrade" using a 2.4.0 version of mongos. |
| Participants: |
| Description |
|
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 |
| Comments |
| Comment by Michael Dickey [ 21/Mar/13 ] |
|
This is a duplicate, accidentally uploaded public. It's just a test cluster so not a big deal, but please delete this if you can. |