hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bikas Saha (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-771) AMRMClient support for resource blacklisting
Date Thu, 29 Aug 2013 16:54:52 GMT

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

Bikas Saha commented on YARN-771:

The RM must handle anything input that the user sends to it. However, as the official client,
AMRMClient should only send valid input to the RM. IMO, having same node in both list at the
same invocation of AMRMClient.updateBlacklist() should be an error. Something is wrong with
the user and results may be unexpected. We should detect it and at least log a warning. Adding
and removing of nodes in different invocations of the method should result in the expected
behavior == the result of the last invocation. It should not be the case that the node ends
up in both lists since then the results are indeterminate (in this case the RM logic ends
up not blacklisting it).
> AMRMClient  support for resource blacklisting
> ---------------------------------------------
>                 Key: YARN-771
>                 URL: https://issues.apache.org/jira/browse/YARN-771
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Bikas Saha
>            Assignee: Junping Du
>         Attachments: YARN-771-v1.0.patch, YARN-771-v2.patch, YARN-771-v3.patch
> After YARN-750 AMRMClient should support blacklisting via the new YARN API's

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message