Hi Robert, Source artifacts are missing. Could you please upload those as a separate tarball like the last time?
+1 from me (non-binding) for the binaries otherwise. Verified the signature. ➜ gpg --verify hadoop-0.23.4.tar.gz.asc hadoop-0.23.4.tar.gz gpg: Good signature from "Robert Joseph Evans (Bobby) <bobby[at]apache[dot]org>" Ran a single machine cluster and ran a couple of MR jobs and the distributed shell YARN app (needed extra configuring, check https://issues.apache.org/jira/browse/MAPREDUCE-3869 for your next release, if you perhaps want to make the experience better?). Seems to work alright. ➜ bin/yarn jar share/hadoop/mapreduce/hadoop-mapreduce-examples-0.23.4.jar pi -Dmapreduce.framework.name=yarn 10 10 … Estimated value of Pi is 3.20000000000000000000 On Sat, Sep 29, 2012 at 9:05 PM, Robert Evans <ev...@yahoo-inc.com> wrote: > I have built a 0.23.4-rc0 and am calling a release vote on it. As per the > bylaws this vote will be open for 1 week, and will close next Saturday > October 6th. > > You can access the release through the apache maven staging repo, with the > 0.23.4-rc0 tag in subversion, and at > http://people.apache.org/~bobby/hadoop-0.23.4-candidate-0/ > > This release is a sustaining release with several important bug fixes in it. > Most notably upgrading of a 1.0 cluster with append/sync enabled should now > work (HDFS-3731). There are no known blockers against this release, there > are only two critical issues. > > HADOOP-8811 > Compile hadoop native library in FreeBSD > > HDFS-3990 > NN's health report has severe performance problems > > HDFS-3990 only really has a significant impact on large clusters, and can be > mitigated by enabling DNS caching. > > I have run several manual tests on this release on a small insecure cluster > and all of them pass I am a +1 (binding) for this release. > > On a side note I am happy to announce that the 0.23 line is being rolled out > more widely at Yahoo!. We just installed 0.23.3 on a 2000 node cluster and > have only seen a few issues (HDFS-3990 is the biggest of them). I expect to > do a 0.23.5 release in the coming weeks/months as we find more issues running > on large clusters. > > --Bobby Evans > > -- Harsh J
