hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jian He (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-4164) Retrospect update ApplicationPriority API return type
Date Wed, 04 Jan 2017 23:51:58 GMT

     [ https://issues.apache.org/jira/browse/YARN-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jian He updated YARN-4164:
--------------------------
    Fix Version/s: 2.8.0

> 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
>             Fix For: 2.8.0, 2.9.0, 3.0.0-alpha1
>
>         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)

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


Mime
View raw message