Vinod Kumar Vavilapalli commented on YARN-2495:

bq. Well as craig informed, RegisterNodeManagerRequestProto.nodeLabels is 
already a set but as by default empty set is provided by protoc, its req to 
inform whether labels are set as part of request hence areNodeLabelsSetInReq is 
It's just that I don't like this _areNodeLabelsSetInReq_ flag in the protocol. 
Are there other ways of achieving this?

bq.  Well i am little confused here, As per wangda's earlier comment i 
understand that it was your comment to send shutdown (which i felt correct in 
terms of maintenance)
I think treating invalid labels as a disaster case will be, well, a disaster. 
How about we let the node run (just like we let an unhealthy node run) and 
report it in the diagnostics? I'm okay keeping that same behavior during 
registration too.

> Allow admin specify labels from 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.20141024-1.patch, 
> YARN-2495.20141030-1.patch, YARN-2495.20141031-1.patch, 
> YARN-2495.20141119-1.patch, YARN-2495.20141126-1.patch, 
> YARN-2495.20141204-1.patch, YARN-2495.20141208-1.patch, 
> YARN-2495.20150305-1.patch, YARN-2495.20150309-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 (YARN-2923) or 
> using script suggested by [~aw] (YARN-2729) )
> - 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

Reply via email to