[SERVER-43378] Allow mongod to run on read-only media Created: 19/Sep/19 Updated: 10/May/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Security, Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Mark Brinsmead | Assignee: | Brian Lane |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Case: | (copied to CRM) |
| Description |
|
Allow mongod instance to be started on read-only filesystem or read-only media (e.g. WORM device) for archival or regulatory purposes. |
| Comments |
| Comment by Steven Vannelli [ 10/May/22 ] |
|
Moving this ticket to the Backlog and removing the "Backlog" fixVersion as per our latest policy for using fixVersions. |
| Comment by Brian Lane [ 19/Nov/19 ] |
|
Thanks mark.brinsmead - I figured. I can just set it to open for now, as I am not actively investigating this ticket if that was causing any confusion. |
| Comment by Mark Brinsmead [ 19/Nov/19 ] |
|
Hi, brian.lane. This was opened (meant to have been opened) as a feature request as much as anything. This customer (and maybe others) still wants to be able to have an instance (or maybe individual collections) on read-only media. It is possible that data-lake could meet some of that need, but I expect most used cases will still call for the same query performance as usual – just a guarantee that data cannot be modified. |
| Comment by Brian Lane [ 24/Sep/19 ] |
|
Hey mark.brinsmead, WiredTiger does already support a read-only mode. We would probably start from there and see what else is required. -Brian |