[
https://issues.apache.org/jira/browse/HADOOP-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580263#action_12580263
]
Hadoop QA commented on HADOOP-2947:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12378113/HADOOP-2947
against trunk revision 619744.
@author +1. The patch does not contain any @author tags.
tests included +1. The patch appears to include 4 new or modified tests.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new javac compiler
warnings.
release audit +1. The applied patch does not generate any new release
audit warnings.
findbugs +1. The patch does not introduce any new Findbugs warnings.
core tests -1. The patch failed core unit tests.
contrib tests +1. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1992/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1992/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1992/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1992/console
This message is automatically generated.
> [HOD] Hod should redirect stderr and stdout of Hadoop daemons to assist
> debugging
> ---------------------------------------------------------------------------------
>
> Key: HADOOP-2947
> URL: https://issues.apache.org/jira/browse/HADOOP-2947
> Project: Hadoop Core
> Issue Type: Improvement
> Components: contrib/hod
> Affects Versions: 0.16.0
> Reporter: Hemanth Yamijala
> Assignee: Vinod Kumar Vavilapalli
> Fix For: 0.17.0
>
> Attachments: HADOOP-2947
>
>
> Copied from internal bug details from Koji:
> ==========================
> Sometimes JobTracker/TaskTracker starts consuming 99% cpu and stops
> responding to 'jstack' call. In those cases,
> usually it still responds to kill -QUIT signal which forces the jvm to dump
> the stack to stdout.
> Please have the stdout of JT/TT redirected to a file.
> Adding stderr.
> If thread has an uncaught exception, it prints out to stderr and dies.
> ==========================
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
