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 18:40:59 GMT

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

Thomas Graves commented on MAPREDUCE-3851:
------------------------------------------

Yes we've seen both instances in production. I don't have any metrics on which one we are
seeing more.  I should have a patch for this up later today, finishing up some testing.
                
> 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

        

Mime
View raw message