[DOCS-12231] 3.6 and 4.0 oplog resize procedures only work for WT Created: 03/Dec/18 Updated: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kevin Pulo | Assignee: | Ravind Kumar (Inactive) |
| Resolution: | Won't Do | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Days since reply: | 1 year, 14 weeks, 2 days ago | ||||||||||||
| Epic Link: | DOCSP-1769 | ||||||||||||
| Description |
DescriptionIn 3.6 the Oplog Resize procedure was changed from "standalone-drop-recreate" to the replSetResizeOplog command. However, this command only works for the WiredTiger storage engine, and will fail if attempted on an MMAPv1 replica set member. This is only a problem in the 3.6 and 4.0 docs, because MMAPv1 support is being removed in 4.2. Scope of changesUpdate replSetOplogResize + oplog resize pages to point to the 3.4 resize oplog instructions for users on MMAPv1, call out upcoming MMAPv1 deprecation and guide to rolling to WT. |
| Comments |
| Comment by Education Bot [ 31/Oct/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |
| Comment by Kevin Pulo [ 03/Dec/18 ] |
|
More specifically, although there is this note:
the page doesn't indicate what to do on members which aren't running WT. (Also there's a stray apostrophe |