[
https://issues.apache.org/jira/browse/YARN-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13594794#comment-13594794
]
Thomas Graves commented on YARN-443:
------------------------------------
Can you elaborate on your proposal. Are you saying use a yarn config and then
pass an argument into the container executor or do something actually higher up
like call nice when calling the container-executor? What do you propose for
the DefaultContainerExecutor since it could run across multiple platforms and
all it does is call a bash script?
I figured with it in the container-executor itself each one could more easily
decide if it applies and how exactly to implement it. I also like the fact that
I can change it without rebooting the NM.
> allow OS scheduling priority of NM to be different than the containers it
> launches
> ----------------------------------------------------------------------------------
>
> Key: YARN-443
> URL: https://issues.apache.org/jira/browse/YARN-443
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: nodemanager
> Affects Versions: 2.0.3-alpha, 0.23.6
> Reporter: Thomas Graves
> Assignee: Thomas Graves
> Attachments: YARN-443.patch
>
>
> It would be nice if we could have the nodemanager run at a different OS
> scheduling priority than the containers so that you can still communicate
> with the nodemanager if the containers out of control.
> On linux we could launch the nodemanager at a higher priority, but then all
> the containers it launches would also be at that higher priority, so we need
> a way for the container executor to launch them at a lower priority.
> I'm not sure how this applies to windows if at all.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
