Return-Path: X-Original-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2B02A1073D for ; Thu, 3 Apr 2014 10:17:47 +0000 (UTC) Received: (qmail 9536 invoked by uid 500); 3 Apr 2014 10:17:46 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 9158 invoked by uid 500); 3 Apr 2014 10:17:39 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 8187 invoked by uid 99); 3 Apr 2014 10:17:37 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Apr 2014 10:17:37 +0000 Date: Thu, 3 Apr 2014 10:17:36 +0000 (UTC) From: "Fengdong Yu (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (MAPREDUCE-2980) Fetch failures and other related issues in Jetty 6.1.26 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MAPREDUCE-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13958689#comment-13958689 ] Fengdong Yu commented on MAPREDUCE-2980: ---------------------------------------- why don't upgrade to the latest version of Jetty? it's incompatible? > 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 > > 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 was sent by Atlassian JIRA (v6.2#6252)