[DOCS-9498] Docs for SERVER-22443: The default storage engine should always work and be configurable Created: 05/Dec/16 Updated: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Emily Hall | Assignee: | Kay Kim (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| 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 |
|
Engineering Ticket Description: For 3.2, the default storage engine is wiredTiger, but it isn't really configurable (it's a string in the storage_options.h header). This leads to the unfortunate reality that 32 bit builds of mongodb 3.2 don't actually run without having --storageEngine passed to them. It would be preferred to have the default engine always runnable (so make mmapv1 the default on 32 bit) and further, it makes sense to have it be configurable (so system packagers could make the call where we hadn't yet) |
| 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! |