[DOCS-5011] Add note on experimental in-memory storage engine Created: 16/Mar/15 Updated: 11/Jan/17 Resolved: 15/Oct/15 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | mongodb-3.0 |
| Fix Version/s: | 01112017-cleanup |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Stennie Steneker (Inactive) | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 2 |
| Labels: | storage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 8 years, 17 weeks, 6 days ago | ||||
| Description |
|
Some of the press activity and 3.0 talks mention the experimental in-memory storage engine but there is no info in docs on how to test this out. The current implication is that mmapv1 and wiredTiger are the only valid storage options: http://docs.mongodb.org/manual/reference/configuration-options/#storage.engine. We should add a note with appropriate caveats on usage:
|
| Comments |
| Comment by Stennie Steneker (Inactive) [ 15/Oct/15 ] |
|
The in-memory experiment in 3.0 is an unsupported and rather quick prototype that isn't a fully formed feature. This is entirely different to the production inMemory storage engine under development for Closing this issue to avoid conflating the two approaches. |