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 D2CEC18C73 for ; Mon, 17 Aug 2015 14:36:52 +0000 (UTC) Received: (qmail 14602 invoked by uid 500); 17 Aug 2015 14:36:46 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 14556 invoked by uid 500); 17 Aug 2015 14:36: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 14541 invoked by uid 99); 17 Aug 2015 14:36:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Aug 2015 14:36:46 +0000 Date: Mon, 17 Aug 2015 14:36:46 +0000 (UTC) From: "Rohith Sharma K S (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-4014) Support user cli interface in for Application Priority MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-4014?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D14699= 591#comment-14699591 ]=20 Rohith Sharma K S commented on YARN-4014: ----------------------------------------- bq. we can make updateApplicationPriority throw an ApplicationNotRunningExc= eption and let client catch the exception and prints =E2=80=9CApplication n= ot running =E2=80=9C msg In {{ClientRMService#updateApplicationPriority}}, update priority to schedu= ler will not be called if application is in NEW , NEW_SAVING also. So I fee= l having new exception ApplicationNotRunningException would lead to confusi= on. I think we can throw YarnException with message "Application in state cannot be update priority." Any thoughts? > Support user cli interface in for Application Priority > ------------------------------------------------------ > > Key: YARN-4014 > URL: https://issues.apache.org/jira/browse/YARN-4014 > Project: Hadoop YARN > Issue Type: Sub-task > Components: client, resourcemanager > Reporter: Rohith Sharma K S > Assignee: Rohith Sharma K S > Attachments: 0001-YARN-4014-V1.patch, 0001-YARN-4014.patch > > > Track the changes for user-RM client protocol i.e ApplicationClientProtoc= ol changes and discussions in this jira. -- This message was sent by Atlassian JIRA (v6.3.4#6332)