Return-Path: X-Original-To: apmail-hadoop-general-archive@minotaur.apache.org Delivered-To: apmail-hadoop-general-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 27C237D00 for ; Fri, 28 Oct 2011 10:27:46 +0000 (UTC) Received: (qmail 39540 invoked by uid 500); 28 Oct 2011 10:27:44 -0000 Delivered-To: apmail-hadoop-general-archive@hadoop.apache.org Received: (qmail 39463 invoked by uid 500); 28 Oct 2011 10:27:44 -0000 Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@hadoop.apache.org Delivered-To: mailing list general@hadoop.apache.org Received: (qmail 39455 invoked by uid 99); 28 Oct 2011 10:27:44 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Oct 2011 10:27:44 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of harsh@cloudera.com designates 209.85.161.176 as permitted sender) Received: from [209.85.161.176] (HELO mail-gx0-f176.google.com) (209.85.161.176) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Oct 2011 10:27:38 +0000 Received: by ggnr1 with SMTP id r1so4686308ggn.35 for ; Fri, 28 Oct 2011 03:27:17 -0700 (PDT) Received: by 10.68.74.4 with SMTP id p4mr3575918pbv.47.1319797637218; Fri, 28 Oct 2011 03:27:17 -0700 (PDT) MIME-Version: 1.0 Received: by 10.142.140.9 with HTTP; Fri, 28 Oct 2011 03:26:56 -0700 (PDT) In-Reply-To: References: From: Harsh J Date: Fri, 28 Oct 2011 15:56:56 +0530 Message-ID: Subject: Re: Homestretch for hadoop-0.22 To: general@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 Hey Konstantin, On Fri, Oct 28, 2011 at 2:59 PM, Konstantin Shvachko wrote: > 3. Jetty upgrade. > 0.22 branch is on Jetty 6.1.14, while everything else moved to 6.1.26. > Based on experiments I ran with Jetty 6.1.14 tasks hang forever if > things go wrong, while with Jetty 6.1.26 you get a lot of "fetch > failure"s. The latter at least fails fast, and does not need manual > intervention, so I'd go for the upgrade. I believe https://issues.apache.org/jira/browse/MAPREDUCE-2980 would help here. -- Harsh J