Re: [VOTE] - Release 2.0.5-beta
+1 on 2.0.5 defined in this thread with the new features. But I am supportive of an earlier release that has ALL the compatibility changes, without the features. sanjay On May 15, 2013, at 10:57 AM, Arun C Murthy wrote: > Folks, > > ... > > I propose we continue the original plan and make a 2.0.5-beta release by May > end with the following content: > # HDFS-347 > # HDFS Snapshots > # Windows support > # Necessary & final API/protocol changes such as: > * Final YARN API changes: YARN-386 > * MR Binary Compatibility: MAPREDUCE-5108 > * Final RPC cleanup: HADOOP-8990
Re: Bugfix release 2.0.4.1
The build is over, all unit tests have passed. Roman, the 2.0.4.1 tarballs are available from https://builds.apache.org/job/Hadoop-branch-2.0.4/47/ For Bigtop to use as the base. Cos On Mon, May 20, 2013 at 12:15PM, Konstantin Boudnik wrote: > I have ran the full set of unit tests on the patched version and I see 3 > failures in HDFS HA stress tests, which are clearly not related to fix in > question. I will commit it shortly. > > Cos > > On Thu, May 16, 2013 at 12:03AM, Roman Shaposhnik wrote: > > On Wed, May 15, 2013 at 11:09 PM, Vinod Kumar Vavilapalli > > wrote: > > > > > > It's a little dirty, but Mark and Jarek (presumably from BigTop) ran a > > > patched version with my change at MAPREDUCE-5240. > > > > I've just updated the patch to apply cleanly on branch-2.0.4 (had to > > refactor > > quite a bit of unit tests). Hopefully Cos can apply it tomorrow and we > > can start testing Bigtop. > > > > > Otherwise we may end up creating lots of bug-fix releases. > > > > Agreed. The point of 2.0.4.1 is to unblock Bigtop 0.6.0 release. We're > > trying to come with stable base line for Hadoop 2.0.x where > > all the downstream components will be running smoothly. > > > > At this point a MAPREDUCE-5240 is the only thing holding us > > up, but once we start our own round of testing other issues > > could pop up. We shall see how it goes. > > > > Thanks, > > Roman. signature.asc Description: Digital signature
Re: [VOTE] Plan to create release candidate for 0.23.8
+1 On 5/17/13 4:10 PM, "Thomas Graves" wrote: >Hello all, > >We've had a few critical issues come up in 0.23.7 that I think warrants a >0.23.8 release. The main one is MAPREDUCE-5211. There are a couple of >other issues that I want finished up and get in before we spin it. Those >include HDFS-3875, HDFS-4805, and HDFS-4835. I think those are on track >to finish up early next week. So I hope to spin 0.23.8 soon after this >vote completes. > >Please vote '+1' to approve this plan. Voting will close on Friday May >24th at 2:00pm PDT. > >Thanks, >Tom Graves >
[jira] [Created] (HADOOP-9582) Non-existent file to "hadoop fs -conf" doesn't throw error
Ashwin Shankar created HADOOP-9582: -- Summary: Non-existent file to "hadoop fs -conf" doesn't throw error Key: HADOOP-9582 URL: https://issues.apache.org/jira/browse/HADOOP-9582 Project: Hadoop Common Issue Type: Bug Components: conf Affects Versions: 2.0.4-alpha, 0.23.7, 3.0.0 Reporter: Ashwin Shankar When we run : hadoop fs -conf BAD_FILE -ls / we expect hadoop to throw an error,but it doesn't. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-9581) Hadoop --config non-existent directory should result in error
Ashwin Shankar created HADOOP-9581:
--
Summary: Hadoop --config non-existent directory should result in
error
Key: HADOOP-9581
URL: https://issues.apache.org/jira/browse/HADOOP-9581
Project: Hadoop Common
Issue Type: Bug
Components: scripts
Affects Versions: 2.0.4-alpha, 0.23.7, 3.0.0
Reporter: Ashwin Shankar
Courtesy : [~cwchung]
{quote}Providing a non-existent config directory should result in error.
$ hadoop dfs -ls / : shows Hadoop DFS directory
$ hadoop --config bad_config_dir dfs -ls : successful, showing Linux directory
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Plan to create release candidate for 0.23.8
+1 (non-binding) On Mon, May 20, 2013 at 11:13 AM, Siddharth Seth wrote: > +1. > > > On Fri, May 17, 2013 at 2:10 PM, Thomas Graves >wrote: > > > Hello all, > > > > We've had a few critical issues come up in 0.23.7 that I think warrants a > > 0.23.8 release. The main one is MAPREDUCE-5211. There are a couple of > > other issues that I want finished up and get in before we spin it. Those > > include HDFS-3875, HDFS-4805, and HDFS-4835. I think those are on track > > to finish up early next week. So I hope to spin 0.23.8 soon after this > > vote completes. > > > > Please vote '+1' to approve this plan. Voting will close on Friday May > > 24th at 2:00pm PDT. > > > > Thanks, > > Tom Graves > > > > >
Re: Bugfix release 2.0.4.1
I have ran the full set of unit tests on the patched version and I see 3 failures in HDFS HA stress tests, which are clearly not related to fix in question. I will commit it shortly. Cos On Thu, May 16, 2013 at 12:03AM, Roman Shaposhnik wrote: > On Wed, May 15, 2013 at 11:09 PM, Vinod Kumar Vavilapalli > wrote: > > > > It's a little dirty, but Mark and Jarek (presumably from BigTop) ran a > > patched version with my change at MAPREDUCE-5240. > > I've just updated the patch to apply cleanly on branch-2.0.4 (had to refactor > quite a bit of unit tests). Hopefully Cos can apply it tomorrow and we > can start testing Bigtop. > > > Otherwise we may end up creating lots of bug-fix releases. > > Agreed. The point of 2.0.4.1 is to unblock Bigtop 0.6.0 release. We're > trying to come with stable base line for Hadoop 2.0.x where > all the downstream components will be running smoothly. > > At this point a MAPREDUCE-5240 is the only thing holding us > up, but once we start our own round of testing other issues > could pop up. We shall see how it goes. > > Thanks, > Roman.
Re: [VOTE] Plan to create release candidate for 0.23.8
+1. On Fri, May 17, 2013 at 2:10 PM, Thomas Graves wrote: > Hello all, > > We've had a few critical issues come up in 0.23.7 that I think warrants a > 0.23.8 release. The main one is MAPREDUCE-5211. There are a couple of > other issues that I want finished up and get in before we spin it. Those > include HDFS-3875, HDFS-4805, and HDFS-4835. I think those are on track > to finish up early next week. So I hope to spin 0.23.8 soon after this > vote completes. > > Please vote '+1' to approve this plan. Voting will close on Friday May > 24th at 2:00pm PDT. > > Thanks, > Tom Graves > >
[jira] [Created] (HADOOP-9580) Jenkins should run all the tests irrespective of which module was updated
Omkar Vinit Joshi created HADOOP-9580: - Summary: Jenkins should run all the tests irrespective of which module was updated Key: HADOOP-9580 URL: https://issues.apache.org/jira/browse/HADOOP-9580 Project: Hadoop Common Issue Type: Bug Reporter: Omkar Vinit Joshi It is observed that Jenkins only run certain set of tests both when we submit the patch and when it is committed. At the time of commit, (as a part of pre commit build) It should run all these tests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Plan to create release candidate for 0.23.8
+1 -- Arpit Gupta Hortonworks Inc. http://hortonworks.com/ On May 17, 2013, at 2:10 PM, Thomas Graves wrote: > Hello all, > > We've had a few critical issues come up in 0.23.7 that I think warrants a > 0.23.8 release. The main one is MAPREDUCE-5211. There are a couple of > other issues that I want finished up and get in before we spin it. Those > include HDFS-3875, HDFS-4805, and HDFS-4835. I think those are on track > to finish up early next week. So I hope to spin 0.23.8 soon after this > vote completes. > > Please vote '+1' to approve this plan. Voting will close on Friday May > 24th at 2:00pm PDT. > > Thanks, > Tom Graves >
Re: [VOTE] Plan to create release candidate for 0.23.8
Thanks Chris, I'll take a look at HDFS-3180. Tom On 5/19/13 12:54 PM, "Chris Nauroth" wrote: >+1 (non-binding) > >BTW, I left a comment on HDFS-4835 suggesting that you include HDFS-3180 >for WebHDFS socket connect/read timeouts. It's up to you. (I'm voting +1 >for the release plan either way.) > >Chris Nauroth >Hortonworks >http://hortonworks.com/ > > > >On Fri, May 17, 2013 at 7:25 PM, Eli Collins wrote: > >> +1 >> >> On Friday, May 17, 2013, Thomas Graves wrote: >> >> > Hello all, >> > >> > We've had a few critical issues come up in 0.23.7 that I think >>warrants a >> > 0.23.8 release. The main one is MAPREDUCE-5211. There are a couple of >> > other issues that I want finished up and get in before we spin it. >>Those >> > include HDFS-3875, HDFS-4805, and HDFS-4835. I think those are on >>track >> > to finish up early next week. So I hope to spin 0.23.8 soon after >>this >> > vote completes. >> > >> > Please vote '+1' to approve this plan. Voting will close on Friday May >> > 24th at 2:00pm PDT. >> > >> > Thanks, >> > Tom Graves >> > >> > >>
