hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Foley (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-2980) Fetch failures and other related issues in Jetty 6.1.26
Date Tue, 04 Oct 2011 17:27:34 GMT

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

Matt Foley commented on MAPREDUCE-2980:
---------------------------------------

Should we instead be looking at upgrading to Jetty 7.x?  It doesn't look like the Jetty dev
community is supporting 6.x in any significant way any more, see for example
[JETTY-1374 Hadoop's TaskTracker OOM after upgrade to jetty6|http://jira.codehaus.org/browse/JETTY-1374?focusedCommentId=271808&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-271808]
                
> Fetch failures and other related issues in Jetty 6.1.26
> -------------------------------------------------------
>
>                 Key: MAPREDUCE-2980
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2980
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: tasktracker
>    Affects Versions: 0.20.205.0, 0.23.0
>            Reporter: Todd Lipcon
>            Priority: Critical
>
> Since upgrading Jetty from 6.1.14 to 6.1.26 we've had a ton of HTTP-related issues, including:
> - Much higher incidence of fetch failures
> - A few strange file-descriptor related bugs (eg MAPREDUCE-2389)
> - A few unexplained issues where long "fsck"s on the NameNode drop out halfway through
with a ClosedChannelException
> Stress tests with 10000Map x 10000Reduce sleep jobs reliably reproduce fetch failures
at a rate of about 1 per million on a 25 node test cluster. These problems are all new since
the upgrade from 6.1.14.

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