[SERVER-24486] Clarification w.r.t mongo upgrade from 2.6 to 3.2 Created: 09/Jun/16 Updated: 14/Jul/16 Resolved: 09/Jun/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 2.6.5 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Rajkumar Kalaiselvam | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Could you please elaborate on actual reason behind the below mentioned 2 step process for upgrading mongo version from 2.6 to 3.2 version ? From "https://docs.mongodb.com/manual/release-notes/3.2-upgrade/" page Do we need to follow this procedure even if we are shutting down the existing process (mongo version 2.6) and roll out a new mongo instance in 3.2 version with the existing data ? Sorry if its sounds a trivial question, just try to clear my head around on this one. |
| Comments |
| Comment by Ramon Fernandez Marina [ 09/Jun/16 ] |
|
While you may be able to upgrade a standalone node from 2.6 to 3.2 as you describe, it is neither recommended nor supported. The reason to request the upgrade to 3.0 first is to ensure replica sets can be upgraded in a rolling fashion without downtime. Because of internal changes, 2.6 and 3.2 nodes are not guaranteed to be able to operate together in a replica set. You can read about the compatibility changes for 3.0 and for 3.2 for more details. As you know, the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag, where your question will reach a larger audience. See also our Technical Support page for additional support resources. Regards, |