hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jun Gong (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4735) Remove stale LogAggregationReport from NM's context
Date Fri, 26 Feb 2016 14:30:18 GMT

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

Jun Gong commented on YARN-4735:

Thanks [~mingma]. I checked the code, it seems not an issue. I'll verify it again. 

[~kasha] Maybe the issue you met is not same? 

> 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
> {quote}
> Per discussion in YARN-4720, we need remove stale LogAggregationReport from NM's context.

This message was sent by Atlassian JIRA

View raw message