[SERVER-19576] Ability to select which storage engines to build (Wiredtiger or MMAPv1) Created: 24/Jul/15 Updated: 06/Dec/22 Resolved: 29/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | 3.1.6 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Anup Halarnkar | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Done | Votes: | 1 |
| Labels: | feature | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
RHEL - 7.1 / PPC64LE |
||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
I am using the following system I have built 3.1.7-pre successfully on this system. Also, the tests execute successfully barring 1 error(server_options_test) for unittests. All tests related to dbtest and jscore tests pass. The commands are as given on link https://www.mongodb.org/about/contributors/tutorial/test-the-mongodb-server/ But when I execute these tests using "--storageEngine=mmapv1" I get a lot of errors. There seems to be portability issues for MMAPv1 across PPC64LE. It would be a great relief to build all test suites using WiredTiger storage engine as it would save a lot of time that would otherwise be invested in porting MMAPv1. Thanks in advance, |
| Comments |
| Comment by Geert Bosch [ 29/Jul/19 ] |
|
With the removal of the MMAPv1 storage engine in MongoDB v4.2, this option is no longer relevant. |