Return-Path: X-Original-To: apmail-hadoop-yarn-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 44F9817330 for ; Wed, 16 Sep 2015 05:35:47 +0000 (UTC) Received: (qmail 19039 invoked by uid 500); 16 Sep 2015 05:35:46 -0000 Delivered-To: apmail-hadoop-yarn-dev-archive@hadoop.apache.org Received: (qmail 18929 invoked by uid 500); 16 Sep 2015 05:35:46 -0000 Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-dev@hadoop.apache.org Delivered-To: mailing list yarn-dev@hadoop.apache.org Received: (qmail 18740 invoked by uid 99); 16 Sep 2015 05:35: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:35:46 +0000 Date: Wed, 16 Sep 2015 05:35:46 +0000 (UTC) From: "Rohith Sharma K S (JIRA)" To: yarn-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (YARN-4164) Retrospect update ApplicationPriority response API MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 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)