Great news! Thanks for the update, Bobby!

+Vinod Kumar Vavilapalli
Hortonworks Inc.

On Oct 15, 2012, at 12:55 PM, Robert Evans wrote:

From my count we have 5 binding +1 votes and no -1s so it passes.  I will upgrade nexus and move the tag to its final value.

Thanks for the help from everyone.

On a related note I am happy to say that 0.23.3 has moved to an even larger grid at Yahoo!. Today we are now running 0.23.3 on a 3,600 node cluster, still with no new issues beyond those we saw on the previous 2000 node cluster.  There is still some polishing to do, but YARN is looking fairly good so far.  Which is great because this cluster has a few production jobs running on it :).


-----Original Message-----
From: Robert Evans []
Sent: Monday, October 08, 2012 12:12 PM
Subject: Re: [VOTE] 0.23.4 release

Thanks for catching that.  There was a bug in my script that I used to
build everything for the release.  It rebuilt the src tag ball after I had
signed the original.  The contents are the same, but the date/time stamps
were off.  I uploaded a new version of the offending tar.gz with the
corresponding signature and mds files.

Thanks again,


On 10/8/12 1:51 PM, "Siddharth Seth" <> wrote:

Bobby, the checksums don't match for hadoop-0.23.4-src.tar.tar.gz.

- Sid

On Mon, Oct 8, 2012 at 8:06 AM, Robert Evans <> wrote:

Thanks for the help everyone on this.  I have re-spun the release.  You
can get it at

And through the apache maven staging repository.

The only difference is some debugging code removed.  The vote now goes
until Monday 15th. I am a +1 for the release.

--Bobby Evans

On 10/5/12 2:41 PM, "Robert Evans" <> wrote:

Arun, if you could re-spin it I would be happy to let you.  If not I
do it myself on Monday.  My box that is set up to do the builds is
until Monday.  There are some workman fixing some things in my cube

Thanks for your help,


On 10/5/12 1:46 PM, "Arun Murthy" <> wrote:

I think Bobby is OOO, I can re-spin if Thomas can't step in.


Sent from my iPhone

On Oct 5, 2012, at 11:44 AM, Owen O'Malley <> wrote:

It looks like some debugging code got committed and rolled into the
release. I think we'll need to re-spin the rc after fixing it, so