Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of owen.omalley@gmail.com
 designates 209.85.161.176 as permitted sender)
Subject: Re: Jetty fixes for Hadoop
References: <CC22FEFC.2F82%evans@yahoo-inc.com>
From: Owen O'Malley <owen.omalley@gmail.com>
Content-Type: text/plain;
	charset=us-ascii
In-Reply-To: <CC22FEFC.2F82%evans@yahoo-inc.com>
Message-Id: <871A74C3-7C23-44C7-B61E-A0ECDA0A7CF8@gmail.com>
Date: Wed, 11 Jul 2012 09:38:12 -0700
To: "common-dev@hadoop.apache.org" <common-dev@hadoop.apache.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)

In 2.0 we've reimplemented the shuffle using Netty for a significant speed u=
p. Moving webhdfs to Netty would be interesting.=20

-- Owen

On Jul 11, 2012, at 6:03, Robert Evans <evans@yahoo-inc.com> wrote:

> I am +1 on this also, although I think we need to look at moving to
> Jetty-7 or possibly dropping Jetty completely and look at Netty or even
> Tomcat long term.  Jetty has just been way too unstable at Hadoop scale
> and that has not really changed with newer versions of Jetty.  Sticking
> with an old forked unsupported version of Jetty longterm seems very risky
> too me.
>=20
> --Bobby
>=20
> On 7/10/12 5:19 PM, "Todd Lipcon" <todd@cloudera.com> wrote:
>=20
>> +1 from me too. We've had this in CDH since Sep '11 and been working
>> much better than the stock 6.1.26.
>>=20
>> -Todd
>>=20
>> On Tue, Jul 10, 2012 at 3:14 PM, Owen O'Malley <omalley@apache.org> wrote=
:
>>> On Tue, Jul 10, 2012 at 2:59 PM, Thomas Graves
>>> <tgraves@yahoo-inc.com>wrote:
>>>=20
>>>> I'm +1 for adding it.
>>>>=20
>>>=20
>>> I'm +1 also.
>>>=20
>>> -- Owen
>>=20
>>=20
>>=20
>> --=20
>> Todd Lipcon
>> Software Engineer, Cloudera
>=20