[DOCS-8423] Docs recommend incorrect order for upgrading a sharded cluster Created: 25/Jul/16  Updated: 30/Oct/23  Resolved: 10/Aug/16

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Bug Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 7 years, 27 weeks ago
Story Points: 0.25

 Description   

The Upgrade Sharded Clusters tutorial still says to upgrade the mongoses first. This was true from 1.6 through 3.0, but in 3.2 and onward you must upgrade the mongods before the mongos. The preferred upgrade order is now the config servers first, then the shards, then the mongoses.



 Comments   
Comment by Githook User [ 10/Aug/16 ]

Author:

{u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}

Message: DOCS-8423 point release upgrade procedure for sharded clusters
Branch: master
https://github.com/mongodb/docs/commit/c49120ff32a23738a4b000e8fcd0681bd11101aa

Generated at Thu Feb 08 07:56:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.