Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@hadoop.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
From: Arun C Murthy <acm@hortonworks.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-44-164543707
Subject: Re: [VOTE] Release hadoop-2.0.0-alpha
Date: Tue, 15 May 2012 10:05:12 -0700
In-Reply-To: 
 <CAPn_vTuePd=pbK8wwrdQHMn0EgwM1rUdhvPKyDrd4YVpZKcOyA@mail.gmail.com>
To: general@hadoop.apache.org
References: <4C4776F7-94C7-453E-ACC8-E4663186FED0@hortonworks.com>
 <CAPn_vTsiNQ+49pwk=2XbJ6TnMqUONUezHcFy+WU+=B+-VDmGrg@mail.gmail.com>
 <CADY20s6WV6XWd2YcRTs0BeJsYpjH2qGFPmDpOXM0dVeb2kygkA@mail.gmail.com>
 <71E3FE22-FB01-453F-9252-CEAF6BD4789A@hortonworks.com>
 <1542FA4EE20C5048A5C2A3663BED2A6B309E4126@szxeml531-mbx.china.huawei.com>
 <1337018844.26122.YahooMailNeo@web65906.mail.ac4.yahoo.com>
 <1337022978.92960.YahooMailNeo@web65906.mail.ac4.yahoo.com>
 <CAPn_vTuePd=pbK8wwrdQHMn0EgwM1rUdhvPKyDrd4YVpZKcOyA@mail.gmail.com>
Message-Id: <6BC1588B-A5BC-44AF-AA66-ECF85C89D8A2@hortonworks.com>

--Apple-Mail-44-164543707
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Eli, is this done so I can roll rc1?

On May 14, 2012, at 1:32 PM, Eli Collins wrote:

> As soon as jira is back up and I can post an updated patch I'll merge
> HDFS-3418 (also incompatible).
>=20
>=20
> On Mon, May 14, 2012 at 12:16 PM, Tsz Wo Sze <szetszwo@yahoo.com> =
wrote:
>> I just have merged HADOOP-8285 and HADOOP-8366.  I also have merged =
HDFS-3211 since it is an incompatible protocol change (without it, =
2.0.0-alphaand 2.0.0 will be incompatible.)
>>=20
>> Tsz-Wo
>>=20
>>=20
>>=20
>> ----- Original Message -----
>> From: Tsz Wo Sze <szetszwo@yahoo.com>
>> To: "general@hadoop.apache.org" <general@hadoop.apache.org>
>> Cc:
>> Sent: Monday, May 14, 2012 11:07 AM
>> Subject: Re: [VOTE] Release hadoop-2.0.0-alpha
>>=20
>> Let me merge HADOOP-8285 and HADOOP-8366.  Thanks.
>> Tsz-Wo
>>=20
>>=20
>>=20
>> ----- Original Message -----
>> From: Uma Maheswara Rao G <maheswara@huawei.com>
>> To: "general@hadoop.apache.org" <general@hadoop.apache.org>
>> Cc:
>> Sent: Monday, May 14, 2012 10:56 AM
>> Subject: RE: [VOTE] Release hadoop-2.0.0-alpha
>>=20
>>> a) Revert HDFS-3157 and commit HADOOP-8285 and HADOOP-8366 on
>>> branch-2.0.0-alpha, so these are the only changes since rc0. Roll a
>>> new rc1 from here.
>> I have merged HDFS-3157 revert.
>> Do you mind taking a look at HADOOP-8285 and HADOOP-8366?
>>=20
>> Thanks,
>> Uma
>> ________________________________________
>> From: Arun C Murthy [acm@hortonworks.com]
>> Sent: Monday, May 14, 2012 10:24 PM
>> To: general@hadoop.apache.org
>> Subject: Re: [VOTE] Release hadoop-2.0.0-alpha
>>=20
>> Todd,
>>=20
>> Please go ahead and merge changes into branch-2.0.0-alpha and I'll =
roll RC1.
>>=20
>> thanks,
>> Arun
>>=20
>> On May 12, 2012, at 10:05 PM, Todd Lipcon wrote:
>>=20
>>> Looking at the release tag vs the current state of branch-2, I have
>>> two concerns from the point of view of HDFS:
>>>=20
>>> 1) We reverted HDFS-3157 in branch-2 because it sends deletions for
>>> corrupt replicas without properly going through the "corrupt block"
>>> path. We saw this cause data loss in TestPipelinesFailover. So, I'm
>>> nervous about putting it in a release, even labeled as alpha.
>>>=20
>>> 2) HADOOP-8285 and HADOOP-8366 changed the wire format for the RPC
>>> envelope in branch-2, but didn't make it into this rc. So, that =
would
>>> mean that future alphas would not be protocol-compatible with this
>>> alpha. Per a discussion a few weeks ago, I think we all were in
>>> agreement that, if possible, we'd like all 2.x to be compatible for
>>> client-server communication, at least (even if we don't support
>>> cross-version for the intra-cluster protocols)
>>>=20
>>> Do other folks think it's worth rolling an rc1? I would propose =
either:
>>> a) Revert HDFS-3157 and commit HADOOP-8285 and HADOOP-8366 on
>>> branch-2.0.0-alpha, so these are the only changes since rc0. Roll a
>>> new rc1 from here.
>>> or:
>>> b) Discard the current branch-2.0.0-alpha and re-branch from the
>>> current state of branch-2.
>>>=20
>>> -Todd
>>>=20
>>> On Fri, May 11, 2012 at 7:19 PM, Eli Collins <eli@cloudera.com> =
wrote:
>>>> +1  I installed the build on a 6 node cluster and kicked the tires,
>>>> didn't find any blocking issues.
>>>>=20
>>>> Btw in the future better to build from the svn repo so the revision =
is
>>>> an svn rev from the release branch. Eg 1336254 instead of 40e90d3c7
>>>> which is from the git mirror, this way we're consistent across
>>>> releases.
>>>>=20
>>>> hadoop-2.0.0-alpha $ ./bin/hadoop version
>>>> Hadoop 2.0.0-alpha
>>>> Subversion =
git://devadm900.cc1.ygridcore.net/grid/0/dev/acm/hadoop-trunk/hadoop-commo=
n-project/hadoop-common
>>>> -r 40e90d3c7e5d71aedcdc2d9cc55d078e78944c55
>>>> Compiled by hortonmu on Wed May  9 16:19:55 UTC 2012
>>>> =46rom source with checksum 3d9a13a31ef3a9ab4b5cba1f982ab888
>>>>=20
>>>>=20
>>>> On Wed, May 9, 2012 at 9:58 AM, Arun C Murthy <acm@hortonworks.com> =
wrote:
>>>>> I've created a release candidate for hadoop-2.0.0-alpha that I =
would like to release.
>>>>>=20
>>>>> It is available at: =
http://people.apache.org/~acmurthy/hadoop-2.0.0-alpha-rc0/
>>>>>=20
>>>>> The maven artifacts are available via repository.apache.org.
>>>>>=20
>>>>> Please try the release and vote; the vote will run for the usual 7 =
days.
>>>>>=20
>>>>> This is a big milestone for the Apache Hadoop community - =
congratulations and thanks for all the contributions!
>>>>>=20
>>>>> thanks,
>>>>> Arun
>>>>>=20
>>>>>=20
>>>>> --
>>>>> Arun C. Murthy
>>>>> Hortonworks Inc.
>>>>> http://hortonworks.com/
>>>>>=20
>>>>>=20
>>>=20
>>>=20
>>>=20
>>> --
>>> Todd Lipcon
>>> Software Engineer, Cloudera
>>=20
>> --
>> Arun C. Murthy
>> Hortonworks Inc.
>> http://hortonworks.com/
>>=20

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/


--Apple-Mail-44-164543707--