Naganarasimha G R commented on YARN-5256:

Thanks [~wangda], was expecting this hence waited :)
Yes i was of the same opinion when [~sunilg] came with the first patch. but 
later during discussion with him felt that once we come up with Constraints 
(YARN-3409) it might be required to treat them differently and separate API's 
to retrieve the constraints and the partition label info separately. So based 
on how the constraint label comes up we need to shape the API. As per the 
offline discussion with [~sunilg] he informed me that he requires a solution 
for this jira to meet the Newe UI dead lines so i am ok with going with the 
other approach.
Few options in this approach
* would be good to have both the {{labelName}} and {{associated nodes info}}  
as params instead of path variable (similar to current patch to fetch 
information for set of labels)
* Would be need to return the used resource info ? we need to fetch from 
scheduler ? i presume not required every time right? any plans in UI ?


> Add REST endpoint to support detailed NodeLabel Informations
> ------------------------------------------------------------
>                 Key: YARN-5256
>                 URL: https://issues.apache.org/jira/browse/YARN-5256
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: webapp
>            Reporter: Sunil G
>            Assignee: Sunil G
>         Attachments: YARN-5256-YARN-3368.1.patch, 
> YARN-5256-YARN-3368.2.patch, YARN-5256.0001.patch, YARN-5256.0002.patch, 
> YARN-5256.0003.patch
> Add a new REST endpoint to fetch few more detailed information about node 
> labels such as resource, list of nodes etc.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to