Re: [VOTE] Release Apache Hadoop 2.6.1 RC1

2015-09-20 Thread Junping Du
+1 (binding) with:
- Download and verify signatures.
- Build and deploy a single node cluster.
- Run some example jobs (PI, etc.) on deployed cluster.

Thanks,

Junping

From: Rohith Sharma K S 
Sent: Monday, September 21, 2015 6:53 AM
To: hdfs-...@hadoop.apache.org; yarn-...@hadoop.apache.org
Cc: common-dev@hadoop.apache.org; mapreduce-...@hadoop.apache.org
Subject: RE: [VOTE] Release Apache Hadoop 2.6.1 RC1

+1 (non-binding)

Downloaded source, built package and installed 5 node cluster.
1. Verified for RMHA/RMRestart/RMWorkpreservingRestart cluster in 
secure/non-secure mode.
2. Attached JCarder tool to cluster for identifying deadlock cycles, No cycles 
found.
3. Verified cluster for high availability.
4. Ran sample MR applications with RM HA enabled.
5. Run sanity test cases and working fine.


Thanks & Regards
Rohith Sharma K S

-Original Message-
From: sjl...@gmail.com [mailto:sjl...@gmail.com] On Behalf Of Sangjin Lee
Sent: 18 September 2015 09:50
To: yarn-...@hadoop.apache.org
Cc: common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org; 
mapreduce-...@hadoop.apache.org
Subject: Re: [VOTE] Release Apache Hadoop 2.6.1 RC1

+1 (non-binding)

Verified the signatures, set up a pseudo-distributed cluster, ran several test 
jobs, and ran an uber job. Also verified that the UI issue I saw on
RC0 is now gone. Thanks Vinod!

Sangjin

On Thu, Sep 17, 2015 at 7:24 PM, Jian He  wrote:

> +1 (binding)
>
> Build from source code.
> Deployed a local cluster.
> Validated sample jobs passed.
>
> Jian
>
> > On Sep 18, 2015, at 7:34 AM, Wangda Tan  wrote:
> >
> > Deployed a local cluster, verified configured cluster with node
> > labels,
> run
> > jobs with/without node labels.
> >
> > +1 (non-binding)
> >
> > Thanks!
> >
> > On Thu, Sep 17, 2015 at 2:40 PM, Xuan Gong 
> wrote:
> >
> >> Update my vote from +1 (non-binding) to +1 binding
> >>
> >> Thanks
> >>
> >> Xuan Gong
> >>
> >>> On Sep 17, 2015, at 2:05 PM, Xuan Gong  wrote:
> >>>
> >>> +1 (non-binding)
> >>> Download and compile the source code, run several MR jobs.
> >>>
> >>> Xuan Gong
> >>>
>  On Sep 16, 2015, at 7:10 PM, Vinod Kumar Vavilapalli <
> >> vino...@apache.org> wrote:
> 
>  Hi all,
> 
>  After a nearly month long [1] toil, with loads of help from
>  Sangjin
> Lee
> >> and
>  Akira Ajisaka, and 153 (RC0)+7(RC1) commits later, I've created a
> >> release
>  candidate RC1 for hadoop-2.6.1.
> 
>  RC1 is RC0 [0] (for which I opened and closed a vote last week) +
>  UI
> >> fixes
>  for the issue Sangjin raised (YARN-3171 and the dependencies
> YARN-3779,
>  YARN-3248), additional fix to avoid incompatibility (YARN-3740),
>  other
> >> UI
>  bugs (YARN-1884, YARN-3544) and the MiniYARNCluster issue (right
>  patch
> >> for
>  YARN-2890) that Jeff Zhang raised.
> 
>  The RC is available at:
> >> http://people.apache.org/~vinodkv/hadoop-2.6.1-RC1/
> 
>  The RC tag in git is: release-2.6.1-RC1
> 
>  The maven artifacts are available via repository.apache.org at
> 
> https://repository.apache.org/content/repositories/orgapachehadoop-102
> 1
> 
>  Some notes from our release process
>  -  - Sangjin and I moved out a bunch of items pending from 2.6.1
>  [2] - non-committed but desired patches. 2.6.1 is already big as
>  is and is
> >> late
>  by any standard, we can definitely include them in the next release.
>  - The 2.6.1 wiki page [3] captures some (but not all) of the
>  context
> of
>  the patches that we pushed in.
>  - Given the number of fixes pushed [4] in, we had to make a bunch
>  of changes to our original plan - we added a few improvements
>  that helped
> >> us
>  backport patches easier (or in many cases made backports
>  possible),
> and
> >> we
>  dropped a few that didn't make sense (HDFS-7831, HDFS-7926,
>  HDFS-7676, HDFS-7611, HDFS-7843, HDFS-8850).
>  - I ran all the unit tests which (surprisingly?) passed. (Except
>  for
> >> one,
>  which pointed out a missing fix HDFS-7552).
> 
>  As discussed before [5]
>  - This release is the first point release after 2.6.0
>  - I’d like to use this as a starting release for 2.6.2 in a few
>  weeks
> >> and
>  then follow up with more of these.
> 
>  Please try the release and vote; the vote will run for the usual
>  5
> days.
> 
>  Thanks,
>  Vinod
> 
>  [0] Hadoop 2.6.1 RC0 vote:
> http://markmail.org/thread/ubut2rn3lodc55iy
>  [1] Hadoop 2.6.1 Release process thread:
>  http://markmail.org/thread/wkbgkxkhntx5tlux
>  [2] 2.6.1 Pending tickets:
>  https://issues.apache.org/jira/issues/?filter=12331711
>  [3] 2.6.1 Wiki page: https://wiki.apache.org/hadoop/Release-2.6.1
>  -Working-Notes
>  [4] List of 2.6.1 patches pushed:
>  https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%202.6
> 

RE: [VOTE] Release Apache Hadoop 2.6.1 RC1

2015-09-20 Thread Rohith Sharma K S
+1 (non-binding)

Downloaded source, built package and installed 5 node cluster.
1. Verified for RMHA/RMRestart/RMWorkpreservingRestart cluster in 
secure/non-secure mode.
2. Attached JCarder tool to cluster for identifying deadlock cycles, No cycles 
found.
3. Verified cluster for high availability.
4. Ran sample MR applications with RM HA enabled. 
5. Run sanity test cases and working fine.


Thanks & Regards
Rohith Sharma K S

-Original Message-
From: sjl...@gmail.com [mailto:sjl...@gmail.com] On Behalf Of Sangjin Lee
Sent: 18 September 2015 09:50
To: yarn-...@hadoop.apache.org
Cc: common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org; 
mapreduce-...@hadoop.apache.org
Subject: Re: [VOTE] Release Apache Hadoop 2.6.1 RC1

+1 (non-binding)

Verified the signatures, set up a pseudo-distributed cluster, ran several test 
jobs, and ran an uber job. Also verified that the UI issue I saw on
RC0 is now gone. Thanks Vinod!

Sangjin

On Thu, Sep 17, 2015 at 7:24 PM, Jian He  wrote:

> +1 (binding)
>
> Build from source code.
> Deployed a local cluster.
> Validated sample jobs passed.
>
> Jian
>
> > On Sep 18, 2015, at 7:34 AM, Wangda Tan  wrote:
> >
> > Deployed a local cluster, verified configured cluster with node 
> > labels,
> run
> > jobs with/without node labels.
> >
> > +1 (non-binding)
> >
> > Thanks!
> >
> > On Thu, Sep 17, 2015 at 2:40 PM, Xuan Gong 
> wrote:
> >
> >> Update my vote from +1 (non-binding) to +1 binding
> >>
> >> Thanks
> >>
> >> Xuan Gong
> >>
> >>> On Sep 17, 2015, at 2:05 PM, Xuan Gong  wrote:
> >>>
> >>> +1 (non-binding)
> >>> Download and compile the source code, run several MR jobs.
> >>>
> >>> Xuan Gong
> >>>
>  On Sep 16, 2015, at 7:10 PM, Vinod Kumar Vavilapalli <
> >> vino...@apache.org> wrote:
> 
>  Hi all,
> 
>  After a nearly month long [1] toil, with loads of help from 
>  Sangjin
> Lee
> >> and
>  Akira Ajisaka, and 153 (RC0)+7(RC1) commits later, I've created a
> >> release
>  candidate RC1 for hadoop-2.6.1.
> 
>  RC1 is RC0 [0] (for which I opened and closed a vote last week) + 
>  UI
> >> fixes
>  for the issue Sangjin raised (YARN-3171 and the dependencies
> YARN-3779,
>  YARN-3248), additional fix to avoid incompatibility (YARN-3740), 
>  other
> >> UI
>  bugs (YARN-1884, YARN-3544) and the MiniYARNCluster issue (right 
>  patch
> >> for
>  YARN-2890) that Jeff Zhang raised.
> 
>  The RC is available at:
> >> http://people.apache.org/~vinodkv/hadoop-2.6.1-RC1/
> 
>  The RC tag in git is: release-2.6.1-RC1
> 
>  The maven artifacts are available via repository.apache.org at
> 
> https://repository.apache.org/content/repositories/orgapachehadoop-102
> 1
> 
>  Some notes from our release process
>  -  - Sangjin and I moved out a bunch of items pending from 2.6.1 
>  [2] - non-committed but desired patches. 2.6.1 is already big as 
>  is and is
> >> late
>  by any standard, we can definitely include them in the next release.
>  - The 2.6.1 wiki page [3] captures some (but not all) of the 
>  context
> of
>  the patches that we pushed in.
>  - Given the number of fixes pushed [4] in, we had to make a bunch 
>  of changes to our original plan - we added a few improvements 
>  that helped
> >> us
>  backport patches easier (or in many cases made backports 
>  possible),
> and
> >> we
>  dropped a few that didn't make sense (HDFS-7831, HDFS-7926, 
>  HDFS-7676, HDFS-7611, HDFS-7843, HDFS-8850).
>  - I ran all the unit tests which (surprisingly?) passed. (Except 
>  for
> >> one,
>  which pointed out a missing fix HDFS-7552).
> 
>  As discussed before [5]
>  - This release is the first point release after 2.6.0
>  - I’d like to use this as a starting release for 2.6.2 in a few 
>  weeks
> >> and
>  then follow up with more of these.
> 
>  Please try the release and vote; the vote will run for the usual 
>  5
> days.
> 
>  Thanks,
>  Vinod
> 
>  [0] Hadoop 2.6.1 RC0 vote:
> http://markmail.org/thread/ubut2rn3lodc55iy
>  [1] Hadoop 2.6.1 Release process thread:
>  http://markmail.org/thread/wkbgkxkhntx5tlux
>  [2] 2.6.1 Pending tickets:
>  https://issues.apache.org/jira/issues/?filter=12331711
>  [3] 2.6.1 Wiki page: https://wiki.apache.org/hadoop/Release-2.6.1
>  -Working-Notes
>  [4] List of 2.6.1 patches pushed:
>  https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%202.6
>  .1
>  %20and%20labels%20%3D%20%222.6.1-candidate%22
>  [5] Planning Hadoop 2.6.1 release:
>  http://markmail.org/thread/sbykjn5xgnksh6wg
> 
>  PS:
>  - Note that branch-2.6 which will be the base for 2.6.2 doesn't 
>  have
> >> these
>  fixes yet. Once 2.6.1 goes through, I plan to rebase branch-2.6 
>  based
> >> off
>  2.6.1.
>  - The additional patches in RC1 that got into 2.6.1 all 

Re: Local repo sharing for maven builds

2015-09-20 Thread Josh Elser

Andrew Wang wrote:

Theoretically, we should be able to run unittests without a full `mvn
install` right? The "test" phase comes before "package" or "install", so I
figured it only needed class files. Maybe the multi-module-ness screws this
up.


Unless something weird is configured in the poms (which is often a smell 
on its own), the reactor (I think is the right Maven bit) is smart 
enough to pull the right code for multi-module builds.


AFAIK, you should be able to run all unit tests with a patch (hitting 
multiple modules or not) without installing all of the artifacts (e.g. 
using the package lifecycle phase).


If this isn't the case, I'd call that a build bug.