hadoop-yarn-issues mailing list archives

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

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

Sunil G commented on YARN-6156:
-------------------------------

Ideally when an AM container is allocated in a non-exclusive  node, we still consider nodes
count from AM RR's node partition. Now assume that AM is failed on that  node. And again AM
container is allocated in another non-exclusive node. So we are now +2 from old node count,
correct?

> 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