[
https://issues.apache.org/jira/browse/YARN-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13597154#comment-13597154
]
Thomas Graves commented on YARN-443:
------------------------------------
I intended to leave that log message in there because if anything comes back on
stderr from try running the container, it goes into the exception but then its
never logged. I'll actually go ahead and remove that and file a follow up jira
as ideally any message would go into the diagnostics that get returned to the
user also.
I'll fix the typo for than and commit.
> 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-branch-0.23.patch, YARN-443-branch-0.23.patch,
> YARN-443-branch-0.23.patch, YARN-443-branch-0.23.patch,
> YARN-443-branch-2.patch, YARN-443-branch-2.patch, YARN-443-branch-2.patch,
> YARN-443.patch, YARN-443.patch, YARN-443.patch, YARN-443.patch,
> YARN-443.patch, YARN-443.patch, 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
