[SERVER-24110] Explicit control over directories created under dbpath by mongod Created: 09/May/16 Updated: 06/Dec/22 Resolved: 27/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mark Helmstetter | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Do | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Participants: | |||||||||
| Description |
|
mongod currently creates/uses subdirectories under the dbpath:
Specifying journalPath is already covered by SERVER-13455. For a number of reasons it would be desirable to make these paths user defined. One case would be when applying security and/or encryption policies for these directories. Note that currently the _tmp directory will be removed when the server starts. This can also be problematic when attempting to apply such a policy. |
| Comments |
| Comment by Tzach Yarimi [ 16/Jan/19 ] |
|
Hello, This feature could be very helpful for my team (using 3.6), since we store the journal and _tmp folders on different devices for performance improvements. Today we have to hack a solution by mounting these folders to the different drives, which can be challenging if we want to use the device for multiple purposes + MongoDB is deleting the _tmp folder on startup, and this requires additional effort to overcome. Any estimated completion time? Tzach |