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 4B4E018399 for ; Thu, 3 Sep 2015 12:26:46 +0000 (UTC) Received: (qmail 3161 invoked by uid 500); 3 Sep 2015 12:26:46 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 3039 invoked by uid 500); 3 Sep 2015 12:26: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 2808 invoked by uid 99); 3 Sep 2015 12:26:45 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Sep 2015 12:26:45 +0000 Date: Thu, 3 Sep 2015 12:26:45 +0000 (UTC) From: "Sunil G (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-4044) Running applications information changes such as movequeue is not published to TimeLine server 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-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728938#comment-14728938 ] Sunil G commented on YARN-4044: ------------------------------- Thank You [~Naganarasimha] for sharing the comments. bq.ApplicationHistoryManagerOnTimelineStore.convertToApplicationReport needs to capture the event ApplicationMetricsConstants.UPDATED_EVENT_TYPE I feel this is not needed. We are already not handling {{ACLS_UPDATED_EVENT_TYPE}} also. I think we use different handling in {{convertToApplicationReport}} for CREATED_EVENT_TYPE and FINISHED_EVENT_TYPE to record appStarted time and appFinished time (plus few other finished details) I used {{entityInfo}} to store Queue and Priority details. Hence the first part of code in {{convertToApplicationReport}} covers reading that details and will fed to {{ApplicationReportExt}} object. Please share your opinion. bq.we need to check return the report with the information present in latest ApplicationMetricsConstants.UPDATED_EVENT_TYPE One doubt here. We already are using {{EnumSet.allOf(Field.class)}} in {{ApplicationHistoryManagerOnTimelineStore.getApplication}} and hence it has {{LAST_EVENT_ONLY}} field. So we will read the last saved entity. Please help to correct me if I am wrong. > Running applications information changes such as movequeue is not published to TimeLine server > ---------------------------------------------------------------------------------------------- > > Key: YARN-4044 > URL: https://issues.apache.org/jira/browse/YARN-4044 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager, timelineserver > Affects Versions: 2.7.0 > Reporter: Sunil G > Assignee: Sunil G > Priority: Critical > Attachments: 0001-YARN-4044.patch, 0002-YARN-4044.patch > > > SystemMetricsPublisher need to expose an appUpdated api to update any change for a running application. > Events can be > - change of queue for a running application. > - change of application priority for a running application. > This ticket intends to handle both RM and timeline side changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)