Naganarasimha G R commented on YARN-3717:

Thanks for the review [~wangda], 
bq.  we can show it like "<not set>", otherwise it will cause confusion if the 
am's nodeLabelExpression = "", but it inherits queue's 
Actually wanted to discuss with you regarding this, recently while working on 
Application Priority, came across that, if the priority for application is not 
set in the submission context, then Queue's/cluster max priority is set to the 
submission context and also while updating the app they do the same thing. Hope 
we could follow the same approach for node labels too. As it would be easy to 
analyze. If not other option is to indicate if app label is null, then in the 
web ui( also rest? )  show as *<Queue's Default Node Label>*.  Also for AM as 
*<Application Node Label's Expression>*
bq. show "DEFAULT_PARTITION" when an app's label="", to make it consistent with 
queue's page.
Sure, it makes sense but what abt REST ? need to follow the same right ?
bq. QueueCLI#printQueueInfo to print <DEFAULT_PARTITION> when it's ""/null? 
OK, will get this done, but should we not support additional CLI similar to the 
lines of UI to get the Queue stats based on NodeLabel? 

> Expose app/am/queue's node-label-expression to RM web UI / CLI / REST-API
> -------------------------------------------------------------------------
>                 Key: YARN-3717
>                 URL: https://issues.apache.org/jira/browse/YARN-3717
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Naganarasimha G R
>            Assignee: Naganarasimha G R
>         Attachments: 3717_cluster_test_snapshots.zip, RMLogsForHungJob.log, 
> YARN-3717.20150822-1.patch, YARN-3717.20150824-1.patch, 
> YARN-3717.20150825-1.patch, YARN-3717.20150826-1.patch
> 1> Add the default-node-Label expression for each queue in scheduler page.
> 2> In Application/Appattempt page  show the app configured node label 
> expression for AM and Job

This message was sent by Atlassian JIRA

Reply via email to