[SERVER-27571] Support WiredTiger custom filesystem feature Created: 04/Jan/17 Updated: 06/Dec/22 Resolved: 19/Feb/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 3.4.0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Deyoung Hong | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Description |
|
I'm implementing a custom filesystem on a block device supported by WiredTiger. |
| Comments |
| Comment by Eric Milkie [ 19/Feb/19 ] |
|
We can revisit this if custom filesystems become a supported feature in MongoDB. |
| Comment by Eric Milkie [ 04/Jan/17 ] |
|
As you have discovered, MongoDB does not currently support the Custom Filesystem feature of WiredTiger. I'll convert this ticket into a feature request to be triaged. |
| Comment by Deyoung Hong [ 04/Jan/17 ] |
|
I should also mention that the same problem exists for the DB data path. In order to support custom filesystem, all file POSIX APIs and system commands (e.g. rm, rmdir, mkdir, etc.) should be replaced. There are other native directories and files created under the DB data path directory during MongoDB run that should not be there when using custom filesystem. |