You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Rohith Sharma K S (JIRA)" <ji...@apache.org> on 2015/09/16 07:35:46 UTC
[jira] [Created] (YARN-4164) Retrospect update ApplicationPriority
response API
Rohith Sharma K S created YARN-4164:
---------------------------------------
Summary: Retrospect update ApplicationPriority response API
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
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)