Naganarasimha G R commented on YARN-3717:

Thanks for the feedback [~leftnoteasy],
bq. I didn't do this because I want late-binding, 
True makes sense. In case of priority, container's priority is not related to 
App's or queue's priority hence late binding will not be req there.
bq. I've thought about this also, it's not straight forward to me as well, user 
has to look at other configurations, it's not a big improvement comparing to 
show "<not-set>".
Well for a naive user will atleast know to what to look at. Or how about your 
idea of ??(For example, showing queue's label when the app's label doesn't set, 
bq. It will be very helpful, but if we want to do this, do we need to update 
REST API as well? Now it doesn't support get "ResourceUsage". I think we need 
it in both REST API (for YARN-3368) / CLI.
Ok, Will raise and start working on them. please inform if the priorty is more 
so that can finish them faster.

> 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