[SERVER-593] read only mode Created: 01/Feb/10  Updated: 05/Dec/16  Resolved: 02/Mar/16

Status: Closed
Project: Core Server
Component/s: Stability
Affects Version/s: None
Fix Version/s: 3.3.3

Type: New Feature Priority: Major - P3
Reporter: Eliot Horowitz (Inactive) Assignee: Adam Midvidy
Resolution: Done Votes: 11
Labels: mms-s
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Documented
is documented by DOCS-9564 Docs for SERVER-593: read only mode Closed
Duplicate
is duplicated by SERVER-9963 Support readonly (filesystem) mode Closed
Related
Backwards Compatibility: Fully Compatible
Participants:

 Description   

for mongod and tools with --dbpath



 Comments   
Comment by Adam Midvidy [ 01/Mar/16 ]

This ticket is only tracking the ability to start MongoD on a read-only filesystem, Transitioning from a writable to read-only filesystem while MongoD is already running is being tracked in SERVER-10556

Comment by Yuri Finkelstein [ 17/Aug/13 ]

The file system status can change from writable to read-only (see CS-8424).
So, additional requirement here is to monitor this status and exit gracefully minimizing potential downtime in the replica set in case this node is primary.

Comment by Scott Hernandez (Inactive) [ 17/Jul/13 ]

If the filesystem is read-only and there are journal files to apply they will need to be applied in memory. This will be case when the files are on a (read-only) snapshot FS, or read-only mounted from a backup, for example.

Comment by Scott Hernandez (Inactive) [ 19/Jun/13 ]

Description from dup:

Add support for the server to start without creating or writing any files. If the filesystem is mounted, or files are, read-only this mode would allow starting the server.

This mode would also be useful when using tools in dbpath mode where they read the raw database files, instead of working in client/server mode.

For people doing snapshot backups (like LVM) which can be mounted read-only this option would allow running the server against the snapshot without making an additional copy. This is a little more tricky if there are journal entries to commit before the files are useable or if there is a lock file and no journal (see SERVER-7861).

Generated at Thu Feb 08 02:54:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.