[DOCS-2822] Comment on: "manual/tutorial/upgrade-revision.txt" Created: 28/Feb/14 Updated: 30/Oct/23 Resolved: 27/Jul/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ger Hartnett | Assignee: | Andrew Aldridge |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | collector-298ba4e7, sharding | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Location: http://docs.mongodb.org/manual/tutorial/upgrade-revision/ |
||
| Participants: | |
| Days since reply: | 7 years, 29 weeks ago |
| Description |
|
Please consider adding additional details/notes to the upgrade page. I think could be useful for some customers. Credit: These are based on notes in a ticket written by duraid.madina@10gen.com Upgrading the mongos query routersFor each mongos router you are running, simply stop it, upgrade it to 2.4.9, and then restart it. NOTE - Any client applications which are connected to a mongos will have their connections closed, and they will need to be restarted if they do not contain automatic retry logic. (Most applications already have such logic, as they will need to in order to perform automatic fail-over when a server goes down.) Upgrading the config serversFor each config server (starting with the last config server in your mongos --configdb) in turn:
Upgrading secondariesUpgrade each of the secondary mongod servers (and arbiters, if you have any) in every shard, as follows:
Upgrading primariesThis time, upgrade the primary mongod server for each shard, as follows:
Notes:
|
| Comments |
| Comment by Emily Hall [ 27/Jul/16 ] |
|
Closed for housekeeping on 7/27/2016 by Emily Hall. |