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, 02 May 2015 20:53:06 GMT

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

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

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch |  14m 34s | Pre-patch trunk compilation is healthy. |
| {color:green}+1{color} | @author |   0m  0s | The patch does not contain any @author tags.
|
| {color:red}-1{color} | tests included |   0m  0s | 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{color} | javac |   7m 35s | There were no new javac warning messages. |
| {color:green}+1{color} | javadoc |   9m 53s | There were no new javadoc warning messages.
|
| {color:green}+1{color} | release audit |   0m 22s | The applied patch does not increase
the total number of release audit warnings. |
| {color:red}-1{color} | checkstyle |   0m 26s | The applied patch generated  4 new checkstyle
issues (total was 41, now 44). |
| {color:red}-1{color} | whitespace |   0m  0s | The patch has 1  line(s) that end in whitespace.
Use git apply --whitespace=fix. |
| {color:green}+1{color} | install |   1m 36s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse |   0m 32s | The patch built with eclipse:eclipse.
|
| {color:green}+1{color} | findbugs |   0m 43s | The patch does not introduce any new Findbugs
(version 2.0.3) warnings. |
| {color:green}+1{color} | mapreduce tests |   5m 43s | Tests passed in hadoop-mapreduce-client-hs.
|
| | |  41m 28s | |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | http://issues.apache.org/jira/secure/attachment/12620602/yarn-647-2.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / 6ae2a0d |
| checkstyle |  https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5598/artifact/patchprocess/diffcheckstylehadoop-mapreduce-client-hs.txt
|
| whitespace | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5598/artifact/patchprocess/whitespace.txt
|
| hadoop-mapreduce-client-hs test log | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5598/artifact/patchprocess/testrun_hadoop-mapreduce-client-hs.txt
|
| Test Results | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5598/testReport/
|
| Java | 1.7.0_55 |
| uname | Linux asf903.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed Sep
3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Console output | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5598/console |


This message was 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: Hong Shen
>            Assignee: Hong Shen
>         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.3.4#6332)

Mime
View raw message