Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 17 May 2016 21:08:12 +0000 (UTC)
From: "Sangjin Lee (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12964028.1461978377000.215998.1463519292942@Atlassian.JIRA>
In-Reply-To: <JIRA.12964028.1461978377000@Atlassian.JIRA>
References: <JIRA.12964028.1461978377000@Atlassian.JIRA> <JIRA.12964028.1461978377447@arcas>
Subject: [jira] [Updated] (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
archived-at: Tue, 17 May 2016 21:08:17 -0000


     [ https://issues.apache.org/jira/browse/YARN-5018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sangjin Lee updated YARN-5018:
------------------------------
    Labels: yarn-2928-1st-milestone  (was: )

> 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
>
> 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