hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Graves (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3851) Allow more aggressive action on detection of the jetty issue
Date Thu, 16 Feb 2012 13:39:59 GMT

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

Thomas Graves commented on MAPREDUCE-3851:

We are looking at doing this to better handle http://jira.codehaus.org/browse/JETTY-1342.
 This is supposedly fixed in Jetty 6.1.27 - if it ever gets released, which I'm guessing is
also in the patched 6.1.26 that Todd created.

I believe MAPREDUCE-3184 is for http://jira.codehaus.org/browse/JETTY-937.

We are seeing both and would like to more aggressive handle Jetty-1342 by exiting immediately
so any running tasks trying to fetch data from this TT will get relaunched somewhere else
rather then trying a bunch of times.

Todd, as Kihwal mentioned if you think MAPREDUCE-3184 also covers Jetty-1342 please let us
> 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
> 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


View raw message