Wangda Tan commented on YARN-2800:

Thanks for mention about YARN-1326, I think we should also add 
RMNodeLabelsManager being using to the web UI.
But the case of mem-based node labels manager is a little different from 
mem-based RM state store.
If user configured mem-based RM state store, apparently, after restart, all 
states will gone, but the RM can still be able to launch and start serving. But 
if user configured mem-based node labels manager, user may add labels to queue 
configurations, when RM will be failed to launch (specifically, CS cannot 
initialize) if a queue use a label but not existed in node labels manager -- 
That is more annoying than mem-based RM state store case. 

So I still prefer continuously printing WARN logs at every time user trying to 
do any modification on node label manager to let admin know about that. Do you 
think does it make sense to you? Please share your opinions.


> Should print WARN log in both RM/RMAdminCLI side when 
> MemoryRMNodeLabelsManager is enabled
> ------------------------------------------------------------------------------------------
>                 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
> 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.

This message was sent by Atlassian JIRA

Reply via email to