hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5700) historyServer can't show container's log when aggregation is not enabled
Date Sat, 28 Dec 2013 02:50:50 GMT

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

Hadoop QA commented on MAPREDUCE-5700:
--------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12620602/yarn-647-2.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version
1.3.9) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs.

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4284//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4284//console

This message is automatically generated.

> historyServer can't show container's log when aggregation is not enabled
> ------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-5700
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5700
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>    Affects Versions: 0.23.7, 2.0.4-alpha, 2.2.0
>         Environment:  yarn.log-aggregation-enable=false , HistoryServer will show like
this:
> Aggregation is not enabled. Try the nodemanager at hd13-vm1:34669
>            Reporter: shenhong
>            Assignee: shenhong
>         Attachments: yarn-647-2.patch, yarn-647.patch
>
>
> When yarn.log-aggregation-enable is seted to false, after a MR_App complete, we can't
view the container's log from the HistoryServer, it shows message like:
> Aggregation is not enabled. Try the nodemanager at hd13-vm1:34669
> Since we don't want to aggregate the container's log, because it will be a pressure to
namenode. but sometimes we also want to take a look at container's log.
> Should we show the container's log across HistoryServer even if yarn.log-aggregation-enable
is seted to false.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message