Details
-
Epic
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
None
-
None
-
None
-
None
-
Disk I/O Isolation
Description
Currently there is no disk isolation in place and this affects an executor to be starved of disk when another disk heavy operation such as copying a multi gigabyte file is being performed by another executor.
At Twitter, the executor performs a few fsync operations and has specific wait periods for these operations to succeed. When these operations take longer than expected during termination of tasks, it would potentially result in LOST tasks.
Attachments
Issue Links
- duplicates
-
MESOS-1979 Implement Block IO throttling in disk isolator
- Open