hadoop-yarn-issues mailing list archives

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

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

Li Lu commented on YARN-5018:
-----------------------------

Right. Potentially this might be a problem since we may "lose control" to some part of our
code since those UTs are not stable. We have to be very careful to not to introduce any regression
on those UTs.  

> 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


Mime
View raw message