[
https://issues.apache.org/jira/browse/MESOS-2825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14740066#comment-14740066
]
Jeffrey Schroeder commented on MESOS-2825:
------------------------------------------
Out of curiosity, roughly where would the code for this live? I wrote a patch
for ossec[1] to do something very similar for low priority cpu bound tasks
8-ish years ago. C++ is not one of my primary programming languages, but I'd be
happy to give it a go if it isn't too hard an someone would help me iterate on
it.
It very likely isn't much more than calling the ioprio_set(2) syscall in the
context that does the heavy IO bits on Linux. No idea if we would want to
support this on OS X or Windows. It would also give me an excuse to hack on
Mesos.
[1] https://groups.google.com/forum/#!msg/ossec-dev/4fC3r0QyoBw/d9YC7mG58J4J |
http://www.digitalprognosis.com/opensource/patches/ossec/ossec-make-syscheckd-use-SCHED_BATCH-on-Linux.patch
> Run heavy disk IO operations at low IO priority
> -----------------------------------------------
>
> Key: MESOS-2825
> URL: https://issues.apache.org/jira/browse/MESOS-2825
> Project: Mesos
> Issue Type: Improvement
> Components: isolation
> Affects Versions: 0.23.0
> Reporter: Ian Downes
> Assignee: Yan Xu
> Priority: Minor
> Labels: twitter
>
> Slave IO operations on large images can be disruptive to tasks, e.g.,
> decompressing, decrypting, hashing, and extracting. Provide option to run
> such operations at a lower IO priority, i.e., at "idle" or by explicitly
> setting the "best effort" priority to less than the tasks', e.g., 0 as the
> lowest best effort priority. All of the existing operations in the Appc
> provisioner are run as Subprocesses.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
