hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohith Sharma K S (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4837) User facing aspects of 'AM blacklisting' feature need fixing
Date Fri, 18 Mar 2016 02:15:33 GMT

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

Rohith Sharma K S commented on YARN-4837:
-----------------------------------------

Adding to discussion about AM blacklisting, there are few corner cases where application can
get hanged forever. Especially after blacklisting some nodes, if other nodes removed from
the cluster. In such cases, there is no mechanism such that to remove blacklisted nodes for
AM. See YARN-4685 for one of the scenario.

> User facing aspects of 'AM blacklisting' feature need fixing
> ------------------------------------------------------------
>
>                 Key: YARN-4837
>                 URL: https://issues.apache.org/jira/browse/YARN-4837
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Vinod Kumar Vavilapalli
>
> Was reviewing the user-facing aspects that we are releasing as part of 2.8.0.
> Looking at the 'AM blacklisting feature', I see several things to be fixed before we
release it in 2.8.0.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message