[SERVER-22443] The default storage engine should always work and be configurable Created: 02/Feb/16 Updated: 05/Apr/17 Resolved: 11/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | 3.3.1 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mira Carey | Assignee: | DO NOT USE - Backlog - Platform Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Participants: | |||||||||
| 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 Mira Carey [ 11/Nov/16 ] |
|
Gone away because we no longer support 32 bit builds |