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 C11F1172B9 for ; Wed, 25 Mar 2015 20:19:06 +0000 (UTC) Received: (qmail 63453 invoked by uid 500); 25 Mar 2015 20:18:54 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 63405 invoked by uid 500); 25 Mar 2015 20:18:54 -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 63391 invoked by uid 99); 25 Mar 2015 20:18:53 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Mar 2015 20:18:53 +0000 Date: Wed, 25 Mar 2015 20:18:53 +0000 (UTC) From: "Vrushali C (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-3044) [Event producers] Implement RM writing app lifecycle events to ATS 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-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14380675#comment-14380675 ] Vrushali C commented on YARN-3044: ---------------------------------- bq. Well i too had the same doubt whether we need to capture very minute part of the life cycle events as present in the RMAppState(/YarnApplicationState) and RMAppAttemptState. That is the reason i had posted earlier but Sangjin Lee had opined to start of with the basic ones hence provided this patch. Based on the input from all will add other required states What is the reasoning behind capturing some but not all application lifecycle state changes? I believe we should not be selectively filtering out capturing of application lifecycle state changes in the next gen timeline service. > [Event producers] Implement RM writing app lifecycle events to ATS > ------------------------------------------------------------------ > > Key: YARN-3044 > URL: https://issues.apache.org/jira/browse/YARN-3044 > Project: Hadoop YARN > Issue Type: Sub-task > Components: timelineserver > Reporter: Sangjin Lee > Assignee: Naganarasimha G R > Attachments: YARN-3044.20150325-1.patch > > > Per design in YARN-2928, implement RM writing app lifecycle events to ATS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)