Re: [VOTE] Release Apache Hadoop 2.7.2 RC2

2016-01-19 Thread Eric Payne
+1 (non-binding) - Downloaded and built the source - Installed on 3-node, non-secured cluster - Ran 2 jobs, one in preemptable queue and one not. Containers were preempted until the app in the non-preemptable queue was balanced with the app running in the preemptable queue, and then preemption

Re: [VOTE] Release Apache Hadoop 2.7.2 RC2

2016-01-19 Thread Chang Li
Thanks Vinod and Junping! +1(non-binding) -built and deployed on linux and mac successfully -ran MR jobs successfully -verified UIs work Best, Chang On Mon, Jan 18, 2016 at 11:46 PM, Arpit Agarwal wrote: > +1 (binding) > > - verified signatures > - Installed

[jira] [Resolved] (HADOOP-10372) Deprecate S3 implementation.

2016-01-19 Thread Allen Wittenauer (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-10372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-10372. --- Resolution: Duplicate Closing this as a dupe. > Deprecate S3 implementation. >

Re: [VOTE] Release Apache Hadoop 2.7.2 RC2

2016-01-19 Thread Vinod Kumar Vavilapalli
The JIRA YARN-4610 links YARN-3434 as the one causing the breakage, and YARN-3434 already exists in 2.7.1 itself. That categorizes the new issue as an existing bug. If you agree with that sentiment, and given that there is a clear work-around,

Re: [VOTE] Release Apache Hadoop 2.7.2 RC2

2016-01-19 Thread Steve Loughran
> On 14 Jan 2016, at 20:57, Vinod Kumar Vavilapalli wrote: > > Hi all, > > I've created an updated release candidate RC2 for Apache Hadoop 2.7.2. > > As discussed before, this is the next maintenance release to follow up 2.7.1. > > The RC is available for validation at:

Re: [VOTE] Release Apache Hadoop 2.7.2 RC2

2016-01-19 Thread Jason Lowe
That's reasonable, especially if we don't take nearly as long for 2.7.3.  Note that there are almost 50 JIRAs already committed to 2.7.3, so hopefully we'll have a plan for that soon. +1 (binding) for 2.7.2 RC2. Jason From: Vinod Kumar Vavilapalli To:

Jenkins build is back to normal : Hadoop-Common-trunk #2249

2016-01-19 Thread Apache Jenkins Server
See

Re: [VOTE] Release Apache Hadoop 2.7.2 RC2

2016-01-19 Thread Masatake Iwasaki
+1(non-binding) - verified mds and signature of source and binary tarball - built from source tarball with -Pnative on CentOS 7/OpenJDK 7 - built rpm by using bigtop, launched 3 nodes cluster, ran smoke test of hdfs, mapreduce, yarn - built rpm of hbase, hive, pig against 2.7.2-RC2, ran smoke

Re: [VOTE] Release Apache Hadoop 2.7.2 RC2

2016-01-19 Thread Xuan Gong
+1 (binding) - Successfully built from source - Deployed on a single node cluster - Ran a simple MR job and a distributed Shell job successfully. Thanks Xuan Gong > On Jan 19, 2016, at 3:30 PM, Jason Lowe wrote: > > That's reasonable, especially if we don't take

Re: [VOTE] Release Apache Hadoop 2.7.2 RC2

2016-01-19 Thread Akira AJISAKA
+1 (binding) - Downloaded source tarball and binary tarball - Verified signatures and checksums - Compiled and built a single node cluster - 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 successfully Thanks, Akira On

[GitHub] hadoop pull request: Creating updated branch for Hadoop-6671

2016-01-19 Thread make5020
GitHub user make5020 opened a pull request: https://github.com/apache/hadoop/pull/69 Creating updated branch for Hadoop-6671 git-svn-id: https://svn.apache.org/repos/asf/hadoop/common/branches/HADOOP-6671-2@956573 13f79535-47bb-0310-9956-ffa450edef68 You can merge this pull

Build failed in Jenkins: Hadoop-common-trunk-Java8 #948

2016-01-19 Thread Apache Jenkins Server
See Changes: [wangda] HADOOP-12356. Fix computing CPU usage statistics on Windows. (Inigo [raviprak] HADOOP-12696. Add tests for S3FileSystem Contract. Contributed by Matt --

Re: [VOTE] Release Apache Hadoop 2.7.2 RC2

2016-01-19 Thread Jason Lowe
-1 (binding) We have been running a release derived from 2.7 on some of our clusters, and we recently hit a bug where an application making large container requests can drastically slow down container allocations for other users in the same queue.  See YARN-4610 for details.  Since