You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Karthik Kambatla (JIRA)" <ji...@apache.org> on 2016/02/25 07:10:18 UTC
[jira] [Commented] (YARN-4735) Remove stale LogAggregationReport
from NM's context
[ https://issues.apache.org/jira/browse/YARN-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15166778#comment-15166778 ]
Karthik Kambatla commented on YARN-4735:
----------------------------------------
We have seen this issue as well.
> Remove stale LogAggregationReport from NM's context
> ---------------------------------------------------
>
> Key: YARN-4735
> URL: https://issues.apache.org/jira/browse/YARN-4735
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Jun Gong
> Assignee: Jun Gong
>
> {quote}
> All LogAggregationReport(current and previous) are only added to *context.getLogAggregationStatusForApps*, and never removed.
> So for long running service, the LogAggregationReport list NM sends to RM will grow over time.
> {quote}
> Per discussion in YARN-4720, we need remove stale LogAggregationReport from NM's context.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)