[ https://issues.apache.org/jira/browse/MAPREDUCE-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122365#comment-13122365 ]
Matt Foley commented on MAPREDUCE-2980: --------------------------------------- I'm afraid I don't see a qualitative difference between the "risk" of transitioning from 6.1.14 -> 6.1.26 vs the risk of transitioning from 6.1.26 -> 7.x. In fact, if we transition to a version of 7.x that is currently viewed as being *stable* (what a concept!) then it might be less risky than transitioning to 6.1.27, which does not have any claim of being stable. > 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