[
https://issues.apache.org/jira/browse/MAPREDUCE-2529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044205#comment-13044205
]
Hadoop QA commented on MAPREDUCE-2529:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12481433/M2529-1.patch
against trunk revision 1131265.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 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 (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed these core unit tests:
org.apache.hadoop.cli.TestMRCLI
+1 contrib tests. The patch passed contrib unit tests.
+1 system test framework. The patch passed system test framework compile.
Test results:
https://builds.apache.org/hudson/job/PreCommit-MAPREDUCE-Build/346//testReport/
Findbugs warnings:
https://builds.apache.org/hudson/job/PreCommit-MAPREDUCE-Build/346//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/hudson/job/PreCommit-MAPREDUCE-Build/346//console
This message is automatically generated.
> Recognize Jetty bug 1342 and handle it
> --------------------------------------
>
> Key: MAPREDUCE-2529
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2529
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: tasktracker
> Affects Versions: 0.20.204.0, 0.23.0
> Reporter: Thomas Graves
> Assignee: Thomas Graves
> Fix For: 0.20.205.0, 0.23.0
>
> Attachments: M2529-1-20s.patch, M2529-1.patch,
> jetty1342-20security.patch, mapred2529-trunk.patch
>
>
> We are seeing many instances of the Jetty-1342
> (http://jira.codehaus.org/browse/JETTY-1342). The bug doesn't cause Jetty to
> stop responding altogether, some fetches go through but a lot of them throw
> exceptions and eventually fail. The only way we have found to get the TT out
> of this state is to restart the TT. This jira is to catch this particular
> exception (or perhaps a configurable regex) and handle it in an automated way
> to either blacklist or shutdown the TT after seeing it a configurable number
> of them.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
