[DOCS-7598] Upgrade Config servers to CSRS - add mongos upgrade step first Created: 07/Apr/16 Updated: 11/Jan/17 Resolved: 25/Sep/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | mongodb-3.2 |
| Fix Version/s: | 01112017-cleanup |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Sumit Sengupta | Assignee: | Kay Kim (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | configserver, csrsupgrade, documentation | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 7 years, 20 weeks, 4 days ago |
| Description |
|
This came up at my last Consult gig. In the section for Upgrade config servers to 3.2 CSRS it does not say explicitly that a) before you upgrade configs to CSRS you need to upgrade mongos to 3.2. This should be step 1 - before stopping the balancer. In addition, there are two ways we advice to upgrade to CSRS- one with an outage and one without. These two sections can improve in two ways. 1) Since most of the steps are common, refer "without downtime" to the "with downtime" and mention only the differences to make it happen with no downtime. 2) I like the paragraph for the "without downtime" section clarifying that "no downtime" implies with some limitations --> "During this procedure there will be a period of time where the config servers will be read-only. During this period, certain catalog operations will fail if attempted..." - a similar section should exist for the "with downtime" section too. |
| Comments |
| Comment by Kay Kim (Inactive) [ 25/Sep/16 ] |
|
Already have the Prerequisite section. For 3.4, will update this page as part of deprecation of support for mirrored config server topology. |