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

Wangda Tan updated YARN-2800:
-----------------------------
    Description: 
In the past, we have a MemoryNodeLabelStore, mostly for user to try this 
feature without configuring where to store node labels on file system. It seems 
convenient for user to try this, but actually it causes some bad experiecne. 
User may add/remove labels, and edit capacity-scheduler.xml. After RM restart, 
labels will gone, (we store it in mem). And RM cannot start if we have some 
queue uses labels, and the labels don't exist in cluster.

As what we discussed, we should have an explicitly way to let user specify if 
he/she wants this feature or not. If node label is disabled, all operations 
trying to modify/use node labels will throw exception.

  was:Even though we have documented this, but it will be better to explicitly 
print a message in both RM/RMAdminCLI side to explicitly say that the node 
label being added will be lost across RM restart.


> Remove MemoryNodeLabelsStore and add a way to enable/disable node labels 
> feature
> --------------------------------------------------------------------------------
>
>                 Key: YARN-2800
>                 URL: https://issues.apache.org/jira/browse/YARN-2800
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: client, resourcemanager
>            Reporter: Wangda Tan
>            Assignee: Wangda Tan
>         Attachments: YARN-2800-20141102-1.patch, YARN-2800-20141102-2.patch
>
>
> In the past, we have a MemoryNodeLabelStore, mostly for user to try this 
> feature without configuring where to store node labels on file system. It 
> seems convenient for user to try this, but actually it causes some bad 
> experiecne. User may add/remove labels, and edit capacity-scheduler.xml. 
> After RM restart, labels will gone, (we store it in mem). And RM cannot start 
> if we have some queue uses labels, and the labels don't exist in cluster.
> As what we discussed, we should have an explicitly way to let user specify if 
> he/she wants this feature or not. If node label is disabled, all operations 
> trying to modify/use node labels will throw exception.



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

Reply via email to