[
https://issues.apache.org/jira/browse/MAPREDUCE-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13104308#comment-13104308
]
Todd Lipcon commented on MAPREDUCE-2980:
----------------------------------------
I agree it's less critical for the shuffle, but we're also seeing an issue
where the NN drops an HTTP connection in the middle of long fsck response, in
particular when it's under other load (eg big checkpoints). It's really
spurious and hard to reproduce, but we have some inkling that it's related to
this issue.
I've been bugging the jetty folks about timeline for a 6.1.27 release, but it
may be a couple months off. I figured that 6.1.26".1" would be an interim
solution for 205 and/or 206 until a 6.1.27 release is ready and can be QAed.
Are you -1 or just not wild about it? FWIW the patch is not a custom change,
bur rather just the NIO-related changes that will be integrated for 6.1.27.
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
