Thanks Andrew for the great effort! Here is my late vote.
+1 (binding)
- Verified checksums and signatures of tarballs
- Built source with native, Oracle Java 1.8.0_152 on Mac OS X 10.13.2
- Verified cloud connectors:
- S3A integration tests (perf tests skipped)
- Deployed
Yes, JIRAs will be filed, the wiki-page idea from YARN meetup is to record all
combinations of testing that need to be done and correspondingly capture all
the testing that someone in the community has already done and record it for
future perusal.
From what you are saying, I guess we haven't
Good stuff Andrew, and thanks everyone!
+Vinod
> On Dec 13, 2017, at 1:05 PM, Andrew Wang wrote:
>
> To close this out, the vote passes successfully with 13 binding +1s, 5
> non-binding +1s, and no -1s. Thanks everyone for voting! I'll work on staging.
>
release.
> >
> >
> > Thanks,
> >
> > Junping
> >
> >
> > From: Robert Kanter <rkan...@cloudera.com>
> > Sent: Tuesday, December 12, 2017 3:10 PM
> > To: Arun Suresh
> > Cc: Andrew Wang;
; Myers; common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org;
> yarn-...@hadoop.apache.org; mapreduce-dev@hadoop.apache.org
> Subject: Re: [VOTE] Release Apache Hadoop 3.0.0 RC1
>
> +1 (binding)
>
> + Downloaded the binary release
> + Deployed on a 3 node cluster on CentO
Looked at RC1. Went through my usual check-list. Here's my summary.
+1 (binding) overall
Verification
- [Check] Successful recompilation from source tar-ball
- [Check] Signature verification
- [Check] Generating dist tarballs from source tar-ball
- [Check] Validating the layout of the binary
Thanks Andrew again,
+1 (binding)
* Downloaded source tarball, and compiled with native libs
successfully: -Pdist,native -Drequire.isal -Drequire.snappy
-Drequire.openssl -Drequire.zstd.
* hadoop checknative ran successfully.
* Upgraded a fsimage that was previously used in a Hadoop 2.6-based
+1 (non-binding)
* Verified md5 of all artifacts
* Built with -Pdist
* Ran several s3a shell commands
* Started a pseudo-distributed HDFS and YARN cluster
* Ran grep and pi MR examples
* Sanity-checked contents of release notes, rat report, and changes
On Fri, Dec 8, 2017 at 1:31 PM, Andrew Wang
Thanks Andrew for driving this.
+1 (Binding)
Ran SLS + CS's Perf unit test and saw similar performance compared to
trunk.
Compiled from source, deployed single node cluster and ran several jobs.
Best,
Wangda
On Wed, Dec 13, 2017 at 7:29 AM, Sunil G wrote:
> +1
+1 (binding)
Thanks Andrew Wang for driving this effort and also thanks to all others
who helped in this release. Kudos!!!
I tested this RC by building it from source. I met with couple of issues
(not blocker) HADOOP-15116 and YARN-7650. This could be tracked separately.
- Ran many MR apps
+1 (non-binding),Thanks Andrew wang for driving this.
---Built from the source
--Installed 3 Node HA cluster
--Verified Basic shell commands
--Ran Sample jobs like pi,wordcount
--Verified the UI's
--Brahma Reddy Battula
-Original Message-
From: Andrew Wang
+1 (binding)
- built from source and deployed 3 node cluster
- installed RM HA cluster along with ATSv2 enabled and new YARN UI.
- verified for
-- RM HA switch / RM Restart / RM Work preserving restart
-- NM work preserving restart
-- Ran sample MR jobs and Distributed shell along with multiple
> > To: Arun Suresh
> > Cc: Andrew Wang; Lei Xu; Wei-Chiu Chuang; Ajay Kumar; Xiao Chen; Aaron T.
> > Myers; common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org;
> > yarn-...@hadoop.apache.org; mapreduce-dev@hadoop.apache.org
> > Subject: Re: [VOTE] Release Apache
n T.
> Myers; common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org;
> yarn-...@hadoop.apache.org; mapreduce-dev@hadoop.apache.org
> Subject: Re: [VOTE] Release Apache Hadoop 3.0.0 RC1
>
> +1 (binding)
>
> + Downloaded the binary release
> + Deployed on a 3 node cluster
ce-dev@hadoop.apache.org
Subject: Re: [VOTE] Release Apache Hadoop 3.0.0 RC1
+1 (binding)
+ Downloaded the binary release
+ Deployed on a 3 node cluster on CentOS 7.3
+ Ran some MR jobs, clicked around the UI, etc
+ Ran some CLI commands (yarn logs, etc)
Good job everyone on Hadoop 3!
- Robert
On Tue,
+1 (binding)
+ Downloaded the binary release
+ Deployed on a 3 node cluster on CentOS 7.3
+ Ran some MR jobs, clicked around the UI, etc
+ Ran some CLI commands (yarn logs, etc)
Good job everyone on Hadoop 3!
- Robert
On Tue, Dec 12, 2017 at 1:56 PM, Arun Suresh wrote:
>
+1 (binding)
- Verified signatures of the source tarball.
- built from source - using the docker build environment.
- set up a pseudo-distributed test cluster.
- ran basic HDFS commands
- ran some basic MR jobs
Cheers
-Arun
On Tue, Dec 12, 2017 at 1:52 PM, Andrew Wang
Hi everyone,
As a reminder, this vote closes tomorrow at 12:31pm, so please give it a
whack if you have time. There are already enough binding +1s to pass this
vote, but it'd be great to get additional validation.
Thanks to everyone who's voted thus far!
Best,
Andrew
On Tue, Dec 12, 2017 at
+1 (binding)
* Verified src tarball and bin tarball, verified md5 of each.
* Build source with -Pdist,native
* Started a pseudo cluster
* Run ec -listPolicies / -getPolicy / -setPolicy on / , and run hdfs
dfs put/get/cat on "/" with XOR-2-1 policy.
Thanks Andrew for this great effort!
Best,
Hi Wei-Chiu,
The patchprocess directory is left over from the create-release process,
and it looks empty to me. We should still file a create-release JIRA to fix
this, but I think this is not a blocker. Would you agree?
Best,
Andrew
On Tue, Dec 12, 2017 at 9:44 AM, Wei-Chiu Chuang
Hi Andrew, thanks the tremendous effort.
I found an empty "patchprocess" directory in the source tarball, that is
not there if you clone from github. Any chance you might have some leftover
trash when you made the tarball?
Not wanting to nitpicking, but you might want to double check so we don't
+1 (binding)
- downloaded src tarball, verified md5
- built from source with jdk1.8.0_112
- started a pseudo cluster with hdfs and kms
- sanity checked encryption related operations working
- sanity checked webui and logs.
-Xiao
On Mon, Dec 11, 2017 at 6:10 PM, Aaron T. Myers
Sorry, forgot to push the tag. It's up there now.
On Sun, Dec 10, 2017 at 8:31 PM, Vinod Kumar Vavilapalli wrote:
> I couldn't find the release tag for RC1 either - is it just me or has the
> release-process changed?
>
> +Vinod
>
> > On Dec 10, 2017, at 4:31 PM, Sangjin Lee
+1 (binding)
- downloaded the src tarball and built the source (-Pdist -Pnative)
- verified the checksum
- brought up a secure pseudo distributed cluster
- did some basic file system operations (mkdir, list, put, cat) and
confirmed that everything was working
- confirmed that the web UI worked
Good point on the mutability. Release tags are immutable, RCs are not.
On Mon, Dec 11, 2017 at 1:39 PM, Sangjin Lee wrote:
> Thanks Andrew. For the record, the commit id would be
> c25427ceca461ee979d30edd7a4b0f50718e6533. I mention that for completeness
> because of the
Thanks Andrew. For the record, the commit id would be
c25427ceca461ee979d30edd7a4b0f50718e6533. I mention that for completeness
because of the mutability of tags.
On Mon, Dec 11, 2017 at 10:31 AM, Andrew Wang
wrote:
> Sorry, forgot to push the tag. It's up there now.
>
I couldn't find the release tag for RC1 either - is it just me or has the
release-process changed?
+Vinod
> On Dec 10, 2017, at 4:31 PM, Sangjin Lee wrote:
>
> Hi Andrew,
>
> Thanks much for your effort! Just to be clear, could you please state the
> git commit id of the
Hi Andrew,
Thanks much for your effort! Just to be clear, could you please state the
git commit id of the RC1 we're voting for?
Sangjin
On Fri, Dec 8, 2017 at 12:31 PM, Andrew Wang
wrote:
> Hi all,
>
> Let me start, as always, by thanking the efforts of all the
28 matches
Mail list logo