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 29AC6183D9 for ; Tue, 13 Oct 2015 17:40:11 +0000 (UTC) Received: (qmail 81527 invoked by uid 500); 13 Oct 2015 17:40:06 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 81483 invoked by uid 500); 13 Oct 2015 17:40:06 -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 81470 invoked by uid 99); 13 Oct 2015 17:40:05 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Oct 2015 17:40:05 +0000 Date: Tue, 13 Oct 2015 17:40:05 +0000 (UTC) From: "Siddharth Seth (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-4207) Add a non-judgemental YARN app completion status 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-4207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14955334#comment-14955334 ] Siddharth Seth commented on YARN-4207: -------------------------------------- [~rhaase] - thanks for taking this up. Along with the change to FinalApplicationStatus, a change is also required to the proto definition (yarn_protos.proto). There'll be a set of converter methods which translate between the proto and FinalApplicationStatus which will also need to be changed. Other than that, I believe adding this additional value is a safe change. > Add a non-judgemental YARN app completion status > ------------------------------------------------ > > Key: YARN-4207 > URL: https://issues.apache.org/jira/browse/YARN-4207 > Project: Hadoop YARN > Issue Type: Improvement > Reporter: Sergey Shelukhin > Labels: trivial > Attachments: YARN-4207.patch > > > For certain applications, it doesn't make sense to have SUCCEEDED or FAILED end state. For example, Tez sessions may include multiple DAGs, some of which have succeeded and some have failed; there's no clear status for the session both logically and from user perspective (users are confused either way). > There needs to be a status not implying success or failure, such as "done"/"ended"/"finished". -- This message was sent by Atlassian JIRA (v6.3.4#6332)