With 9 +1s including mine (6 binding) and no -1s, the vote passes. Thanks to
all who voted.
Arun
On Aug 15, 2013, at 2:15 PM, Arun C Murthy wrote:
> Folks,
>
> I've created a release candidate (rc2) for hadoop-2.1.0-beta that I would
> like to get released - this fixes the bugs we saw since
+1, binding
Review process
# symlink /usr/local/bin/protoc to the homebrew installed 2.5.0 version
# delete all 2.1.0-beta artifacts in the mvn repo:
find ~/.m2 -name 2.1.0-beta -print | xargs rm -rf
# checkout hbase apache/branch-0.95 (commit # b58d596 )
# switch to ASF repo (arun's privat
] Release Apache Hadoop 2.1.0-beta
+1 (binding)
Verified checksums, built from source and ran basic MR jobs on a
single-node cluster.
-- Hitesh
On Aug 15, 2013, at 2:15 PM, Arun C Murthy wrote:
> Folks,
>
> I've created a release candidate (rc2) for hadoop-2.1.0-beta that I
wou
+1 non-binding
Verified signatures and checksums one binary and source tar files
Built the source
Ran some tests on psuedo-distributed cluster.
Rob
On 08/15/2013 09:15 PM, Arun C Murthy wrote:
Folks,
I've created a release candidate (rc2) for hadoop-2.1.0-beta that I would like
to get releas
On Wed, Aug 21, 2013 at 3:49 PM, Stack wrote:
> On Wed, Aug 21, 2013 at 1:25 PM, Colin McCabe wrote:
>
>> St.Ack wrote:
>>
>> > + Once I figured where the logs were, found that JAVA_HOME was not being
>> > exported (don't need this in hadoop-2.0.5 for instance). Adding an
>> > exported JAVA_HOME
+1 (binding)
Verified checksums, built from source and ran basic MR jobs on a single-node
cluster.
-- Hitesh
On Aug 15, 2013, at 2:15 PM, Arun C Murthy wrote:
> Folks,
>
> I've created a release candidate (rc2) for hadoop-2.1.0-beta that I would
> like to get released - this fixes the bugs
+1 (binding)
- verified signatures and checksums
- built from source
- ran some simple jobs on a single-node cluster
On 08/15/2013 04:15 PM, Arun C Murthy wrote:
Folks,
I've created a release candidate (rc2) for hadoop-2.1.0-beta that I would like
to get released - this fixes the bugs we saw
On Wed, Aug 21, 2013 at 1:25 PM, Colin McCabe wrote:
> St.Ack wrote:
>
> > + Once I figured where the logs were, found that JAVA_HOME was not being
> > exported (don't need this in hadoop-2.0.5 for instance). Adding an
> > exported JAVA_HOME to my running shell which don't seem right but it took
+1 (binding).
Verified signature and checksums.
Built from source and upgraded a 2.0.4 cluster. Ran a couple of simple MR
and Tez jobs.
- Sid
On Thu, Aug 15, 2013 at 2:15 PM, Arun C Murthy wrote:
> Folks,
>
> I've created a release candidate (rc2) for hadoop-2.1.0-beta that I would
> like to
St.Ack wrote:
> + Once I figured where the logs were, found that JAVA_HOME was not being
> exported (don't need this in hadoop-2.0.5 for instance). Adding an
> exported JAVA_HOME to my running shell which don't seem right but it took
> care of it (I gave up pretty quick on messing w/
> yarn.nodem
Thanks for the heads up Aaron, I've changed fix-version of HDFS-4763 to
2.1.1-beta for now.
Committers - please be careful setting fix-versions, this is a good
anti-pattern to avoid… though, I'm willing to bet a lot of dough that this
isn't the first Hadoop release with this issue… *smile*
Aru
I was evaluating the release bits when I noticed that the change done in
HDFS-4763 to add support for starting the HDFS NFSv3 gateway, which is
marked with a "fix version" of 2.1.0-beta and included in the release notes
of RC2, is not in fact included in the RC2 release bits. It looks to me
like th
On Thu, Aug 15, 2013 at 2:15 PM, Arun C Murthy wrote:
> Folks,
>
> I've created a release candidate (rc2) for hadoop-2.1.0-beta that I would
> like to get released - this fixes the bugs we saw since the last go-around
> (rc1).
>
> The RC is available at:
> http://people.apache.org/~acmurthy/hadoo
Roman.
>>>>
>>>> On Fri, Aug 16, 2013 at 3:04 PM, Kihwal Lee wrote:
>>>>> I've changed the target version of HADOOP-9880 to 2.1.1. Please change
>>>>> it back, if you feel that it needs to be in 2.1.0-beta.
>>>>>
>>>&g
t; back, if you feel that it needs to be in 2.1.0-beta.
>>>>
>>>>
>>>> Kihwal
>>>>
>>>>
>>>> ____________
>>>> From: Kihwal Lee
>>>> To: Arun Murthy ; "common-...@hadoop.apache.org"
t;>
>>>
>>>
>>> From: Kihwal Lee
>>> To: Arun Murthy ; "common-...@hadoop.apache.org"
>>>
>>> Cc: "mapreduce-...@hadoop.apache.org" ;
>>> "hdfs-dev@hadoop.apache.org" ;
>>>
gt;> Cc: "mapreduce-...@hadoop.apache.org" ;
>> "hdfs-dev@hadoop.apache.org" ;
>> "yarn-...@hadoop.apache.org"
>> Sent: Friday, August 16, 2013 4:55 PM
>> Subject: Re: [VOTE] Release Apache Hadoop 2.1.0-beta
>>
>>
>> It'
he.org" ;
"hdfs-dev@hadoop.apache.org" ;
"yarn-...@hadoop.apache.org"
Sent: Friday, August 16, 2013 4:55 PM
Subject: Re: [VOTE] Release Apache Hadoop 2.1.0-beta
It's your call, Arun. I.e. as long you believe rc2 meets the expectations and
objectives of 2.1.0-bet
ev@hadoop.apache.org"
; "yarn-...@hadoop.apache.org"
Sent: Friday, August 16, 2013 3:44 PM
Subject: Re: [VOTE] Release Apache Hadoop 2.1.0-beta
That makes sense too.
On Aug 16, 2013, at 10:39 AM, Vinod Kumar Vavilapalli
wrote:
>
> We need to make a call on what block
rg" ;
>> "mapreduce-...@hadoop.apache.org" ;
>> "yarn-...@hadoop.apache.org"
>> Sent: Thursday, August 15, 2013 4:15 PM
>> Subject: [VOTE] Release Apache Hadoop 2.1.0-beta
>>
>>
>> Folks,
>>
>> I've created a r
gt; From: Arun C Murthy
> To: "common-...@hadoop.apache.org" ;
> "hdfs-dev@hadoop.apache.org" ;
> "mapreduce-...@hadoop.apache.org" ;
> "yarn-...@hadoop.apache.org"
> Sent: Thursday, August 15, 2013 4:15 PM
> Subject: [VOTE] Release
_
> From: Arun C Murthy
> To: "common-...@hadoop.apache.org" ;
> "hdfs-dev@hadoop.apache.org" ;
> "mapreduce-...@hadoop.apache.org" ;
> "yarn-...@hadoop.apache.org"
> Sent: Thursday, August 15, 2013 4:15 PM
>
;yarn-...@hadoop.apache.org"
Sent: Thursday, August 15, 2013 4:15 PM
Subject: [VOTE] Release Apache Hadoop 2.1.0-beta
Folks,
I've created a release candidate (rc2) for hadoop-2.1.0-beta that I would like
to get released - this fixes the bugs we saw since the last go-around (rc1).
The
;yarn-...@hadoop.apache.org"
Sent: Thursday, August 15, 2013 4:15 PM
Subject: [VOTE] Release Apache Hadoop 2.1.0-beta
Folks,
I've created a release candidate (rc2) for hadoop-2.1.0-beta that I would like
to get released - this fixes the bugs we saw since the last go-around (rc1).
The
Folks,
I've created a release candidate (rc2) for hadoop-2.1.0-beta that I would like
to get released - this fixes the bugs we saw since the last go-around (rc1).
The RC is available at:
http://people.apache.org/~acmurthy/hadoop-2.1.0-beta-rc2/
The RC tag in svn is here:
http://svn.apache.org/
sday, August 1, 2013 1:30 PM
Subject: Re: [VOTE] Release Apache Hadoop 2.1.0-beta
Ok, thanks for heads up Daryn. I'll spin an RC2 once HADOOP-9816 gets in - I'd
appreciate if you could help push the fix in ASAP.
Thanks again!
Arun
On Aug 1, 2013, at 9:38 AM, Daryn Sharp wrote:
&
+1 (non-binding)
* verified md5 of the source code.
* build the package from source code.
* run basic hdfs commands.
* run MapReduce example jobs(random text writer, wordcount, and pi)
over YARN in single node.
- Tsuyoshi
On Tue, Jul 30, 2013 at 10:29 PM, Arun C Murthy wrote:
> Folks,
>
> I've
On 30 July 2013 14:29, Arun C Murthy wrote:
> Folks,
>
> I've created another release candidate (rc1) for hadoop-2.1.0-beta that I
> would like to get released. This RC fixes a number of issues reported on
> the previous candidate.
>
> This release represents a *huge* amount of work done by the c
Ok, thanks for heads up Daryn. I'll spin an RC2 once HADOOP-9816 gets in - I'd
appreciate if you could help push the fix in ASAP.
Thanks again!
Arun
On Aug 1, 2013, at 9:38 AM, Daryn Sharp wrote:
> I broke RPC QOP for integrity and privacy options. :( See blocker
> HADOOP-9816. I think I u
I broke RPC QOP for integrity and privacy options. :( See blocker HADOOP-9816.
I think I understand the problem and it shouldn't be hard to fix.
The bug went unnoticed because sadly there are no unit tests for the QOP
options, even though it just involves a conf setting.
Daryn
On Jul 29, 20
Apache Hadoop 2.1.0-beta
Folks,
I've created another release candidate (rc1) for hadoop-2.1.0-beta that I
would like to get released. This RC fixes a number of issues reported on
the previous candidate.
This release represents a *huge* amount of work done by the community
(~650 fixes)
Thanks Arun,
+1
* verified MD5 & signature of source tarball.
* built from source tarball
* run apache-rat:check on source
* installed pseudo cluster (unsecure)
* test httpfs
* run pi example
* run unmanaged AM application
Minor NITs (in case we do a new RC):
* remove 2.1.1.-beta section from a
Folks,
I've created another release candidate (rc1) for hadoop-2.1.0-beta that I would
like to get released. This RC fixes a number of issues reported on the previous
candidate.
This release represents a *huge* amount of work done by the community (~650
fixes) which includes several major adva
Ok, I think we are close to rc1 now - the last of blockers should be committed
later today… I'll try and spin RC1 tonight.
thanks,
Arun
On Jul 21, 2013, at 12:43 AM, Devaraj Das wrote:
> I have just raised https://issues.apache.org/jira/browse/HDFS-5016 .. This
> bug can easily be reproduced b
I have just raised https://issues.apache.org/jira/browse/HDFS-5016 .. This
bug can easily be reproduced by some HBase tests. I'd like this to be
considered before we make a beta release. Have spoken about this with some
hdfs folks offline and I am told that it is being worked on.
Thanks
Devaraj
As I've mentioned in my previous email, if we get YARN-701 in, we should
also get in the fix for unmanaged AMs in an un-secure setup in 2.1.0-beta.
Else is a regression of a functionality it is already working.
Because of that, to avoid continuing delaying the release, I'm suggesting
to mention in
On Jul 17, 2013, at 1:04 PM, Alejandro Abdelnur wrote:
> * YARN-701
>
> It should be addressed before a GA release.
>
> Still, as it is this breaks unmanaged AMs and to me
> that would be a blocker for the beta.
>
> YARN-701 and the unmanaged AMs fix should be committed
> in tandem.
>
> * YAR
Vinod,
Thanks for reviving this thread.
The current blockers are:
https://issues.apache.org/jira/issues/?jql=project%20in%20(hadoop%2C%20mapreduce%2C%20hdfs%2C%20yarn)%20and%20status%20in%20(open%2C%20'patch%20available')%20and%20priority%20%3D%20blocker%20and%20%22Target%20Version%2Fs%22%20%3D%
Looks like this RC has gone stale and lots of bug fixes went into 2.1 and 2.1.0
branches and there are 4-5 outstanding blockers. And from what I see in
CHANGES.txt files there seems to be a confusion about which branch to get in
what.
I'm blowing off the current 2.1.0 release branch so that we
I committed MAPREDUCE-5358 to branch-2 but did not commit it to
branch-2.1-beta since it wasn't a blocker and Arun was in the middle of
cutting the release.
Arun, if you feel it's appropriate to put this in branch-2.1-beta feel
free to pull it in or let me know. Thanks!
Jason
On 07/03/2013
We should get these in, looking at them now.
Thanks,
+Vinod
On Jun 28, 2013, at 12:03 PM, Hitesh Shah wrote:
> Hi Arun,
>
> From a YARN perspective, YARN-791 and YARN-727 are 2 jiras that may
> potentially change the apis. They can implemented in a backward compat
> fashion if committed aft
Hi Arun,
Some bug fixes about MapReduce should be included in next release.
MAPREDUCE-5221 should be merged because it's a lost feature of MRv2
compared to MRv1.
MAPREDUCE-5358 and MAPREDUCE-5335 are very trivial fixes, so it can be
merged immediately.
# I sent the previous email only to hdfs-dev
Hi Arun,
I think MAPREDUCE-5221 should be merged because it's a missing feature
from MRv1.
Thanks,
Tsuyoshi
On Wed, Jul 3, 2013 at 9:10 AM, Ramya Sunil wrote:
> -1.
> Some of the cli and distcp system tests which use hftp:// and webhdfs://
> are failing on secure cluster (HDFS-4841 and HDFS-495
-1.
Some of the cli and distcp system tests which use hftp:// and webhdfs://
are failing on secure cluster (HDFS-4841 and HDFS-4952/HDFS-4896). This is
a regression and we need to make sure they work before we call a release.
On Wed, Jun 26, 2013 at 1:17 AM, Arun C Murthy wrote:
> Folks,
>
> I'
Thanks Hitesh & Roman, I'll roll RC1 once these are fixed.
Arun
On Jun 28, 2013, at 12:25 PM, Roman Shaposhnik wrote:
> I think it would very useful if somebody more familiar with HDFS
> (Suresh?) could take a look at:
> https://issues.apache.org/jira/browse/HDFS-4940
>
> Suresh was very h
Hi Arun,
From a YARN perspective, YARN-791 and YARN-727 are 2 jiras that may potentially
change the apis. They can implemented in a backward compat fashion if committed
after 2.1.0. However, this will require adding of differently-named apis (
different urls in case of the webservices ) and ma
Folks,
I've created a release candidate (rc0) for hadoop-2.1.0-beta that I would like
to get released.
This release represents a *huge* amount of work done by the community (639
fixes) which includes several major advances including:
# HDFS Snapshots
# Windows support
# YARN API stabilization
#
47 matches
Mail list logo
