] Release Apache Hadoop 2.7.2 RC1
Okay, did a whole bunch of things on 2.7.2.
Fixing CHANGES.txt entry that Junping reported on the voting thread
- 56e2dcc HADOOP-5323. Trash documentation should describe its directory
structure and configurations. (Weiwei Yang via ozawa) Moved entry from HDFS
rg
>> <mailto:mapreduce-...@hadoop.apache.org>; yarn-...@hadoop.apache.org
>> <mailto:yarn-...@hadoop.apache.org>; common-...@hadoop.apache.org
>> <mailto:common-...@hadoop.apache.org>; hdfs-dev@hadoop.apache.org
>> <mailto:hdfs-dev@hadoop.apache.org>
>> Su
mon-...@hadoop.apache.org>;
> hdfs-dev@hadoop.apache.org <mailto:hdfs-dev@hadoop.apache.org>
> Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
>
> I retract my -1. I think we will need to discuss this a bit more.
>
> Beyond those two tickets, there are a bunch
On Mon, Jan 11, 2016 at 7:22 AM, Junping Du wrote:
> bq. Is it difficult to backport to 2.7.x if you're already backporting to
> 2.6.x? I don't follow why special casing some class of fixes is desirable.
> It is not difficult to backport the commits between 2.6.x and 2.7.x.
> However, it do *dif
ouldn't break it.
Thanks,
Junping
From: Andrew Wang
Sent: Friday, January 08, 2016 7:43 PM
To: common-...@hadoop.apache.org
Cc: mapreduce-...@hadoop.apache.org; Vinod Kumar Vavilapalli;
yarn-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org
Subject: Re: [VOTE] Release Apache Hadoop 2.
d be trivial (test case fix,
> >> etc.) enough to deserve more flexibility. I would prefer this rule only
> >> applies on critical/blocker fixes, but not applies on minor/trivial
> issues.
> >>
> >> Just 2 cents.
> >>
> >>
> >>
Junping
>>
>>
>> ____
>> From: Vinod Kumar Vavilapalli
>> Sent: Thursday, December 24, 2015 12:47 AM
>> To: Junping Du
>> Cc: mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org;
>> common-...@hadoop.apache.org; hdfs-dev@had
.org; hdfs-dev@hadoop.apache.org
Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
I retract my -1. I think we will need to discuss this a bit more.
Beyond those two tickets, there are a bunch more (totaling to 16) that are in 2.6.3
but *not* in 2.7.2. See this:
https://issues.apache.org/jira/
ct: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
I retract my -1. I think we will need to discuss this a bit more.
Beyond those two tickets, there are a bunch more (totaling to 16) that are in
2.6.3 but *not* in 2.7.2. See this:
https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2
+1 on cherry-picking the fixes into 2.7.2.
-Varun
On 12/25/15, 9:08 AM, "Akira AJISAKA" wrote:
>Thanks Vinod for starting the discussion.
>I'm +1 for cherry-picking these issues to 2.7.2.
>
>As Andrew said, when users upgrade Hadoop from 2.6.3 to 2.7.2,
>they can hit the issues.
>I'm thinkin
Thanks Vinod for starting the discussion.
I'm +1 for cherry-picking these issues to 2.7.2.
As Andrew said, when users upgrade Hadoop from 2.6.3 to 2.7.2,
they can hit the issues.
I'm thinking we should reduce the regressions as possible.
Regards,
Akira
On 12/25/15 01:56, Andrew Wang wrote:
My
My 2c is that we should have monotonicity in releases. That way no
"upgrade" is a regression.
On Wed, Dec 23, 2015 at 10:00 PM, Tsuyoshi Ozawa wrote:
> Hi Vinod,
>
> thank you for the clarification.
>
> > - Pull these 16 tickets into 2.7.2 and roll a new RC
> > > What do people think? Do folks
Hi Vinod,
thank you for the clarification.
> - Pull these 16 tickets into 2.7.2 and roll a new RC
> > What do people think? Do folks expect “any fix in 2.6.3 to be there in all
> > releases that get out after 2.6.3 release date (December 16th)”?
I personally prefer to pull these tickets into 2
I retract my -1. I think we will need to discuss this a bit more.
Beyond those two tickets, there are a bunch more (totaling to 16) that are in
2.6.3 but *not* in 2.7.2. See this:
https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2
Sigh. Missed this.
To retain causality ("any fix in 2.6.3 will be there in all releases that got
out after 2.6.3”), I’ll get these patches in.
Reverting my +1, and casting -1 for the RC myself.
Will spin a new RC, this voting thread is marked dead.
Thanks
+Vinod
> On Dec 22, 2015, at 8:24 AM,
+1 (non-binding)
1. Download the src tar file and validate the integrity
2. Build and configure the local cluster
3. Operate the HDFS from command line interface
4. Run several example MR jobs
5. Check logs
Thanks.
L
> On Dec 16, 2015, at 6:49 PM, Vinod Kumar Vavilapalli
> wrote:
>
> Hi all,
M
To: mapreduce-...@hadoop.apache.org
Cc: common-...@hadoop.apache.org; yarn-...@hadoop.apache.org;
hdfs-dev@hadoop.apache.org; Vinod Kumar Vavilapalli
Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
+1 (non binding)
Downloaed src and built on single node cluster.
Ran some MR jobs successfully.
Veri
+1 (non binding)
Downloaed src and built on single node cluster.
Ran some MR jobs successfully.
Verified signature.
Thanks,
Chang
On Mon, Dec 21, 2015 at 9:34 PM, Tsuyoshi Ozawa wrote:
> +1
>
> - downloaded src and bin tar balls and verified signatures.
> - built Tez and Spark with 2.7.2 artifa
K S
-Original Message-
From: Tsuyoshi Ozawa [mailto:oz...@apache.org]
Sent: 22 December 2015 09:04
To: common-...@hadoop.apache.org
Cc: yarn-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
mapreduce-...@hadoop.apache.org; Vinod Kumar Vavilapalli
Subject: Re: [VOTE] Release Apache Ha
+1
- downloaded src and bin tar balls and verified signatures.
- built Tez and Spark with 2.7.2 artifacts and JDK7.
- ran tests of Tez with 2.7.2 artifacts, it passed.
FYI: YARN-4348, reported by Jian, is one of critical issues of 2.7.2
release.It's better to release 2.7.3 as soon as possible aft
Thanks for putting together this release Vinod.
+1 (binding)
- Verified signatures
- Started pseudo-cluster with binary distribution, verified git commit ID
- Built sources, deployed pseudo-cluster and ran example map reduce jobs,
DistributedShell, HDFS commands.
PS: Extra file hadoop-2.7.2
+1 (binding)
Thanks
Xuan Gong
> On Dec 21, 2015, at 4:25 PM, Chen He wrote:
>
> +1 (non-binding)
>
> deploy to a 2-node cluster
> run loadgen and wc without problem
>
>
> Kindly ask a silly question, why we separate 2.6.x from 2.7.x?
>
> On Mon, Dec 21, 2015 at 11:51 AM, Wangda Tan wrote:
+1 (binding)
- Build & deploy single-node Hadoop from source code
- Add/Remove node labels to queues/nodes
- Run distributed shell commanding using default/specified node labels
Thanks,
Wangda
On Mon, Dec 21, 2015 at 9:58 AM, Masatake Iwasaki <
iwasak...@oss.nttdata.co.jp> wrote:
> +1(non-bind
+1(non-binding)
- verified mds and signature of source and binary tarball
- started 3 node cluster and ran example jobs such as wordcount and terasort
- built from source tarball with -Pnative on CentOS 7 and OpenJDK 7
- built site documentation and skimmed the contents
Thanks,
Masatake Iwasaki
+1 (binding)- Verified the signature/digest.
- I've built the dist tree with the native support from the source.- Brought up
a single node cluster and ran a set of basic tests.
From: Vinod Kumar Vavilapalli
To: Hadoop Common ; hdfs-dev@hadoop.apache.org;
yarn-...@hadoop.apache.org; ma
+1 (binding)
- Downloaded source tarball
- Verified signatures and checksums
- Compiled and built a single node cluster
- Confirmed commons-collections is upgraded to 3.2.2
- Compiled Hive 1.2.1 and Tez 0.7.0/0.8.1-alpha using Hadoop 2.7.2 pom
successfully
- Ran some Hive on Tez/MRv2 queries su
+1 (binding)
- Verified signatures and digests- Spot checked CHANGES.txt files- Successfully
performed a native build from source- Deployed to a single node cluster and ran
sample jobs
We have been running with the fix for YARN-4354 on two of our clusters for some
time with no issues, so I feel
Hi,
I have run test suite for tip of hbase 0.98 branch against this RC.
All tests passed.
+1
On Wed, Dec 16, 2015 at 6:49 PM, Vinod Kumar Vavilapalli wrote:
> Hi all,
>
> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>
> As discussed before, this is the next maintenance release
28 matches
Mail list logo
