hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amar Kamat (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-2529) Recognize Jetty bug 1342 and handle it
Date Sat, 04 Jun 2011 06:02:47 GMT

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

Amar Kamat commented on MAPREDUCE-2529:
---------------------------------------

If the currently used version of Jetty is buggy then why can't we revert back to the previous
stable (well tested) release? Apologies if its already discussed.

> 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

Mime
View raw message