Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

This started out as something and ended up as something else altogether. In any case, I think you should give a fresh heads up outside this thread. There are a bunch of commits and merges happening into branch-2 and thus 2.0.5, so it'll be safe to have an explicit hold-off/all-clear signaling.

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

Thanks Alejandro, that's what my plan for the morning. Thanks for putting together the check-list - would be easier for me not to miss anything. I am aiming to have the bits out by noon or so. Appreciate the help! Cos On Thu, May 30, 2013 at 08:41PM, Alejandro Abdelnur wrote: > Konstantin, Cos,

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

Sounds like a plan. Thanks, --Konst On Thu, May 30, 2013 at 8:41 PM, Alejandro Abdelnur wrote: > Konstantin, Cos, > > As we change from 2.0.4.1 to 2.0.5 you'll need to do the following > housekeeping as you work the new RC. > > * rename the svn branch > * update the versions in the POMs > * upd

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

Konstantin, Cos, As we change from 2.0.4.1 to 2.0.5 you'll need to do the following housekeeping as you work the new RC. * rename the svn branch * update the versions in the POMs * update the CHANGES.txt in trunk, branch-2 and the release branch * change the current 2.0.5 version in JIRA to 2.1.0

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

On Thu, May 30, 2013 at 5:51 PM, Konstantin Boudnik wrote: > I have no issues of changing the version to 2.0.5-alpha and restarting to vote > for the release content, e.g. 2 bug fixes. Shall I call 3 days re-vote because > of the number change? +1 Sounds great. > Does the result of bylaw vote nu

Backwards compatibility of FileSystem interface.

Hi : Are FileSystem interfaces gauranteed to retain semantics of the old FileSystem contract? Im noticing that the new FileSystem uses the "CreateFlag" class, which older ones did not, and I'm wondering wether the deprecation of some FileSystem methods (i.e. createNonRecursive) will eventually be

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

On Thu, May 30, 2013 at 05:30PM, Chris Douglas wrote: > On Thu, May 30, 2013 at 3:25 PM, Konstantin Boudnik wrote: > > There's no plans to release anything else at this point - this is a bug-fix > > release, as I pointed out on a numerous occasions. There's no new features - > > just 2 fixes. > >

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

On Thu, May 30, 2013 at 3:25 PM, Konstantin Boudnik wrote: > There's no plans to release anything else at this point - this is a bug-fix > release, as I pointed out on a numerous occasions. There's no new features - > just 2 fixes. If you're worried about extending the voting by a week, I don't t

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

On Thu, May 30, 2013 at 04:08PM, Jean-Daniel Cryans wrote: > FWIW, not that I have a dog in this fight, but the only release with a > 4th number (not including .0 like the 0.20.20x releases did) we had > was: > > http://hadoop.6.n7.nabble.com/VOTE-Release-0-17-2-1-rc-0-td13398.html > > 0.17.2 was

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

FWIW, not that I have a dog in this fight, but the only release with a 4th number (not including .0 like the 0.20.20x releases did) we had was: http://hadoop.6.n7.nabble.com/VOTE-Release-0-17-2-1-rc-0-td13398.html 0.17.2 was missing some native libs so 0.17.2.1 was released to fix that critical i

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

On Thu, May 30, 2013 at 03:11PM, Matt Foley wrote: > Hi Cos, > I would also request that you renumber the release candidate to just > three-numbers, hence "2.0.5-alpha". > > Arun, are you willing to start the 2.1.x name-space for your next release, > so that 2.0.x-alpha can become an intermediate

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

On Thu, May 30, 2013 at 03:18PM, Chris Douglas wrote: > On Thu, May 30, 2013 at 2:39 PM, Konstantin Boudnik wrote: > > There's no misunderstanding Chris - this release is to unblock downstream. > > > > As for your question: I don't have a crystal ball; I wish though. I think > > the > > answer de

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

On Thu, May 30, 2013 at 2:39 PM, Konstantin Boudnik wrote: > There's no misunderstanding Chris - this release is to unblock downstream. > > As for your question: I don't have a crystal ball; I wish though. I think the > answer depends on will be there more blocking bugs found in the later releases

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

Hi Cos, I would also request that you renumber the release candidate to just three-numbers, hence "2.0.5-alpha". Arun, are you willing to start the 2.1.x name-space for your next release, so that 2.0.x-alpha can become an intermediate stabilization branch as Cos and Konst want? I just think that

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

There's no misunderstanding Chris - this release is to unblock downstream. As for your question: I don't have a crystal ball; I wish though. I think the answer depends on will be there more blocking bugs found in the later releases of Bigtop or other downstream components. This is bugfix release a

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

On the version number we use, if it is greater than 2.0.4, I really don't care. Though I think Konstantin argument that branch-2 is publishing as 2.0.5-SNAPSHOT has some ground (still, it could be argued that they are DEV JARs so they can be in flux). On the changes that went into this RC, they a

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

On Thu, May 30, 2013 at 10:57 AM, Arun C Murthy wrote: > Why not include MAPREDUCE-4211 as well rather than create one release per > patch? >From Cos's description, it sounded like these were backports of fixes to help Sqoop2 and fix some build issues. If it's not just to fixup leftover bugs in

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

> Why not call this 2.0.5-alpha? Technically, current branch-2 uses 2.0.5-SNAPSHOT and produces maven artifacts with that version. So having another version with the same numbers will be confusing. Therefore 4-level numbers. I thought I mentioned it to you before. Thanks, --Konst On Thu, May 30

Re: [VOTE] Release Apache Hadoop 0.23.8

+1 Downloaded the release and ran a few basic tests. --Bobby On 5/28/13 11:00 AM, "Thomas Graves" wrote: > >I've created a release candidate (RC0) for hadoop-0.23.8 that I would like >to release. > >This release is a sustaining release with several important bug fixes in >it. The most critica

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

+1 I verified checksums, the signature, built sources on CentOS, ran tests and a few hadoop commands. Thanks, --Konst On Fri, May 24, 2013 at 8:48 PM, Konstantin Boudnik wrote: > All, > > I have created a release candidate (rc0) for hadoop-2.0.4.1-alpha that I > would > like to release. > > Th

[jira] [Created] (HDFS-4868) Clean up error message when trying to snapshot using ViewFileSystem

Stephen Chu created HDFS-4868: - Summary: Clean up error message when trying to snapshot using ViewFileSystem Key: HDFS-4868 URL: https://issues.apache.org/jira/browse/HDFS-4868 Project: Hadoop HDFS

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

On Thu, May 30, 2013 at 10:57AM, Arun C Murthy wrote: > I see you just re-opened MAPREUDCE-5211. > > Why not include MAPREDUCE-5211 as well rather than create one release per > patch? Arun, it is unclear if MAPREDUCE-5211 has implications in 2.0.4 as per https://issues.apache.org/jira/browse/MA

[jira] [Created] (HDFS-4867) metaSave NPEs when there are invalid blocks in repl queue.

Kihwal Lee created HDFS-4867: Summary: metaSave NPEs when there are invalid blocks in repl queue. Key: HDFS-4867 URL: https://issues.apache.org/jira/browse/HDFS-4867 Project: Hadoop HDFS Issue Ty

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

Sorry, it should be MAPREDUCE-5211 (not MAPREDUCE-4211). thanks, Arun On May 30, 2013, at 10:57 AM, Arun C Murthy wrote: > I see you just re-opened MAPREUDCE-4211. > > Why not include MAPREDUCE-4211 as well rather than create one release per > patch? > > Also, this is the first time we are se

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

I see you just re-opened MAPREUDCE-4211. Why not include MAPREDUCE-4211 as well rather than create one release per patch? Also, this is the first time we are seeing a four-numbered scheme in Hadoop. Why not call this 2.0.5-alpha? Arun On May 24, 2013, at 8:48 PM, Konstantin Boudnik wrote: > A

Build failed in Jenkins: Hadoop-Hdfs-trunk #1415

See Changes: [sseth] YARN-719. Move RMIdentifier from Container to ContainerTokenIdentifier. Contributed by Vinod Kumar Vavilapalli. [vinodkv] HADOOP-9574. Fix for timing issues in the original patch's test-case. [vinodkv] YARN-638

Hadoop-Hdfs-trunk - Build # 1415 - Still Failing

See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1415/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 14508 lines...] [INFO] [INFO] --- maven-source-plugin:2.