Naganarasimha G R updated YARN-2729:
    Attachment: YARN-2729.20151023-1.patch

Thanks [~rohithsharma] & [~sunilg], for the comments . I have updated the patch 
with the approach specified. but i have a query.
bq.  If you call super.serviceStop() first, D1 clean up will not happen first 
rather, D1(D,C,B,A)-cleanup D1 which is at the end.
I could not get the above statement clearly, IIUC  the order would be either 
*D1,D,C,B,A* when {{super.serviceStop()}} is called first and *D,D1,C,B,A* when 
{{super.serviceStop()}} is called at the last. Latter is what we are trying to 
achieve earlier, correct me if i am wrong. 

> Support script based NodeLabelsProvider Interface in Distributed Node Label 
> Configuration Setup
> -----------------------------------------------------------------------------------------------
>                 Key: YARN-2729
>                 URL: https://issues.apache.org/jira/browse/YARN-2729
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager
>            Reporter: Naganarasimha G R
>            Assignee: Naganarasimha G R
>         Attachments: YARN-2729.20141023-1.patch, YARN-2729.20141024-1.patch, 
> YARN-2729.20141031-1.patch, YARN-2729.20141120-1.patch, 
> YARN-2729.20141210-1.patch, YARN-2729.20150309-1.patch, 
> YARN-2729.20150322-1.patch, YARN-2729.20150401-1.patch, 
> YARN-2729.20150402-1.patch, YARN-2729.20150404-1.patch, 
> YARN-2729.20150517-1.patch, YARN-2729.20150830-1.patch, 
> YARN-2729.20150925-1.patch, YARN-2729.20151015-1.patch, 
> YARN-2729.20151019.patch, YARN-2729.20151023-1.patch, 
> YARN-2729.20151310-1.patch, YARN-2729.20151310-2.patch
> Support script based NodeLabelsProvider Interface in Distributed Node Label 
> Configuration Setup . 
> Miscellaneous Issues :
> # In configurationNodeLabelsProvider instead of taking multiple labels from 
> single configuration, we need to support exclusive configuration for 
> partition (single label).
> # Proper logging when registration of Node Fails
> # Classloader was not getting reset from custom class loader in 
> TestConfigurationNodeLabelsProvider.java which could make test cases fail in 
> certain conditions
> # In ResourceTrackerService we need to consider distributed configuration 
> only when node labels are enabled. leads to lots of logs in certain conditions
> # NodeLabelsProvider needs to be a interface rather than  abstract class 

This message was sent by Atlassian JIRA

Reply via email to