You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Naganarasimha G R (JIRA)" <ji...@apache.org> on 2015/04/04 21:45:33 UTC

[jira] [Updated] (YARN-2923) Support configuration based NodeLabelsProvider Service in Distributed Node Label Configuration Setup

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

Naganarasimha G R updated YARN-2923:
------------------------------------
    Attachment: YARN-2923.20150404-1.patch

Rebasing the patch based on changes in yarn-2729 
[~john.jian.fang]
bq. BTW, would the labels in RM persist some somewhere to handle RM restart and how about the failover in HA case then?  Would the labels are reported to both RMs or there is a shared label store (or in the shared RM state store)?
Well in case of distributed configuraton, Every time NM Registers we are sending the Labels, so on restart or HA it gets automatically handled and we are not persisting to a store .

bq. BTW, seems to me it is not a good idea to periodically check the configuration file. Why not monitor the configuration file by some file watcher instead? Furthermore, HADOOP-7001 defines an API to reload the configuration without restart. Would it possible to integrate HADOOP-7001 with your jira?
Thanks for the feed back, had a look at the watcher API, generally changes in the file/ directory is identified internally by polling mechanism so i feel its almost as the same approach as we take and it would involve additional effort of finding the path to the yarn-site.xml. and wrt  HADOOP-7001, there too, to find whether the configuration is changed or not they do not use watchers and they too do {{new Configuration}}, and we do not have multiple configurations and hence felt current interface we have is simpler and lighter but i am still open for modifications if any precise benefit i can see and also would like to get some opinion on this from [~wangda] too 

> Support configuration based NodeLabelsProvider Service in Distributed Node Label Configuration Setup 
> -----------------------------------------------------------------------------------------------------
>
>                 Key: YARN-2923
>                 URL: https://issues.apache.org/jira/browse/YARN-2923
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager
>            Reporter: Naganarasimha G R
>            Assignee: Naganarasimha G R
>             Fix For: 2.8.0
>
>         Attachments: YARN-2923.20141204-1.patch, YARN-2923.20141210-1.patch, YARN-2923.20150328-1.patch, YARN-2923.20150404-1.patch
>
>
> As part of Distributed Node Labels configuration we need to support Node labels to be configured in Yarn-site.xml. And on modification of Node Labels configuration in yarn-site.xml, NM should be able to get modified Node labels from this NodeLabelsprovider service without NM restart



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)