Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id F3D86200B31 for ; Tue, 24 May 2016 19:41:14 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id F0E54160A36; Tue, 24 May 2016 17:41:14 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 3824E160A37 for ; Tue, 24 May 2016 19:41:14 +0200 (CEST) Received: (qmail 24633 invoked by uid 500); 24 May 2016 17:41:13 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 24321 invoked by uid 99); 24 May 2016 17:41:13 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 May 2016 17:41:13 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 09F862C1F56 for ; Tue, 24 May 2016 17:41:13 +0000 (UTC) Date: Tue, 24 May 2016 17:41:13 +0000 (UTC) From: "Li Lu (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-5018) Online aggregation logic should not run immediately after collectors got started MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 24 May 2016 17:41:15 -0000 [ https://issues.apache.org/jira/browse/YARN-5018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15298585#comment-15298585 ] Li Lu commented on YARN-5018: ----------------------------- YARN-4478 appears to be an umbrella, and I think at least YARN-4318 is something we fixed recently. YARN-5091 intends to fix some intermittent failures but I'm not sure when it will be ready. > Online aggregation logic should not run immediately after collectors got started > -------------------------------------------------------------------------------- > > Key: YARN-5018 > URL: https://issues.apache.org/jira/browse/YARN-5018 > Project: Hadoop YARN > Issue Type: Sub-task > Components: timelineserver > Reporter: Li Lu > Assignee: Li Lu > Labels: yarn-2928-1st-milestone > Attachments: YARN-5018-YARN-2928.001.patch, YARN-5018-YARN-2928.002.patch, YARN-5018-YARN-2928.003.patch, YARN-5018-YARN-2928.004.patch, YARN-5018-YARN-2928.005.patch > > > In app level collector, we launch the aggregation logic immediately after the collector got started. However, at this time, important context data has yet to be published to the container. Also, if the aggregation result is empty, we do not need to publish them. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org