You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-dev@hadoop.apache.org by "Kihwal Lee (Created) (JIRA)" <ji...@apache.org> on 2012/02/10 23:16:59 UTC

[jira] [Created] (MAPREDUCE-3851) Allow more aggressive action on detection of the jetty issue

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
             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