hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varun Saxena (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6156) AM blacklistdisableThreshold consider node partition count
Date Tue, 14 Feb 2017 03:57:41 GMT

    [ https://issues.apache.org/jira/browse/YARN-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15865001#comment-15865001
] 

Varun Saxena commented on YARN-6156:
------------------------------------

[~bibinchundatt], we need not initialize amNodeLabelExpression to null outside if condition
in getApplicableNodeCountForAM methods. Also no need of check for unmanaged AM in RMAppAttemptImpl#getApplicableNodeCountForAM
as the method will be called from within a check for unmanaged AM.
These methods are quite similar in both RMAppImpl and RMAppAttemptImpl but I guess its fine
as we do not need to explicitly get app from the applications map.

> AM blacklistdisableThreshold  consider node partition count
> -----------------------------------------------------------
>
>                 Key: YARN-6156
>                 URL: https://issues.apache.org/jira/browse/YARN-6156
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Bibin A Chundatt
>            Assignee: Bibin A Chundatt
>         Attachments: YARN-6156.0001.patch, YARN-6156.0002.patch
>
>
> As per the current implementation for AM blacklisting disabling is based on completed
custer resource.
> Incase of partitioned cluster, nodes applicable for AM labels only should be considered
as total nodes.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message