[
https://issues.apache.org/jira/browse/HADOOP-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689810#action_12689810
]
Hadoop QA commented on HADOOP-4374:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12403690/HADOOP-4374.v1.1.patch
against trunk revision 758925.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 6 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
-1 findbugs. The patch appears to introduce 1 new Findbugs warnings.
+1 Eclipse classpath. The patch retains Eclipse classpath integrity.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
-1 contrib tests. The patch failed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/145/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/145/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/145/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/145/console
This message is automatically generated.
> JVM should not be killed but given an opportunity to exit gracefully
> --------------------------------------------------------------------
>
> Key: HADOOP-4374
> URL: https://issues.apache.org/jira/browse/HADOOP-4374
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.19.0
> Reporter: Devaraj Das
> Assignee: Ravi Gummadi
> Fix For: 0.20.0
>
> Attachments: HADOOP-4374.patch, HADOOP-4374.v1.1.patch,
> HADOOP-4374.v1.patch
>
>
> When the tasktracker picks an idle JVM for purging, it should signal the JVM
> to exit gracefully, rather than forcefully killing it. This might have the
> unfortunate side effect of logs not fully flushed yet in some cases.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
