[SERVER-12445] Downgrading from 2.5.6 to 2.2.6 (through 2.4.9) fails Created: 22/Jan/14 Updated: 10/Dec/14 Resolved: 24/Jan/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.5.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | James O'Leary | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
I provisioned a MongoDB 2.2.6 cluster with the following configuration :
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 :
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 :
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, |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 24/Jan/14 ] |
|
This isn't supported. |