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 0188E10073 for ; Mon, 14 Sep 2015 14:39:54 +0000 (UTC) Received: (qmail 22836 invoked by uid 500); 14 Sep 2015 14:39:47 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 22792 invoked by uid 500); 14 Sep 2015 14:39:47 -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 22776 invoked by uid 99); 14 Sep 2015 14:39:47 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Sep 2015 14:39:47 +0000 Date: Mon, 14 Sep 2015 14:39:47 +0000 (UTC) From: "Jason Lowe (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-4141) Runtime Application Priority change should not throw exception for applications at finishing states 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-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14743602#comment-14743602 ] Jason Lowe commented on YARN-4141: ---------------------------------- When the user tries to verify the priority they will get an app report showing the job is in a terminal state which will explain why the priority isn't updated. This is akin to killing an application that already completed. We don't retroactively mark it as killed, and we also don't report an error to the user when they tried to kill the terminated application. > Runtime Application Priority change should not throw exception for applications at finishing states > --------------------------------------------------------------------------------------------------- > > Key: YARN-4141 > URL: https://issues.apache.org/jira/browse/YARN-4141 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager > Reporter: Sunil G > Assignee: Sunil G > Attachments: 0001-YARN-4141.patch, 0002-YARN-4141.patch > > > As suggested by [~jlowe] in [MAPREDUCE-5870-comment|https://issues.apache.org/jira/browse/MAPREDUCE-5870?focusedCommentId=14737035&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14737035] , its good that if YARN can suppress exceptions during change application priority calls for applications at its finishing stages. > Currently it will be difficult for clients to handle this. This will be similar to kill application behavior. -- This message was sent by Atlassian JIRA (v6.3.4#6332)