[
https://issues.apache.org/jira/browse/YARN-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14181771#comment-14181771
]
Naganarasimha G R commented on YARN-2495:
-----------------------------------------
hi [~wangda]
Actually what i meant was update the HeartBeatResponse abt the labels
acceptance by RM and once NodeStatusUpdater gets response(+ve or -ve) from RM
then it can set LabelsProvider with approp flag. But your logic seems to be
much better because i was handling thread sync unnecessarly in
ConfNodeLabelsProvider. Having this logic in Node status updater removes the
burden of each type of NodeLabelsProvider to have this sync logic and interface
will be simple in NodeLabelsProvider (earlier my thinking was labels should
not be handled by NodeStatusUpdater hence kept in nodeLabelsprovider)
Actually was about the upload the patch with my logic, as its not as per your
latest comments i will upload one more by tomorrow afternoon(IST) after
correction as per your comments
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
you meant NodeHeartBeatResponse right ?
> 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_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
(v6.3.4#6332)
