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 1C4D6C9BA for ; Tue, 15 May 2012 18:58:39 +0000 (UTC) Received: (qmail 78160 invoked by uid 500); 15 May 2012 18:58:37 -0000 Delivered-To: apmail-hadoop-general-archive@hadoop.apache.org Received: (qmail 78083 invoked by uid 500); 15 May 2012 18:58:37 -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 78072 invoked by uid 99); 15 May 2012 18:58:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 May 2012 18:58:37 +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 (nike.apache.org: domain of eli@cloudera.com designates 209.85.215.48 as permitted sender) Received: from [209.85.215.48] (HELO mail-lpp01m010-f48.google.com) (209.85.215.48) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 May 2012 18:58:31 +0000 Received: by lagz14 with SMTP id z14so6117809lag.35 for ; Tue, 15 May 2012 11:58:11 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding:x-gm-message-state; bh=VlKqm7rFl3oNyLfLgOTzDNdYlV7YgfpZXllNl5wAcy8=; b=puugFXccPkwksXG+/5vNa3xBnaN4VW1kg24uhpXsRsmKZfwSES/5jVrPF7aaLh+T8T tmLAr0VnrZbhy7QaeFJIBPUMkSVHqVArsSX/iqWxj8YMUP6aMjechQ36VK7GQIpxpE6i DXva+AFyvVoaCUYTuxvgAs4w0PRAQuRNc4F0GMlWPueqkL1m1HeJcnd8RRy1YKIbfs6m X1AnFacKx4k5BanIX+do1ZRiyk+DQkdrGd8u3dzlTyoX9lGFlFOsNCgG538sjOvc0tIA T0kuUjU0HrvUw8BPYNcFdX7C1Lhz1EVHvLcCZ+Sdr1JHiuGiNk1mBzZGbMohLymdfgA3 /c1A== MIME-Version: 1.0 Received: by 10.152.122.116 with SMTP id lr20mr20126lab.42.1337108291071; Tue, 15 May 2012 11:58:11 -0700 (PDT) Received: by 10.112.4.2 with HTTP; Tue, 15 May 2012 11:58:10 -0700 (PDT) In-Reply-To: <6BC1588B-A5BC-44AF-AA66-ECF85C89D8A2@hortonworks.com> References: <4C4776F7-94C7-453E-ACC8-E4663186FED0@hortonworks.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> <6BC1588B-A5BC-44AF-AA66-ECF85C89D8A2@hortonworks.com> Date: Tue, 15 May 2012 11:58:10 -0700 Message-ID: Subject: Re: [VOTE] Release hadoop-2.0.0-alpha From: Eli Collins To: general@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQlLtpydyfhteXhOikphJKrXs3YU+jQBU3AZXb1bwGoLF2PnAzPdrorAz/UQAQUZSGWyFuuk Turns out 3418 is compatible, so no need to block on it. Thanks Arun! On Tue, May 15, 2012 at 10:05 AM, Arun C Murthy wrote= : > 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). >> >> >> On Mon, May 14, 2012 at 12:16 PM, Tsz Wo Sze wrote: >>> I just have merged HADOOP-8285 and HADOOP-8366. =A0I also have merged H= DFS-3211 since it is an incompatible protocol change (without it, 2.0.0-alp= haand 2.0.0 will be incompatible.) >>> >>> Tsz-Wo >>> >>> >>> >>> ----- Original Message ----- >>> From: Tsz Wo Sze >>> To: "general@hadoop.apache.org" >>> Cc: >>> Sent: Monday, May 14, 2012 11:07 AM >>> Subject: Re: [VOTE] Release hadoop-2.0.0-alpha >>> >>> Let me merge HADOOP-8285 and HADOOP-8366. =A0Thanks. >>> Tsz-Wo >>> >>> >>> >>> ----- Original Message ----- >>> From: Uma Maheswara Rao G >>> To: "general@hadoop.apache.org" >>> Cc: >>> Sent: Monday, May 14, 2012 10:56 AM >>> Subject: RE: [VOTE] Release hadoop-2.0.0-alpha >>> >>>> 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? >>> >>> 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 >>> >>> Todd, >>> >>> Please go ahead and merge changes into branch-2.0.0-alpha and I'll roll= RC1. >>> >>> thanks, >>> Arun >>> >>> On May 12, 2012, at 10:05 PM, Todd Lipcon wrote: >>> >>>> Looking at the release tag vs the current state of branch-2, I have >>>> two concerns from the point of view of HDFS: >>>> >>>> 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. >>>> >>>> 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) >>>> >>>> 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. >>>> >>>> -Todd >>>> >>>> On Fri, May 11, 2012 at 7:19 PM, Eli Collins wrote: >>>>> +1 =A0I installed the build on a 6 node cluster and kicked the tires, >>>>> didn't find any blocking issues. >>>>> >>>>> Btw in the future better to build from the svn repo so the revision i= s >>>>> 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. >>>>> >>>>> hadoop-2.0.0-alpha $ ./bin/hadoop version >>>>> Hadoop 2.0.0-alpha >>>>> Subversion git://devadm900.cc1.ygridcore.net/grid/0/dev/acm/hadoop-tr= unk/hadoop-common-project/hadoop-common >>>>> -r 40e90d3c7e5d71aedcdc2d9cc55d078e78944c55 >>>>> Compiled by hortonmu on Wed May =A09 16:19:55 UTC 2012 >>>>> From source with checksum 3d9a13a31ef3a9ab4b5cba1f982ab888 >>>>> >>>>> >>>>> On Wed, May 9, 2012 at 9:58 AM, Arun C Murthy w= rote: >>>>>> I've created a release candidate for hadoop-2.0.0-alpha that I would= like to release. >>>>>> >>>>>> It is available at: http://people.apache.org/~acmurthy/hadoop-2.0.0-= alpha-rc0/ >>>>>> >>>>>> The maven artifacts are available via repository.apache.org. >>>>>> >>>>>> Please try the release and vote; the vote will run for the usual 7 d= ays. >>>>>> >>>>>> This is a big milestone for the Apache Hadoop community - congratula= tions and thanks for all the contributions! >>>>>> >>>>>> thanks, >>>>>> Arun >>>>>> >>>>>> >>>>>> -- >>>>>> Arun C. Murthy >>>>>> Hortonworks Inc. >>>>>> http://hortonworks.com/ >>>>>> >>>>>> >>>> >>>> >>>> >>>> -- >>>> Todd Lipcon >>>> Software Engineer, Cloudera >>> >>> -- >>> Arun C. Murthy >>> Hortonworks Inc. >>> http://hortonworks.com/ >>> > > -- > Arun C. Murthy > Hortonworks Inc. > http://hortonworks.com/ > >