[DOCS-6298] Provide some detail about the directory structure and files expected for WiredTiger dbPath Created: 29/Sep/15 Updated: 30/Oct/23 Resolved: 01/Nov/22 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Andrew Ryder (Inactive) | Assignee: | Kay Kim (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 1 year, 14 weeks, 1 day ago | ||||
| Epic Link: | DOCSP-1769 | ||||
| Description |
|
We do not seem to have an public facing information regarding the expected layout of the files in the dbPath for WiredTiger. Aside from this being useful just to predict what to expect, it would also be beneficial to understand where sensitive information might be present for the purposes of auditing and encryption. Ideally, it would be nice to have a list of the names of each file that might be created (or their name pattern as needed) and a rough guide to the types of data that each retains. |
| Comments |
| Comment by Education Bot [ 01/Nov/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |
| Comment by David Hows [ 29/Sep/15 ] |
|
I think it may be worthwhile adding a single reference page describing the metadata files (and dbfiles) for MongoDB first party storage engines. This kind of information is really valuable for anyone doing security analysis around a MongoDB instance in their environment. |