hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohith Sharma K S (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4164) Retrospect update ApplicationPriority API return type
Date Fri, 18 Dec 2015 05:43:46 GMT

    [ https://issues.apache.org/jira/browse/YARN-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15063518#comment-15063518
] 

Rohith Sharma K S commented on YARN-4164:
-----------------------------------------

Looking into the HadoopQA result, 
bq. -1	cc	16m 49s	root-jdk1.8.0_66 with JDK v1.8.0_66 generated 2 new issues (was 16, now
16).
Not caused by this patch
bq. -1	javac	25m 36s	root-jdk1.7.0_91 with JDK v1.7.0_91 generated 1 new issues (was 723,
now 723).
Not caused by this patch

And test failures are not related this patch. 
YARN side test case failure JIRA's are tracked by umbrella jira YARN-4478
MapReduce test case failure are tracked by MAPREDUCE-6580 and MAPREDUCE-6579

> Retrospect update ApplicationPriority API return type
> -----------------------------------------------------
>
>                 Key: YARN-4164
>                 URL: https://issues.apache.org/jira/browse/YARN-4164
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Rohith Sharma K S
>            Assignee: Rohith Sharma K S
>         Attachments: 0001-YARN-4164.patch, 0002-YARN-4164.patch, 0003-YARN-4164.patch,
0004-YARN-4164.patch
>
>
> Currently {{ApplicationClientProtocol#updateApplicationPriority()}} API returns empty
UpdateApplicationPriorityResponse response.
> But RM update priority to the cluster.max-priority if the given priority is greater than
cluster.max-priority. In this scenarios, need to intimate back to client that updated  priority
rather just keeping quite where client assumes that given priority itself is taken.
> During application submission also has same scenario can happen, but I feel when 
> explicitly invoke via ApplicationClientProtocol#updateApplicationPriority(), response
should have updated priority in response. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message