[
https://issues.apache.org/jira/browse/YARN-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15167456#comment-15167456
]
Ming Ma commented on YARN-4735:
-------------------------------
I just read the code again. {{NodeStatusUpdaterImpl}} 's
{{getLogAggregationReportsForApps}} actually calls
{{lastestLogAggregationStatus.poll()}} and add it to another newly created list
to be sent to RM. So this isn't an issue?
> 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)
