-
Type:
New Feature
-
Resolution: Won't Fix
-
Priority:
Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: Storage
-
Labels:None
-
Storage Execution
Currently, low disk space conditions only cause write operations to fail when the actual attempt to get/use more disk space from the OS fails. It would help (operationally) if writes could additionally fail when the amount of free disk space falls below some configurable threshold (eg. 10GB). This would leave some disk space as headroom that can be used to restore service, as opposed to the alternative of a filesystem that is either completely full or has a uselessly small amount of free space (eg. under 2GB).
A simple workaround for this (and the behaviour that I'm effectively asking for) is to allocate on disk a large dummy file of the desired size. This will cause the filesystem to fill up "early", and if this happens the dummy file can be deleted to gain access to the "spare" disk space.
- is duplicated by
-
SERVER-18967 Failed to start MongoD after hitting out of disk space
-
- Closed
-
-
-
- Closed
-
- is related to
-
SERVER-18963 Make directory per DB the default for WT
-
- Closed
-
- related to
-
DOCS-5651 Update production notes to cover disk space/ running out of it
-
- Closed
-