-
Type:
New Feature
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Storage Engines - Foundations
-
1,242.42
-
StorEng - Defined Pipeline
-
None
On occasion, WiredTiger has evergreen failures due to out of disk space failures. This ticket involves adding a new configuration where we can limit the disk space of a specific test run. The idea is that when we reach the configured disk space, we stop inserting or doing operations can could potentially increase the disk size. This is just a proof of concept idea. It would be highly valuable if the investigation ends up being completed with a solution.
This ticket investigates if it is feasible to limit the disk space of a test/format run and implements the solution.
- is depended on by
-
WT-16127 test/format copy_on_file fails with ENOENT
-
- Blocked
-
-
WT-12921 failed: format-stress-test-2-nonstandalone on ubuntu2004-stress-tests [wiredtiger-mongo-v7.0 @ eed05eb5]
-
- Blocked
-
-
WT-18086 __posix_file_write: failed to write : No space left on device
-
- Blocked
-
-
WT-14092 format-stress-test-2 ran out of disk space
-
- Closed
-
- related to
-
WT-16127 test/format copy_on_file fails with ENOENT
-
- Blocked
-
-
WT-12921 failed: format-stress-test-2-nonstandalone on ubuntu2004-stress-tests [wiredtiger-mongo-v7.0 @ eed05eb5]
-
- Blocked
-