[ https://issues.apache.org/jira/browse/YARN-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14948914#comment-14948914 ]
zhihai xu commented on YARN-4201: --------------------------------- Thanks for the patch [~hex108]! It is a good catch. Should we use {{SchedulerNode#getNodeName}} to get the blacklisted node name? We can add {{getSchedulerNode}} to {{YarnScheduler}}, So we can call {{getSchedulerNode}} to look up the the SchedulerNode using NodeId in {{RMAppAttemptImpl}}. > 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 > > > 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 (v6.3.4#6332)