[
https://issues.apache.org/jira/browse/YARN-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358109#comment-14358109
]
Wangda Tan commented on YARN-2495:
----------------------------------
Hi [~Naganarasimha],
For areNodeLabelsSetInReq, one appoarch to avoid it is, you can add a PB
structure (like NodeLabelsProto, could placed in yarn_protos.proto, like
NodeIdToLabelsProto), which contains {{repeated string nodeLabels}}. It will be
a part of RegisterProto and HeartbeatProto, and it could be null. "Null" means
not set, agree?
Regarding the invalid node label issue of registration/hearbeating, bring down
the whole cluster when label is invalid is a serious problem as mentioned by
Craig, maybe you can:
If label(s) of a node being reporting is invalid, we can
- Show/log diagnostic in RM (nodes) page and NM page, saying label is invalid.
(Need modify web UI, can be done in a separated task)
- Make the node's labels to be empty, so that applications can continue use it.
Thanks,
> Allow admin specify labels from 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.20141030-1.patch, YARN-2495.20141031-1.patch,
> YARN-2495.20141119-1.patch, YARN-2495.20141126-1.patch,
> YARN-2495.20141204-1.patch, YARN-2495.20141208-1.patch,
> YARN-2495.20150305-1.patch, YARN-2495.20150309-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 (YARN-2923) or
> using script suggested by [~aw] (YARN-2729) )
> - 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
(v6.3.4#6332)
