hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sangjin Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5018) Online aggregation logic should not run immediately after collectors got started
Date Fri, 20 May 2016 16:28:12 GMT

    [ https://issues.apache.org/jira/browse/YARN-5018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15293651#comment-15293651
] 

Sangjin Lee commented on YARN-5018:
-----------------------------------

[~gtCarrera9], how about adding a check in {{AppLevelAggregator.run()}} so that it skips the
run if the context is not completely set (e.g. checking for flow name) *or* there is no entity
aggregated? That would be an additional fail-safe mechanism.

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


Mime
View raw message