hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Naganarasimha G R (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-2495) Allow admin specify labels in each NM (Distributed configuration)
Date Fri, 24 Oct 2014 14:04:34 GMT

     [ https://issues.apache.org/jira/browse/YARN-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Naganarasimha G R updated YARN-2495:
    Attachment: YARN-2495.20141024-1.patch

Hi [~wangda]
bq. Add a reject node labels list in NodeHeartbeatRequest – we may not have to handle this
list for now. But we can keep it on the interface
??rmContext.getNodeLabelManager().replaceLabelsOnNode(labelUpdate);?? currently throws exception
and hence felt that this message should be sent back to NM
instead of sending the invalid list (which requires interface changes in NodeLabelsManager).
So I was thinking of propagating Exception's errorMsg to NM by makiing use of NodeHeartbeatResponse.DiagnosticsMessage.
and will log this in NM
Have handled in this way please check the code ResourceTrackerService and NodeStatusUpdaterIMPL.(also
contains other changes which you mentioned yest)

> Allow admin specify labels in each NM (Distributed configuration)
> -----------------------------------------------------------------
>                 Key: YARN-2495
>                 URL: https://issues.apache.org/jira/browse/YARN-2495
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Wangda Tan
>            Assignee: Naganarasimha G R
>         Attachments: YARN-2495.20141023-1.patch, YARN-2495.20141024-1.patch, YARN-2495_20141022.1.patch
> Target of this JIRA is to allow admin specify labels in each NM, this covers
> - User can set labels in each NM (by setting yarn-site.xml or using script suggested
by [~aw])
> - NM will send labels to RM via ResourceTracker API
> - RM will set labels in NodeLabelManager when NM register/update labels

This message was sent by Atlassian JIRA

View raw message