Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9216817388 for ; Wed, 16 Sep 2015 05:44:46 +0000 (UTC) Received: (qmail 36162 invoked by uid 500); 16 Sep 2015 05:44:46 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 36048 invoked by uid 500); 16 Sep 2015 05:44:46 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 35849 invoked by uid 99); 16 Sep 2015 05:44:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Sep 2015 05:44:46 +0000 Date: Wed, 16 Sep 2015 05:44:46 +0000 (UTC) From: "Rohith Sharma K S (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-4164) Retrospect update ApplicationPriority API return type MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-4164: ------------------------------------ Summary: Retrospect update ApplicationPriority API return type (was: Retrospect update ApplicationPriority response API) > 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 > > 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)