hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jian He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3505) Node's Log Aggregation Report with SUCCEED should not cached in RMApps
Date Thu, 30 Apr 2015 20:41:06 GMT

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

Jian He commented on YARN-3505:
-------------------------------

One other thing, the LogAggregationReport#(get/set)getNodeId can also be removed as it's not
used anywhere. 
I'm also unsure about the usage of LogAggregationReport#(get/set)DiagnosticMessage as it's
only set with an empty string.

> Node's Log Aggregation Report with SUCCEED should not cached in RMApps
> ----------------------------------------------------------------------
>
>                 Key: YARN-3505
>                 URL: https://issues.apache.org/jira/browse/YARN-3505
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: log-aggregation
>    Affects Versions: 2.8.0
>            Reporter: Junping Du
>            Assignee: Xuan Gong
>            Priority: Critical
>         Attachments: YARN-3505.1.patch
>
>
> Per discussions in YARN-1402, we shouldn't cache all node's log aggregation reports in
RMApps for always, especially for those finished with SUCCEED.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message