[DOCS-7323] Highlight authorization and authorization (meta)data is also transient in the In-Memory Storage Engine Created: 02/Mar/16 Updated: 30/Oct/23 Resolved: 28/Apr/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Raul Marin-Perez | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 7 years, 41 weeks, 6 days ago | ||||||||
| Description |
|
Hi there, I'm in a customer and we thought that using the In-Memory Storage Engine would be a nice feature to use (https://jira.mongodb.org/browse/HELP-1834). After reading the documentation, we thought only application data is not persisted to disk and it's gone after restarts. What we didn't expect was that authentication and authorization (meta)data was going to be lost as well. I think it could be helpful to highlight that not only data, but metadata stored in MongoDB (such as authentication and authorization), will be gone after restarting the instance. |
| Comments |
| Comment by Githook User [ 28/Apr/16 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |