[
https://issues.apache.org/jira/browse/MAPREDUCE-3851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213754#comment-13213754
]
Hadoop QA commented on MAPREDUCE-3851:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12515608/MAPREDUCE-3851.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 6 new or modified tests.
-1 patch. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1910//console
This message is automatically generated.
> Allow more aggressive action on detection of the jetty issue
> ------------------------------------------------------------
>
> Key: MAPREDUCE-3851
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3851
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: tasktracker
> Affects Versions: 1.0.0
> Reporter: Kihwal Lee
> Assignee: Thomas Graves
> Fix For: 1.1.0, 1.0.1
>
> Attachments: MAPREDUCE-3851.patch, MAPREDUCE-3851.patch,
> MAPREDUCE-3851.patch, MAPREDUCE-3851.patch
>
>
> MAPREDUCE-2529 added the useful failure detection mechanism. In this jira, I
> propose we add a periodic check inside TT and configurable action to
> self-destruct. Blacklisting helps but is not enough. Hung jetty still accepts
> connection and it takes very long time for clients to fail out. Short jobs
> are delayed for hours because of this. This feature will be a nice companion
> to MAPREDUCE-3184.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
