hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "zhihai xu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4201) AMBlacklist does not work for minicluster
Date Fri, 09 Oct 2015 06:57:26 GMT

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

zhihai xu commented on YARN-4201:

Thanks for the new patch [~hex108], I think it will be better to check {{scheduler.getSchedulerNode(nodeId)}}
not null to avoid NPE.
If {{scheduler.getSchedulerNode(nodeId)}} return null, it means the blacklisted node is just
removed from scheduler, I think it will be ok to not add a removed node to black List.

> AMBlacklist does not work for minicluster
> -----------------------------------------
>                 Key: YARN-4201
>                 URL: https://issues.apache.org/jira/browse/YARN-4201
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>            Reporter: Jun Gong
>            Assignee: Jun Gong
>         Attachments: YARN-4021.001.patch, YARN-4201.002.patch
> For minicluster (scheduler.include-port-in-node-name is set to TRUE), AMBlacklist does
not work. It is because RM just puts host to AMBlacklist whether scheduler.include-port-in-node-name
is set or not. In fact RM should put "host + port" to AMBlacklist when it is set.

This message was sent by Atlassian JIRA

View raw message