[SERVER-35695] Enable transactions on inMemory storage engine with a command line flag Created: 19/Jun/18 Updated: 29/Oct/23 Resolved: 23/Jul/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.2, 4.1.2 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | William Schultz (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||
| Backport Requested: |
v4.0
|
||||||||||||||||||||||||||||
| Sprint: | Repl 2018-07-16, Repl 2018-07-30 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Description |
|
In It's useful though for applications to run regression tests against the inMemory engine, as it's significantly faster than the wiredTiger engine, so disabling this has an effect on developer productivity. To satisfy both concerns, consider allowing transactions to be re-enabled for inMemory engine via command line, e.g. --setParameter inMemoryEnableTransactions |
| Comments |
| Comment by Githook User [ 14/Aug/18 ] |
|
Author: {'name': 'William Schultz', 'email': 'william.schultz@mongodb.com', 'username': 'will62794'}Message: (cherry picked from commit 826d21952137b50e6376cea627995d24a9eb54a9) |
| Comment by Githook User [ 23/Jul/18 ] |
|
Author: {'name': 'William Schultz', 'email': 'william.schultz@mongodb.com', 'username': 'will62794'}Message: |
| Comment by Jeffrey Yemin [ 05/Jul/18 ] |
|
Sounds perfect. We typically enable test command already for driver tests. |
| Comment by William Schultz (Inactive) [ 05/Jul/18 ] |
|
jeff.yemin What do you think about the possibility of enabling transactions on the inMemory storage engine only if test commands are enabled? |