You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2017/10/03 19:57:00 UTC
[jira] [Commented] (YARN-7285) ContainerExecutor always launches
with priorities due to yarn-default property
[ https://issues.apache.org/jira/browse/YARN-7285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16190238#comment-16190238 ]
Jason Lowe commented on YARN-7285:
----------------------------------
YARN-5444 first reported the test failure, but it was misinterpreted as a problem in the unit test rather than a problem introduced in yarn-default.xml.
> ContainerExecutor always launches with priorities due to yarn-default property
> ------------------------------------------------------------------------------
>
> Key: YARN-7285
> URL: https://issues.apache.org/jira/browse/YARN-7285
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 2.8.0, 2.9.0
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Priority: Minor
>
> ContainerExecutor will launch containers with a specified priority if a priority adjustment is specified, otherwise with the OS default priority if it is unspecified. YARN-3069 added yarn.nodemanager.container-executor.os.sched.priority.adjustment to yarn-default.xml, so it is always specified even if the user did not explicitly set it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org