Hadoop QA commented on YARN-2408:

{color:red}-1 overall{color}.  Here are the results of testing the latest 
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
                        Also please list what manual steps were performed to 
verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with 

    {color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in 

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4600//console

This message is automatically generated.

> Resource Request REST API for YARN
> ----------------------------------
>                 Key: YARN-2408
>                 URL: https://issues.apache.org/jira/browse/YARN-2408
>             Project: Hadoop YARN
>          Issue Type: New Feature
>          Components: webapp
>            Reporter: Renan DelValle
>            Priority: Minor
>              Labels: features
>         Attachments: YARN-2408.patch
> I’m proposing a new REST API for YARN which exposes a snapshot of the 
> Resource Requests that exist inside of the Scheduler. My motivation behind 
> this new feature is to allow external software to monitor the amount of 
> resources being requested to gain more insightful information into cluster 
> usage than is already provided. The API can also be used by external software 
> to detect a starved application and alert the appropriate users and/or sys 
> admin so that the problem may be remedied.
> Here is the proposed API:
> {code:xml}
> <resourceRequests>
>   <MB>96256</MB>
>   <VCores>94</VCores>
>   <appMaster>
>     <applicationId>application_</applicationId>
>     <applicationAttemptId>appattempt_</applicationAttemptId>
>     <queueName>default</queueName>
>     <totalPendingMB>96256</totalPendingMB>
>     <totalPendingVCores>94</totalPendingVCores>
>     <numResourceRequests>3</numResourceRequests>
>     <resourceRequests>
>       <request>
>         <MB>1024</MB>
>         <VCores>1</VCores>
>         <resourceName>/default-rack</resourceName>
>         <numContainers>94</numContainers>
>         <relaxLocality>true</relaxLocality>
>         <priority>20</priority>
>       </request>
>       <request>
>         <MB>1024</MB>
>         <VCores>1</VCores>
>         <resourceName>*</resourceName>
>         <numContainers>94</numContainers>
>         <relaxLocality>true</relaxLocality>
>         <priority>20</priority>
>       </request>
>       <request>
>         <MB>1024</MB>
>         <VCores>1</VCores>
>         <resourceName>master</resourceName>
>         <numContainers>94</numContainers>
>         <relaxLocality>true</relaxLocality>
>         <priority>20</priority>
>       </request>
>     </resourceRequests>
>   </appMaster>
> </resourceRequests>
> {code}

This message was sent by Atlassian JIRA

Reply via email to