[DOCS-10441] Comment on: "manual/tutorial/upgrade-config-servers-to-replica-set" Created: 27/Jun/17 Updated: 27/Oct/23 Resolved: 29/Jun/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Carsten Strauss | Assignee: | Unassigned |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Location: https://docs.mongodb.com/v3.2/tutorial/upgrade-config-servers-to-replica-set/ |
||
| Participants: | |
| Days since reply: | 6 years, 32 weeks, 6 days ago |
| Description |
|
First paragraph says: To deploy config servers as a replica set, the config servers must run the WiredTiger storage engine. Then in step 4: If the config server is using MMAPv1, start 3 new mongod instances. WTF? |
| Comments |
| Comment by Kay Kim (Inactive) [ 29/Jun/17 ] |
|
|
| Comment by Carsten Strauss [ 29/Jun/17 ] |
|
Okay, resolved |
| Comment by Kay Kim (Inactive) [ 27/Jun/17 ] |
|
Hey Carsten – the first paragraph is referring to the resulting CSRS at the end of the tutorial, as in when the config servers are running as a replica set, they must be running WT storage engine. The config servers of the existing sharded clusters (they are mirrored config servers) could be running MMAPv1 (or could be WT). Hope this helps. |