[
https://issues.apache.org/jira/browse/YARN-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15863368#comment-15863368
]
Bibin A Chundatt commented on YARN-6156:
----------------------------------------
{quote}
However if some resource are obtained from any such node, we have to increase
and update nodes count to SimpleBlacklistManager and then decrease node count
when resources are removed.
{quote}
AM allocation will always be with 1 container so {{resource removed}} means
either will container is kill or failed and thr is probability of getting added
to blacklisted nodes list.
The scenario that could cause issue is when all AM containers are getting
allocated to non-exclusive , failing and added to blacklist. Blacklisted nodes
considers non-exclusive and Total nodes its excluded. Will look into it again
how to handle.
> 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: [email protected]
For additional commands, e-mail: [email protected]
