hadoop-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Todd Lipcon <t...@cloudera.com>
Subject Re: [VOTE] Release hadoop-2.0.0-alpha
Date Tue, 15 May 2012 17:00:51 GMT
Hi Kumar,

It looks like that patch was only committed to trunk, not branch-2.

IMO we should keep the new changes for 2.0.0-alpha to a minimum (just
things that impact client-server wire compatibility) and then plan a
2.0.1-alpha ASAP following this release, where we can pull in everything
else that went into branch-2 in the last couple weeks since the 2.0.0-alpha
branch was cut.

Arun: do you have time today to roll a new RC? If not, I am happy to do so.

Does that sound reasonable?
-Todd

On Tue, May 15, 2012 at 8:51 AM, Kumar Ravi <kumarr@us.ibm.com> wrote:

> Hi,
>
>  Can HDFS-3265 be included too?
> It seems like this was marked for inclusion but I can't seem to find the
> patch in the branch-2.0.0-alpha tree.
>
> Thanks,
> Kumar
>
> Kumar Ravi
>
>
> [image: Inactive hide details for Todd Lipcon ---05/14/2012 11:21:34
> PM---Hey Arun,]Todd Lipcon ---05/14/2012 11:21:34 PM---Hey Arun,
>
>
>
>    From:
>
>
> Todd Lipcon <todd@cloudera.com>
>
>    To:
>
>
> general@hadoop.apache.org
>
>    Date:
>
>
> 05/14/2012 11:21 PM
>
>    Subject:
>
>
> Re: [VOTE] Release hadoop-2.0.0-alpha
> ------------------------------
>
>
> Hey Arun,
>
> One more thing on the rc tarball: the source artifact doesn't appear
> to be an exact svn export, based on a diff. For example, it includes
> the README, NOTICE, and LICENSE files, as well as a few other things
> which appear to be build artifacts (eg
> hadoop-hdfs-project/hadoop-hdfs/downloads,
> hadoop-hdfs-project/hadoop-hdfs/test_edit_log, etc).
>
> It seems like we _should_ have the various README style files, but we
> shouldn't have the test artifacts in our source release.
>
> In order to get our source release to match svn, perhaps we should
> move NOTICE, README, LICENSE, etc to the top level of our svn repo,
> such that a pure svn export would be a releaseable source artifact?
>
> -Todd
>
>
>
> On Mon, May 14, 2012 at 2:14 PM, Siddharth Seth
> <seth.siddharth@gmail.com> wrote:
> > Do we want to get MAPREDUCE-4067 in as well ? It affects folks who may be
> > writing their own AMs. Shouldn't affect MR clients though. I believe 2.0
> > alpha doesn't freeze the Yarn protocols for the 2.0 branch, so probably
> not
> > critical.
> >
> > Thanks
> > - Sid
> >
> > On Mon, May 14, 2012 at 1:32 PM, Eli Collins <eli@cloudera.com> 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 <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.)
> >> >
> >> > Tsz-Wo
> >> >
> >> >
> >> >
> >> > ----- 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
> >> >
> >> > Let me merge HADOOP-8285 and HADOOP-8366.  Thanks.
> >> > Tsz-Wo
> >> >
> >> >
> >> >
> >> > ----- 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
> >> >
> >> >> 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 <eli@cloudera.com>
> wrote:
> >> >>> +1  I 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
> 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.
> >> >>>
> >> >>> 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-common-project/hadoop-common
> >> >>> -r 40e90d3c7e5d71aedcdc2d9cc55d078e78944c55
> >> >>> Compiled by hortonmu on Wed May  9 16:19:55 UTC 2012
> >> >>> From source with checksum 3d9a13a31ef3a9ab4b5cba1f982ab888
> >> >>>
> >> >>>
> >> >>> 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.
> >> >>>>
> >> >>>> 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
> >> days.
> >> >>>>
> >> >>>> This is a big milestone for the Apache Hadoop community -
> >> congratulations 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/
> >> >
> >>
>
>
>
> --
> Todd Lipcon
> Software Engineer, Cloudera
>
>
>


-- 
Todd Lipcon
Software Engineer, Cloudera

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message