[VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Sangjin Lee <sj...@apache.org>]

Hi folks,

I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
release (the next maintenance release in the 2.6.x release line). RC1
contains fixes to CHANGES.txt, and is otherwise identical to RC0.

Below are the details of this release candidate:

The RC is available for validation at:
http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.

The RC tag in git is release-2.6.5-RC1 and its git commit is
e8c9fe0b4c252caf2ebf1464220599650f119997.

The maven artifacts are staged via repository.apache.org at:
https://repository.apache.org/content/repositories/orgapachehadoop-1050/.

You can find my public key at
http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.

Please try the release and vote. The vote will run for the usual 5 days. I
would greatly appreciate your timely vote. Thanks!

Regards,
Sangjin

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Chris Trezzo <ct...@gmail.com>]

+1 (non-binding)

Thanks for cutting another release candidate Sangjin!

1. Diff'ed the CHANGES-*.txt files against the branch-2.6.5 git log and
verified the set of listed issues matches.
2. Verified md5 checksums and signature on src and binary tar.gz.
3. Built from source.
4. Started up a pseudo distributed cluster.
5. Successfully ran a PI job.
6. Ran the balancer.
7. Inspected UI for RM, NN, JobHistory.

On Sun, Oct 2, 2016 at 5:12 PM, Sangjin Lee <sj...@apache.org> wrote:

> Hi folks,
>
> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> release (the next maintenance release in the 2.6.x release line). RC1
> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
>
> Below are the details of this release candidate:
>
> The RC is available for validation at:
> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
>
> The RC tag in git is release-2.6.5-RC1 and its git commit is
> e8c9fe0b4c252caf2ebf1464220599650f119997.
>
> The maven artifacts are staged via repository.apache.org at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1050/.
>
> You can find my public key at
> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
>
> Please try the release and vote. The vote will run for the usual 5 days. I
> would greatly appreciate your timely vote. Thanks!
>
> Regards,
> Sangjin
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[John Zhuge <jz...@cloudera.com>]

+1 (non-binding)

- Verified checksums and signatures of the tarballs
- Built source with Java 1.7.0_111 on Centos 6.6 with native
- Verified licenses and notices using verify-license-notice.sh
- Deployed a pseudo cluster

- Ran basic dfs, distcp, ACL commands
- Ran MapReduce wordcount example
- Ran balancer


Thanks,
John

John Zhuge
Software Engineer, Cloudera

On Sun, Oct 2, 2016 at 5:12 PM, Sangjin Lee <sj...@apache.org> wrote:

> Hi folks,
>
> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> release (the next maintenance release in the 2.6.x release line). RC1
> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
>
> Below are the details of this release candidate:
>
> The RC is available for validation at:
> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
>
> The RC tag in git is release-2.6.5-RC1 and its git commit is
> e8c9fe0b4c252caf2ebf1464220599650f119997.
>
> The maven artifacts are staged via repository.apache.org at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1050/.
>
> You can find my public key at
> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
>
> Please try the release and vote. The vote will run for the usual 5 days. I
> would greatly appreciate your timely vote. Thanks!
>
> Regards,
> Sangjin
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Brahma Reddy Battula <br...@apache.org>]

Thanks Sangjin!


+1 ( non- binding)


--Downloaded the source and complied

--Installed HA cluster

--Verified basic fsshell commands

--Ran pi,terasort Slive jobs, all works fine.



--Brahma Reddy Battula

On Mon, Oct 3, 2016 at 5:42 AM, Sangjin Lee <sj...@apache.org> wrote:

> Hi folks,
>
> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> release (the next maintenance release in the 2.6.x release line). RC1
> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
>
> Below are the details of this release candidate:
>
> The RC is available for validation at:
> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
>
> The RC tag in git is release-2.6.5-RC1 and its git commit is
> e8c9fe0b4c252caf2ebf1464220599650f119997.
>
> The maven artifacts are staged via repository.apache.org at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1050/.
>
> You can find my public key at
> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
>
> Please try the release and vote. The vote will run for the usual 5 days. I
> would greatly appreciate your timely vote. Thanks!
>
> Regards,
> Sangjin
>



-- 



--Brahma Reddy Battula

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Sangjin Lee <sj...@apache.org>]

I think it's a good idea. We can still have the underlying data (in
*-version.properties) but we can consider removing the date and the build
person from the web UI. I'll file a JIRA to consider the idea.

I would greatly appreciate it if you folks can take a little time to take
the RC1 for a spin and vote on it. Tomorrow will be the conclusion of the
vote, and I haven't received many votes yet. Thanks!

Sangjin

On Thu, Oct 6, 2016 at 3:13 PM, Andrew Wang <an...@cloudera.com>
wrote:

> I don't think it's a blocker, though I wonder what the point of that date
> and attribution are on the WebUI.
>
> Maybe file a follow-on JIRA to remove it for the future?
>
> On Thu, Oct 6, 2016 at 3:09 PM, Sangjin Lee <sj...@apache.org> wrote:
>
> > I looked into building it on jenkins earlier, but it appears that this
> > jenkins job is busted (at least for 2.6.x):
> > https://builds.apache.org/job/HADOOP2_Release_Artifacts_Builder/
> >
> > I don't have access to the job configuration, so I'm unable to fix it
> atm.
> >
> > That said, I do think Allen has a point. It strikes me that the release
> > manager building it under his/her own control shouldn't be a problem, if
> > not better. Also, the how-to-release wiki currently seems to suggest
> > building it locally is fine (http://wiki.apache.org/hadoop/HowToRelease
> ).
> >
> > IMO I don't think this is a blocker. Thoughts?
> >
> > Thanks,
> > Sangjin
> >
> > On Thu, Oct 6, 2016 at 1:39 PM, Akira Ajisaka <
> ajisakaa@oss.nttdata.co.jp>
> > wrote:
> >
> > > > It wasn't 'renamed' to jenkins, prior releases were actually built by
> > > and on the Jenkins infrastructure. Which was a very very bad idea:
> it's
> > > insecure and pretty much against ASF policy.
> > >
> > > Sorry for the confusion. I should not have used the word 'rename'.
> > > What I meant is that "would you change the name to 'jenkins' by using
> the
> > > Jenkins infra?"
> > >
> > > Regards,
> > > Akira
> > >
> > >
> > > On 10/7/16 03:04, Allen Wittenauer wrote:
> > >
> > >>
> > >> On Oct 5, 2016, at 10:35 PM, Akira Ajisaka <
> ajisakaa@oss.nttdata.co.jp>
> > >>> wrote:
> > >>> Can we rename it?
> > >>>
> > >>> AFAIK, hadoop releases were built by hortonmu in 2014 and was renamed
> > to
> > >>> jenkins.
> > >>>
> > >>
> > >>         That's not how that works.
> > >>
> > >>         It's literally storing the id of the person who built the
> > >> classes.  It wasn't 'renamed' to jenkins, prior releases were actually
> > >> built by and on the Jenkins infrastructure. Which was a very very bad
> > >> idea:  it's insecure and pretty much against ASF policy.
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > >> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> > >>
> > >>
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: common-dev-help@hadoop.apache.org
> > >
> > >
> >
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Sangjin Lee <sj...@apache.org>]

I think it's a good idea. We can still have the underlying data (in
*-version.properties) but we can consider removing the date and the build
person from the web UI. I'll file a JIRA to consider the idea.

I would greatly appreciate it if you folks can take a little time to take
the RC1 for a spin and vote on it. Tomorrow will be the conclusion of the
vote, and I haven't received many votes yet. Thanks!

Sangjin

On Thu, Oct 6, 2016 at 3:13 PM, Andrew Wang <an...@cloudera.com>
wrote:

> I don't think it's a blocker, though I wonder what the point of that date
> and attribution are on the WebUI.
>
> Maybe file a follow-on JIRA to remove it for the future?
>
> On Thu, Oct 6, 2016 at 3:09 PM, Sangjin Lee <sj...@apache.org> wrote:
>
> > I looked into building it on jenkins earlier, but it appears that this
> > jenkins job is busted (at least for 2.6.x):
> > https://builds.apache.org/job/HADOOP2_Release_Artifacts_Builder/
> >
> > I don't have access to the job configuration, so I'm unable to fix it
> atm.
> >
> > That said, I do think Allen has a point. It strikes me that the release
> > manager building it under his/her own control shouldn't be a problem, if
> > not better. Also, the how-to-release wiki currently seems to suggest
> > building it locally is fine (http://wiki.apache.org/hadoop/HowToRelease
> ).
> >
> > IMO I don't think this is a blocker. Thoughts?
> >
> > Thanks,
> > Sangjin
> >
> > On Thu, Oct 6, 2016 at 1:39 PM, Akira Ajisaka <
> ajisakaa@oss.nttdata.co.jp>
> > wrote:
> >
> > > > It wasn't 'renamed' to jenkins, prior releases were actually built by
> > > and on the Jenkins infrastructure. Which was a very very bad idea:
> it's
> > > insecure and pretty much against ASF policy.
> > >
> > > Sorry for the confusion. I should not have used the word 'rename'.
> > > What I meant is that "would you change the name to 'jenkins' by using
> the
> > > Jenkins infra?"
> > >
> > > Regards,
> > > Akira
> > >
> > >
> > > On 10/7/16 03:04, Allen Wittenauer wrote:
> > >
> > >>
> > >> On Oct 5, 2016, at 10:35 PM, Akira Ajisaka <
> ajisakaa@oss.nttdata.co.jp>
> > >>> wrote:
> > >>> Can we rename it?
> > >>>
> > >>> AFAIK, hadoop releases were built by hortonmu in 2014 and was renamed
> > to
> > >>> jenkins.
> > >>>
> > >>
> > >>         That's not how that works.
> > >>
> > >>         It's literally storing the id of the person who built the
> > >> classes.  It wasn't 'renamed' to jenkins, prior releases were actually
> > >> built by and on the Jenkins infrastructure. Which was a very very bad
> > >> idea:  it's insecure and pretty much against ASF policy.
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > >> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> > >>
> > >>
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: common-dev-help@hadoop.apache.org
> > >
> > >
> >
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Sangjin Lee <sj...@apache.org>]

I think it's a good idea. We can still have the underlying data (in
*-version.properties) but we can consider removing the date and the build
person from the web UI. I'll file a JIRA to consider the idea.

I would greatly appreciate it if you folks can take a little time to take
the RC1 for a spin and vote on it. Tomorrow will be the conclusion of the
vote, and I haven't received many votes yet. Thanks!

Sangjin

On Thu, Oct 6, 2016 at 3:13 PM, Andrew Wang <an...@cloudera.com>
wrote:

> I don't think it's a blocker, though I wonder what the point of that date
> and attribution are on the WebUI.
>
> Maybe file a follow-on JIRA to remove it for the future?
>
> On Thu, Oct 6, 2016 at 3:09 PM, Sangjin Lee <sj...@apache.org> wrote:
>
> > I looked into building it on jenkins earlier, but it appears that this
> > jenkins job is busted (at least for 2.6.x):
> > https://builds.apache.org/job/HADOOP2_Release_Artifacts_Builder/
> >
> > I don't have access to the job configuration, so I'm unable to fix it
> atm.
> >
> > That said, I do think Allen has a point. It strikes me that the release
> > manager building it under his/her own control shouldn't be a problem, if
> > not better. Also, the how-to-release wiki currently seems to suggest
> > building it locally is fine (http://wiki.apache.org/hadoop/HowToRelease
> ).
> >
> > IMO I don't think this is a blocker. Thoughts?
> >
> > Thanks,
> > Sangjin
> >
> > On Thu, Oct 6, 2016 at 1:39 PM, Akira Ajisaka <
> ajisakaa@oss.nttdata.co.jp>
> > wrote:
> >
> > > > It wasn't 'renamed' to jenkins, prior releases were actually built by
> > > and on the Jenkins infrastructure. Which was a very very bad idea:
> it's
> > > insecure and pretty much against ASF policy.
> > >
> > > Sorry for the confusion. I should not have used the word 'rename'.
> > > What I meant is that "would you change the name to 'jenkins' by using
> the
> > > Jenkins infra?"
> > >
> > > Regards,
> > > Akira
> > >
> > >
> > > On 10/7/16 03:04, Allen Wittenauer wrote:
> > >
> > >>
> > >> On Oct 5, 2016, at 10:35 PM, Akira Ajisaka <
> ajisakaa@oss.nttdata.co.jp>
> > >>> wrote:
> > >>> Can we rename it?
> > >>>
> > >>> AFAIK, hadoop releases were built by hortonmu in 2014 and was renamed
> > to
> > >>> jenkins.
> > >>>
> > >>
> > >>         That's not how that works.
> > >>
> > >>         It's literally storing the id of the person who built the
> > >> classes.  It wasn't 'renamed' to jenkins, prior releases were actually
> > >> built by and on the Jenkins infrastructure. Which was a very very bad
> > >> idea:  it's insecure and pretty much against ASF policy.
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > >> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> > >>
> > >>
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: common-dev-help@hadoop.apache.org
> > >
> > >
> >
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Sangjin Lee <sj...@apache.org>]

I think it's a good idea. We can still have the underlying data (in
*-version.properties) but we can consider removing the date and the build
person from the web UI. I'll file a JIRA to consider the idea.

I would greatly appreciate it if you folks can take a little time to take
the RC1 for a spin and vote on it. Tomorrow will be the conclusion of the
vote, and I haven't received many votes yet. Thanks!

Sangjin

On Thu, Oct 6, 2016 at 3:13 PM, Andrew Wang <an...@cloudera.com>
wrote:

> I don't think it's a blocker, though I wonder what the point of that date
> and attribution are on the WebUI.
>
> Maybe file a follow-on JIRA to remove it for the future?
>
> On Thu, Oct 6, 2016 at 3:09 PM, Sangjin Lee <sj...@apache.org> wrote:
>
> > I looked into building it on jenkins earlier, but it appears that this
> > jenkins job is busted (at least for 2.6.x):
> > https://builds.apache.org/job/HADOOP2_Release_Artifacts_Builder/
> >
> > I don't have access to the job configuration, so I'm unable to fix it
> atm.
> >
> > That said, I do think Allen has a point. It strikes me that the release
> > manager building it under his/her own control shouldn't be a problem, if
> > not better. Also, the how-to-release wiki currently seems to suggest
> > building it locally is fine (http://wiki.apache.org/hadoop/HowToRelease
> ).
> >
> > IMO I don't think this is a blocker. Thoughts?
> >
> > Thanks,
> > Sangjin
> >
> > On Thu, Oct 6, 2016 at 1:39 PM, Akira Ajisaka <
> ajisakaa@oss.nttdata.co.jp>
> > wrote:
> >
> > > > It wasn't 'renamed' to jenkins, prior releases were actually built by
> > > and on the Jenkins infrastructure. Which was a very very bad idea:
> it's
> > > insecure and pretty much against ASF policy.
> > >
> > > Sorry for the confusion. I should not have used the word 'rename'.
> > > What I meant is that "would you change the name to 'jenkins' by using
> the
> > > Jenkins infra?"
> > >
> > > Regards,
> > > Akira
> > >
> > >
> > > On 10/7/16 03:04, Allen Wittenauer wrote:
> > >
> > >>
> > >> On Oct 5, 2016, at 10:35 PM, Akira Ajisaka <
> ajisakaa@oss.nttdata.co.jp>
> > >>> wrote:
> > >>> Can we rename it?
> > >>>
> > >>> AFAIK, hadoop releases were built by hortonmu in 2014 and was renamed
> > to
> > >>> jenkins.
> > >>>
> > >>
> > >>         That's not how that works.
> > >>
> > >>         It's literally storing the id of the person who built the
> > >> classes.  It wasn't 'renamed' to jenkins, prior releases were actually
> > >> built by and on the Jenkins infrastructure. Which was a very very bad
> > >> idea:  it's insecure and pretty much against ASF policy.
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > >> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> > >>
> > >>
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: common-dev-help@hadoop.apache.org
> > >
> > >
> >
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Andrew Wang <an...@cloudera.com>]

I don't think it's a blocker, though I wonder what the point of that date
and attribution are on the WebUI.

Maybe file a follow-on JIRA to remove it for the future?

On Thu, Oct 6, 2016 at 3:09 PM, Sangjin Lee <sj...@apache.org> wrote:

> I looked into building it on jenkins earlier, but it appears that this
> jenkins job is busted (at least for 2.6.x):
> https://builds.apache.org/job/HADOOP2_Release_Artifacts_Builder/
>
> I don't have access to the job configuration, so I'm unable to fix it atm.
>
> That said, I do think Allen has a point. It strikes me that the release
> manager building it under his/her own control shouldn't be a problem, if
> not better. Also, the how-to-release wiki currently seems to suggest
> building it locally is fine (http://wiki.apache.org/hadoop/HowToRelease).
>
> IMO I don't think this is a blocker. Thoughts?
>
> Thanks,
> Sangjin
>
> On Thu, Oct 6, 2016 at 1:39 PM, Akira Ajisaka <aj...@oss.nttdata.co.jp>
> wrote:
>
> > > It wasn't 'renamed' to jenkins, prior releases were actually built by
> > and on the Jenkins infrastructure. Which was a very very bad idea:  it's
> > insecure and pretty much against ASF policy.
> >
> > Sorry for the confusion. I should not have used the word 'rename'.
> > What I meant is that "would you change the name to 'jenkins' by using the
> > Jenkins infra?"
> >
> > Regards,
> > Akira
> >
> >
> > On 10/7/16 03:04, Allen Wittenauer wrote:
> >
> >>
> >> On Oct 5, 2016, at 10:35 PM, Akira Ajisaka <aj...@oss.nttdata.co.jp>
> >>> wrote:
> >>> Can we rename it?
> >>>
> >>> AFAIK, hadoop releases were built by hortonmu in 2014 and was renamed
> to
> >>> jenkins.
> >>>
> >>
> >>         That's not how that works.
> >>
> >>         It's literally storing the id of the person who built the
> >> classes.  It wasn't 'renamed' to jenkins, prior releases were actually
> >> built by and on the Jenkins infrastructure. Which was a very very bad
> >> idea:  it's insecure and pretty much against ASF policy.
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >
> >
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Andrew Wang <an...@cloudera.com>]

I don't think it's a blocker, though I wonder what the point of that date
and attribution are on the WebUI.

Maybe file a follow-on JIRA to remove it for the future?

On Thu, Oct 6, 2016 at 3:09 PM, Sangjin Lee <sj...@apache.org> wrote:

> I looked into building it on jenkins earlier, but it appears that this
> jenkins job is busted (at least for 2.6.x):
> https://builds.apache.org/job/HADOOP2_Release_Artifacts_Builder/
>
> I don't have access to the job configuration, so I'm unable to fix it atm.
>
> That said, I do think Allen has a point. It strikes me that the release
> manager building it under his/her own control shouldn't be a problem, if
> not better. Also, the how-to-release wiki currently seems to suggest
> building it locally is fine (http://wiki.apache.org/hadoop/HowToRelease).
>
> IMO I don't think this is a blocker. Thoughts?
>
> Thanks,
> Sangjin
>
> On Thu, Oct 6, 2016 at 1:39 PM, Akira Ajisaka <aj...@oss.nttdata.co.jp>
> wrote:
>
> > > It wasn't 'renamed' to jenkins, prior releases were actually built by
> > and on the Jenkins infrastructure. Which was a very very bad idea:  it's
> > insecure and pretty much against ASF policy.
> >
> > Sorry for the confusion. I should not have used the word 'rename'.
> > What I meant is that "would you change the name to 'jenkins' by using the
> > Jenkins infra?"
> >
> > Regards,
> > Akira
> >
> >
> > On 10/7/16 03:04, Allen Wittenauer wrote:
> >
> >>
> >> On Oct 5, 2016, at 10:35 PM, Akira Ajisaka <aj...@oss.nttdata.co.jp>
> >>> wrote:
> >>> Can we rename it?
> >>>
> >>> AFAIK, hadoop releases were built by hortonmu in 2014 and was renamed
> to
> >>> jenkins.
> >>>
> >>
> >>         That's not how that works.
> >>
> >>         It's literally storing the id of the person who built the
> >> classes.  It wasn't 'renamed' to jenkins, prior releases were actually
> >> built by and on the Jenkins infrastructure. Which was a very very bad
> >> idea:  it's insecure and pretty much against ASF policy.
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >
> >
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Andrew Wang <an...@cloudera.com>]

I don't think it's a blocker, though I wonder what the point of that date
and attribution are on the WebUI.

Maybe file a follow-on JIRA to remove it for the future?

On Thu, Oct 6, 2016 at 3:09 PM, Sangjin Lee <sj...@apache.org> wrote:

> I looked into building it on jenkins earlier, but it appears that this
> jenkins job is busted (at least for 2.6.x):
> https://builds.apache.org/job/HADOOP2_Release_Artifacts_Builder/
>
> I don't have access to the job configuration, so I'm unable to fix it atm.
>
> That said, I do think Allen has a point. It strikes me that the release
> manager building it under his/her own control shouldn't be a problem, if
> not better. Also, the how-to-release wiki currently seems to suggest
> building it locally is fine (http://wiki.apache.org/hadoop/HowToRelease).
>
> IMO I don't think this is a blocker. Thoughts?
>
> Thanks,
> Sangjin
>
> On Thu, Oct 6, 2016 at 1:39 PM, Akira Ajisaka <aj...@oss.nttdata.co.jp>
> wrote:
>
> > > It wasn't 'renamed' to jenkins, prior releases were actually built by
> > and on the Jenkins infrastructure. Which was a very very bad idea:  it's
> > insecure and pretty much against ASF policy.
> >
> > Sorry for the confusion. I should not have used the word 'rename'.
> > What I meant is that "would you change the name to 'jenkins' by using the
> > Jenkins infra?"
> >
> > Regards,
> > Akira
> >
> >
> > On 10/7/16 03:04, Allen Wittenauer wrote:
> >
> >>
> >> On Oct 5, 2016, at 10:35 PM, Akira Ajisaka <aj...@oss.nttdata.co.jp>
> >>> wrote:
> >>> Can we rename it?
> >>>
> >>> AFAIK, hadoop releases were built by hortonmu in 2014 and was renamed
> to
> >>> jenkins.
> >>>
> >>
> >>         That's not how that works.
> >>
> >>         It's literally storing the id of the person who built the
> >> classes.  It wasn't 'renamed' to jenkins, prior releases were actually
> >> built by and on the Jenkins infrastructure. Which was a very very bad
> >> idea:  it's insecure and pretty much against ASF policy.
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >
> >
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Andrew Wang <an...@cloudera.com>]

I don't think it's a blocker, though I wonder what the point of that date
and attribution are on the WebUI.

Maybe file a follow-on JIRA to remove it for the future?

On Thu, Oct 6, 2016 at 3:09 PM, Sangjin Lee <sj...@apache.org> wrote:

> I looked into building it on jenkins earlier, but it appears that this
> jenkins job is busted (at least for 2.6.x):
> https://builds.apache.org/job/HADOOP2_Release_Artifacts_Builder/
>
> I don't have access to the job configuration, so I'm unable to fix it atm.
>
> That said, I do think Allen has a point. It strikes me that the release
> manager building it under his/her own control shouldn't be a problem, if
> not better. Also, the how-to-release wiki currently seems to suggest
> building it locally is fine (http://wiki.apache.org/hadoop/HowToRelease).
>
> IMO I don't think this is a blocker. Thoughts?
>
> Thanks,
> Sangjin
>
> On Thu, Oct 6, 2016 at 1:39 PM, Akira Ajisaka <aj...@oss.nttdata.co.jp>
> wrote:
>
> > > It wasn't 'renamed' to jenkins, prior releases were actually built by
> > and on the Jenkins infrastructure. Which was a very very bad idea:  it's
> > insecure and pretty much against ASF policy.
> >
> > Sorry for the confusion. I should not have used the word 'rename'.
> > What I meant is that "would you change the name to 'jenkins' by using the
> > Jenkins infra?"
> >
> > Regards,
> > Akira
> >
> >
> > On 10/7/16 03:04, Allen Wittenauer wrote:
> >
> >>
> >> On Oct 5, 2016, at 10:35 PM, Akira Ajisaka <aj...@oss.nttdata.co.jp>
> >>> wrote:
> >>> Can we rename it?
> >>>
> >>> AFAIK, hadoop releases were built by hortonmu in 2014 and was renamed
> to
> >>> jenkins.
> >>>
> >>
> >>         That's not how that works.
> >>
> >>         It's literally storing the id of the person who built the
> >> classes.  It wasn't 'renamed' to jenkins, prior releases were actually
> >> built by and on the Jenkins infrastructure. Which was a very very bad
> >> idea:  it's insecure and pretty much against ASF policy.
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >
> >
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Sangjin Lee <sj...@apache.org>]

I looked into building it on jenkins earlier, but it appears that this
jenkins job is busted (at least for 2.6.x):
https://builds.apache.org/job/HADOOP2_Release_Artifacts_Builder/

I don't have access to the job configuration, so I'm unable to fix it atm.

That said, I do think Allen has a point. It strikes me that the release
manager building it under his/her own control shouldn't be a problem, if
not better. Also, the how-to-release wiki currently seems to suggest
building it locally is fine (http://wiki.apache.org/hadoop/HowToRelease).

IMO I don't think this is a blocker. Thoughts?

Thanks,
Sangjin

On Thu, Oct 6, 2016 at 1:39 PM, Akira Ajisaka <aj...@oss.nttdata.co.jp>
wrote:

> > It wasn't 'renamed' to jenkins, prior releases were actually built by
> and on the Jenkins infrastructure. Which was a very very bad idea:  it's
> insecure and pretty much against ASF policy.
>
> Sorry for the confusion. I should not have used the word 'rename'.
> What I meant is that "would you change the name to 'jenkins' by using the
> Jenkins infra?"
>
> Regards,
> Akira
>
>
> On 10/7/16 03:04, Allen Wittenauer wrote:
>
>>
>> On Oct 5, 2016, at 10:35 PM, Akira Ajisaka <aj...@oss.nttdata.co.jp>
>>> wrote:
>>> Can we rename it?
>>>
>>> AFAIK, hadoop releases were built by hortonmu in 2014 and was renamed to
>>> jenkins.
>>>
>>
>>         That's not how that works.
>>
>>         It's literally storing the id of the person who built the
>> classes.  It wasn't 'renamed' to jenkins, prior releases were actually
>> built by and on the Jenkins infrastructure. Which was a very very bad
>> idea:  it's insecure and pretty much against ASF policy.
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Akira Ajisaka <aj...@oss.nttdata.co.jp>]

I'm sorry I was wrong. Thanks Allen for the detailed information.

-Akira

On 10/7/16 15:04, Allen Wittenauer wrote:
>
>> On Oct 6, 2016, at 1:39 PM, Akira Ajisaka <aj...@oss.nttdata.co.jp> wrote:
>>
>>> It wasn't 'renamed' to jenkins, prior releases were actually built by and on the Jenkins infrastructure. Which was a very very bad idea:  it's insecure and pretty much against ASF policy.
>>
>> Sorry for the confusion. I should not have used the word 'rename'.
>> What I meant is that "would you change the name to 'jenkins' by using the Jenkins infra?"
>
>
> To re-iterate, building on the jenkins servers is a violation of ASF release policy and the PMC pretty much has a duty to vote -1 on any such release.
>
> http://www.apache.org/dev/release.html#owned-controlled-hardware
>
> --snip--
>
> Must releases be built on hardware owned and controlled by the committer?
>
> ....
>
> Practically speaking, when a release consists of anything beyond an archive (e.g., tarball or zip file) of a source control tag, the only practical way to validate that archive is to build it locally; manually inspecting generated files (especially binary files) is not feasible. So, basically, "Yes".
>
> --snip--
>
> The ASF build servers are multi-user and run many many many untested code bases.  It would be extremely easy to inject class files into any running compile (Docker-ized or otherwise).   This means that any build that comes from those servers should be considered untrusted, especially from a release perspective.
>
> For 3.x releases, I rewrote create-release and added the --asfrelease option to specifically provide a way for us to get consistent release candidates regardless of who builds it.  It should also speed up the release process since it also does a lot of the previously manually steps, such as signing.
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Akira Ajisaka <aj...@oss.nttdata.co.jp>]

I'm sorry I was wrong. Thanks Allen for the detailed information.

-Akira

On 10/7/16 15:04, Allen Wittenauer wrote:
>
>> On Oct 6, 2016, at 1:39 PM, Akira Ajisaka <aj...@oss.nttdata.co.jp> wrote:
>>
>>> It wasn't 'renamed' to jenkins, prior releases were actually built by and on the Jenkins infrastructure. Which was a very very bad idea:  it's insecure and pretty much against ASF policy.
>>
>> Sorry for the confusion. I should not have used the word 'rename'.
>> What I meant is that "would you change the name to 'jenkins' by using the Jenkins infra?"
>
>
> To re-iterate, building on the jenkins servers is a violation of ASF release policy and the PMC pretty much has a duty to vote -1 on any such release.
>
> http://www.apache.org/dev/release.html#owned-controlled-hardware
>
> --snip--
>
> Must releases be built on hardware owned and controlled by the committer?
>
> ....
>
> Practically speaking, when a release consists of anything beyond an archive (e.g., tarball or zip file) of a source control tag, the only practical way to validate that archive is to build it locally; manually inspecting generated files (especially binary files) is not feasible. So, basically, "Yes".
>
> --snip--
>
> The ASF build servers are multi-user and run many many many untested code bases.  It would be extremely easy to inject class files into any running compile (Docker-ized or otherwise).   This means that any build that comes from those servers should be considered untrusted, especially from a release perspective.
>
> For 3.x releases, I rewrote create-release and added the --asfrelease option to specifically provide a way for us to get consistent release candidates regardless of who builds it.  It should also speed up the release process since it also does a lot of the previously manually steps, such as signing.
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Akira Ajisaka <aj...@oss.nttdata.co.jp>]

I'm sorry I was wrong. Thanks Allen for the detailed information.

-Akira

On 10/7/16 15:04, Allen Wittenauer wrote:
>
>> On Oct 6, 2016, at 1:39 PM, Akira Ajisaka <aj...@oss.nttdata.co.jp> wrote:
>>
>>> It wasn't 'renamed' to jenkins, prior releases were actually built by and on the Jenkins infrastructure. Which was a very very bad idea:  it's insecure and pretty much against ASF policy.
>>
>> Sorry for the confusion. I should not have used the word 'rename'.
>> What I meant is that "would you change the name to 'jenkins' by using the Jenkins infra?"
>
>
> To re-iterate, building on the jenkins servers is a violation of ASF release policy and the PMC pretty much has a duty to vote -1 on any such release.
>
> http://www.apache.org/dev/release.html#owned-controlled-hardware
>
> --snip--
>
> Must releases be built on hardware owned and controlled by the committer?
>
> ....
>
> Practically speaking, when a release consists of anything beyond an archive (e.g., tarball or zip file) of a source control tag, the only practical way to validate that archive is to build it locally; manually inspecting generated files (especially binary files) is not feasible. So, basically, "Yes".
>
> --snip--
>
> The ASF build servers are multi-user and run many many many untested code bases.  It would be extremely easy to inject class files into any running compile (Docker-ized or otherwise).   This means that any build that comes from those servers should be considered untrusted, especially from a release perspective.
>
> For 3.x releases, I rewrote create-release and added the --asfrelease option to specifically provide a way for us to get consistent release candidates regardless of who builds it.  It should also speed up the release process since it also does a lot of the previously manually steps, such as signing.
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Akira Ajisaka <aj...@oss.nttdata.co.jp>]

I'm sorry I was wrong. Thanks Allen for the detailed information.

-Akira

On 10/7/16 15:04, Allen Wittenauer wrote:
>
>> On Oct 6, 2016, at 1:39 PM, Akira Ajisaka <aj...@oss.nttdata.co.jp> wrote:
>>
>>> It wasn't 'renamed' to jenkins, prior releases were actually built by and on the Jenkins infrastructure. Which was a very very bad idea:  it's insecure and pretty much against ASF policy.
>>
>> Sorry for the confusion. I should not have used the word 'rename'.
>> What I meant is that "would you change the name to 'jenkins' by using the Jenkins infra?"
>
>
> To re-iterate, building on the jenkins servers is a violation of ASF release policy and the PMC pretty much has a duty to vote -1 on any such release.
>
> http://www.apache.org/dev/release.html#owned-controlled-hardware
>
> --snip--
>
> Must releases be built on hardware owned and controlled by the committer?
>
> ....
>
> Practically speaking, when a release consists of anything beyond an archive (e.g., tarball or zip file) of a source control tag, the only practical way to validate that archive is to build it locally; manually inspecting generated files (especially binary files) is not feasible. So, basically, "Yes".
>
> --snip--
>
> The ASF build servers are multi-user and run many many many untested code bases.  It would be extremely easy to inject class files into any running compile (Docker-ized or otherwise).   This means that any build that comes from those servers should be considered untrusted, especially from a release perspective.
>
> For 3.x releases, I rewrote create-release and added the --asfrelease option to specifically provide a way for us to get consistent release candidates regardless of who builds it.  It should also speed up the release process since it also does a lot of the previously manually steps, such as signing.
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Allen Wittenauer <aw...@effectivemachines.com>]

> On Oct 6, 2016, at 1:39 PM, Akira Ajisaka <aj...@oss.nttdata.co.jp> wrote:
> 
> > It wasn't 'renamed' to jenkins, prior releases were actually built by and on the Jenkins infrastructure. Which was a very very bad idea:  it's insecure and pretty much against ASF policy.
> 
> Sorry for the confusion. I should not have used the word 'rename'.
> What I meant is that "would you change the name to 'jenkins' by using the Jenkins infra?"


To re-iterate, building on the jenkins servers is a violation of ASF release policy and the PMC pretty much has a duty to vote -1 on any such release.  

http://www.apache.org/dev/release.html#owned-controlled-hardware

--snip--

Must releases be built on hardware owned and controlled by the committer?

....

Practically speaking, when a release consists of anything beyond an archive (e.g., tarball or zip file) of a source control tag, the only practical way to validate that archive is to build it locally; manually inspecting generated files (especially binary files) is not feasible. So, basically, "Yes".

--snip--

The ASF build servers are multi-user and run many many many untested code bases.  It would be extremely easy to inject class files into any running compile (Docker-ized or otherwise).   This means that any build that comes from those servers should be considered untrusted, especially from a release perspective.

For 3.x releases, I rewrote create-release and added the --asfrelease option to specifically provide a way for us to get consistent release candidates regardless of who builds it.  It should also speed up the release process since it also does a lot of the previously manually steps, such as signing.



---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Allen Wittenauer <aw...@effectivemachines.com>]

> On Oct 6, 2016, at 1:39 PM, Akira Ajisaka <aj...@oss.nttdata.co.jp> wrote:
> 
> > It wasn't 'renamed' to jenkins, prior releases were actually built by and on the Jenkins infrastructure. Which was a very very bad idea:  it's insecure and pretty much against ASF policy.
> 
> Sorry for the confusion. I should not have used the word 'rename'.
> What I meant is that "would you change the name to 'jenkins' by using the Jenkins infra?"


To re-iterate, building on the jenkins servers is a violation of ASF release policy and the PMC pretty much has a duty to vote -1 on any such release.  

http://www.apache.org/dev/release.html#owned-controlled-hardware

--snip--

Must releases be built on hardware owned and controlled by the committer?

....

Practically speaking, when a release consists of anything beyond an archive (e.g., tarball or zip file) of a source control tag, the only practical way to validate that archive is to build it locally; manually inspecting generated files (especially binary files) is not feasible. So, basically, "Yes".

--snip--

The ASF build servers are multi-user and run many many many untested code bases.  It would be extremely easy to inject class files into any running compile (Docker-ized or otherwise).   This means that any build that comes from those servers should be considered untrusted, especially from a release perspective.

For 3.x releases, I rewrote create-release and added the --asfrelease option to specifically provide a way for us to get consistent release candidates regardless of who builds it.  It should also speed up the release process since it also does a lot of the previously manually steps, such as signing.



---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Sangjin Lee <sj...@apache.org>]

I looked into building it on jenkins earlier, but it appears that this
jenkins job is busted (at least for 2.6.x):
https://builds.apache.org/job/HADOOP2_Release_Artifacts_Builder/

I don't have access to the job configuration, so I'm unable to fix it atm.

That said, I do think Allen has a point. It strikes me that the release
manager building it under his/her own control shouldn't be a problem, if
not better. Also, the how-to-release wiki currently seems to suggest
building it locally is fine (http://wiki.apache.org/hadoop/HowToRelease).

IMO I don't think this is a blocker. Thoughts?

Thanks,
Sangjin

On Thu, Oct 6, 2016 at 1:39 PM, Akira Ajisaka <aj...@oss.nttdata.co.jp>
wrote:

> > It wasn't 'renamed' to jenkins, prior releases were actually built by
> and on the Jenkins infrastructure. Which was a very very bad idea:  it's
> insecure and pretty much against ASF policy.
>
> Sorry for the confusion. I should not have used the word 'rename'.
> What I meant is that "would you change the name to 'jenkins' by using the
> Jenkins infra?"
>
> Regards,
> Akira
>
>
> On 10/7/16 03:04, Allen Wittenauer wrote:
>
>>
>> On Oct 5, 2016, at 10:35 PM, Akira Ajisaka <aj...@oss.nttdata.co.jp>
>>> wrote:
>>> Can we rename it?
>>>
>>> AFAIK, hadoop releases were built by hortonmu in 2014 and was renamed to
>>> jenkins.
>>>
>>
>>         That's not how that works.
>>
>>         It's literally storing the id of the person who built the
>> classes.  It wasn't 'renamed' to jenkins, prior releases were actually
>> built by and on the Jenkins infrastructure. Which was a very very bad
>> idea:  it's insecure and pretty much against ASF policy.
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Sangjin Lee <sj...@apache.org>]

I looked into building it on jenkins earlier, but it appears that this
jenkins job is busted (at least for 2.6.x):
https://builds.apache.org/job/HADOOP2_Release_Artifacts_Builder/

I don't have access to the job configuration, so I'm unable to fix it atm.

That said, I do think Allen has a point. It strikes me that the release
manager building it under his/her own control shouldn't be a problem, if
not better. Also, the how-to-release wiki currently seems to suggest
building it locally is fine (http://wiki.apache.org/hadoop/HowToRelease).

IMO I don't think this is a blocker. Thoughts?

Thanks,
Sangjin

On Thu, Oct 6, 2016 at 1:39 PM, Akira Ajisaka <aj...@oss.nttdata.co.jp>
wrote:

> > It wasn't 'renamed' to jenkins, prior releases were actually built by
> and on the Jenkins infrastructure. Which was a very very bad idea:  it's
> insecure and pretty much against ASF policy.
>
> Sorry for the confusion. I should not have used the word 'rename'.
> What I meant is that "would you change the name to 'jenkins' by using the
> Jenkins infra?"
>
> Regards,
> Akira
>
>
> On 10/7/16 03:04, Allen Wittenauer wrote:
>
>>
>> On Oct 5, 2016, at 10:35 PM, Akira Ajisaka <aj...@oss.nttdata.co.jp>
>>> wrote:
>>> Can we rename it?
>>>
>>> AFAIK, hadoop releases were built by hortonmu in 2014 and was renamed to
>>> jenkins.
>>>
>>
>>         That's not how that works.
>>
>>         It's literally storing the id of the person who built the
>> classes.  It wasn't 'renamed' to jenkins, prior releases were actually
>> built by and on the Jenkins infrastructure. Which was a very very bad
>> idea:  it's insecure and pretty much against ASF policy.
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Allen Wittenauer <aw...@effectivemachines.com>]

> On Oct 6, 2016, at 1:39 PM, Akira Ajisaka <aj...@oss.nttdata.co.jp> wrote:
> 
> > It wasn't 'renamed' to jenkins, prior releases were actually built by and on the Jenkins infrastructure. Which was a very very bad idea:  it's insecure and pretty much against ASF policy.
> 
> Sorry for the confusion. I should not have used the word 'rename'.
> What I meant is that "would you change the name to 'jenkins' by using the Jenkins infra?"


To re-iterate, building on the jenkins servers is a violation of ASF release policy and the PMC pretty much has a duty to vote -1 on any such release.  

http://www.apache.org/dev/release.html#owned-controlled-hardware

--snip--

Must releases be built on hardware owned and controlled by the committer?

....

Practically speaking, when a release consists of anything beyond an archive (e.g., tarball or zip file) of a source control tag, the only practical way to validate that archive is to build it locally; manually inspecting generated files (especially binary files) is not feasible. So, basically, "Yes".

--snip--

The ASF build servers are multi-user and run many many many untested code bases.  It would be extremely easy to inject class files into any running compile (Docker-ized or otherwise).   This means that any build that comes from those servers should be considered untrusted, especially from a release perspective.

For 3.x releases, I rewrote create-release and added the --asfrelease option to specifically provide a way for us to get consistent release candidates regardless of who builds it.  It should also speed up the release process since it also does a lot of the previously manually steps, such as signing.



---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Sangjin Lee <sj...@apache.org>]

I looked into building it on jenkins earlier, but it appears that this
jenkins job is busted (at least for 2.6.x):
https://builds.apache.org/job/HADOOP2_Release_Artifacts_Builder/

I don't have access to the job configuration, so I'm unable to fix it atm.

That said, I do think Allen has a point. It strikes me that the release
manager building it under his/her own control shouldn't be a problem, if
not better. Also, the how-to-release wiki currently seems to suggest
building it locally is fine (http://wiki.apache.org/hadoop/HowToRelease).

IMO I don't think this is a blocker. Thoughts?

Thanks,
Sangjin

On Thu, Oct 6, 2016 at 1:39 PM, Akira Ajisaka <aj...@oss.nttdata.co.jp>
wrote:

> > It wasn't 'renamed' to jenkins, prior releases were actually built by
> and on the Jenkins infrastructure. Which was a very very bad idea:  it's
> insecure and pretty much against ASF policy.
>
> Sorry for the confusion. I should not have used the word 'rename'.
> What I meant is that "would you change the name to 'jenkins' by using the
> Jenkins infra?"
>
> Regards,
> Akira
>
>
> On 10/7/16 03:04, Allen Wittenauer wrote:
>
>>
>> On Oct 5, 2016, at 10:35 PM, Akira Ajisaka <aj...@oss.nttdata.co.jp>
>>> wrote:
>>> Can we rename it?
>>>
>>> AFAIK, hadoop releases were built by hortonmu in 2014 and was renamed to
>>> jenkins.
>>>
>>
>>         That's not how that works.
>>
>>         It's literally storing the id of the person who built the
>> classes.  It wasn't 'renamed' to jenkins, prior releases were actually
>> built by and on the Jenkins infrastructure. Which was a very very bad
>> idea:  it's insecure and pretty much against ASF policy.
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Allen Wittenauer <aw...@effectivemachines.com>]

> On Oct 6, 2016, at 1:39 PM, Akira Ajisaka <aj...@oss.nttdata.co.jp> wrote:
> 
> > It wasn't 'renamed' to jenkins, prior releases were actually built by and on the Jenkins infrastructure. Which was a very very bad idea:  it's insecure and pretty much against ASF policy.
> 
> Sorry for the confusion. I should not have used the word 'rename'.
> What I meant is that "would you change the name to 'jenkins' by using the Jenkins infra?"


To re-iterate, building on the jenkins servers is a violation of ASF release policy and the PMC pretty much has a duty to vote -1 on any such release.  

http://www.apache.org/dev/release.html#owned-controlled-hardware

--snip--

Must releases be built on hardware owned and controlled by the committer?

....

Practically speaking, when a release consists of anything beyond an archive (e.g., tarball or zip file) of a source control tag, the only practical way to validate that archive is to build it locally; manually inspecting generated files (especially binary files) is not feasible. So, basically, "Yes".

--snip--

The ASF build servers are multi-user and run many many many untested code bases.  It would be extremely easy to inject class files into any running compile (Docker-ized or otherwise).   This means that any build that comes from those servers should be considered untrusted, especially from a release perspective.

For 3.x releases, I rewrote create-release and added the --asfrelease option to specifically provide a way for us to get consistent release candidates regardless of who builds it.  It should also speed up the release process since it also does a lot of the previously manually steps, such as signing.



---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Akira Ajisaka <aj...@oss.nttdata.co.jp>]

 > It wasn't 'renamed' to jenkins, prior releases were actually built by 
and on the Jenkins infrastructure. Which was a very very bad idea:  it's 
insecure and pretty much against ASF policy.

Sorry for the confusion. I should not have used the word 'rename'.
What I meant is that "would you change the name to 'jenkins' by using 
the Jenkins infra?"

Regards,
Akira

On 10/7/16 03:04, Allen Wittenauer wrote:
>
>> On Oct 5, 2016, at 10:35 PM, Akira Ajisaka <aj...@oss.nttdata.co.jp> wrote:
>> Can we rename it?
>>
>> AFAIK, hadoop releases were built by hortonmu in 2014 and was renamed to jenkins.
>
> 	That's not how that works.
>
> 	It's literally storing the id of the person who built the classes.  It wasn't 'renamed' to jenkins, prior releases were actually built by and on the Jenkins infrastructure. Which was a very very bad idea:  it's insecure and pretty much against ASF policy.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Akira Ajisaka <aj...@oss.nttdata.co.jp>]

 > It wasn't 'renamed' to jenkins, prior releases were actually built by 
and on the Jenkins infrastructure. Which was a very very bad idea:  it's 
insecure and pretty much against ASF policy.

Sorry for the confusion. I should not have used the word 'rename'.
What I meant is that "would you change the name to 'jenkins' by using 
the Jenkins infra?"

Regards,
Akira

On 10/7/16 03:04, Allen Wittenauer wrote:
>
>> On Oct 5, 2016, at 10:35 PM, Akira Ajisaka <aj...@oss.nttdata.co.jp> wrote:
>> Can we rename it?
>>
>> AFAIK, hadoop releases were built by hortonmu in 2014 and was renamed to jenkins.
>
> 	That's not how that works.
>
> 	It's literally storing the id of the person who built the classes.  It wasn't 'renamed' to jenkins, prior releases were actually built by and on the Jenkins infrastructure. Which was a very very bad idea:  it's insecure and pretty much against ASF policy.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Akira Ajisaka <aj...@oss.nttdata.co.jp>]

 > It wasn't 'renamed' to jenkins, prior releases were actually built by 
and on the Jenkins infrastructure. Which was a very very bad idea:  it's 
insecure and pretty much against ASF policy.

Sorry for the confusion. I should not have used the word 'rename'.
What I meant is that "would you change the name to 'jenkins' by using 
the Jenkins infra?"

Regards,
Akira

On 10/7/16 03:04, Allen Wittenauer wrote:
>
>> On Oct 5, 2016, at 10:35 PM, Akira Ajisaka <aj...@oss.nttdata.co.jp> wrote:
>> Can we rename it?
>>
>> AFAIK, hadoop releases were built by hortonmu in 2014 and was renamed to jenkins.
>
> 	That's not how that works.
>
> 	It's literally storing the id of the person who built the classes.  It wasn't 'renamed' to jenkins, prior releases were actually built by and on the Jenkins infrastructure. Which was a very very bad idea:  it's insecure and pretty much against ASF policy.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Akira Ajisaka <aj...@oss.nttdata.co.jp>]

 > It wasn't 'renamed' to jenkins, prior releases were actually built by 
and on the Jenkins infrastructure. Which was a very very bad idea:  it's 
insecure and pretty much against ASF policy.

Sorry for the confusion. I should not have used the word 'rename'.
What I meant is that "would you change the name to 'jenkins' by using 
the Jenkins infra?"

Regards,
Akira

On 10/7/16 03:04, Allen Wittenauer wrote:
>
>> On Oct 5, 2016, at 10:35 PM, Akira Ajisaka <aj...@oss.nttdata.co.jp> wrote:
>> Can we rename it?
>>
>> AFAIK, hadoop releases were built by hortonmu in 2014 and was renamed to jenkins.
>
> 	That's not how that works.
>
> 	It's literally storing the id of the person who built the classes.  It wasn't 'renamed' to jenkins, prior releases were actually built by and on the Jenkins infrastructure. Which was a very very bad idea:  it's insecure and pretty much against ASF policy.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Allen Wittenauer <aw...@effectivemachines.com>]

> On Oct 5, 2016, at 10:35 PM, Akira Ajisaka <aj...@oss.nttdata.co.jp> wrote:
> Can we rename it?
> 
> AFAIK, hadoop releases were built by hortonmu in 2014 and was renamed to jenkins.

	That's not how that works.

	It's literally storing the id of the person who built the classes.  It wasn't 'renamed' to jenkins, prior releases were actually built by and on the Jenkins infrastructure. Which was a very very bad idea:  it's insecure and pretty much against ASF policy.
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Allen Wittenauer <aw...@effectivemachines.com>]

> On Oct 5, 2016, at 10:35 PM, Akira Ajisaka <aj...@oss.nttdata.co.jp> wrote:
> Can we rename it?
> 
> AFAIK, hadoop releases were built by hortonmu in 2014 and was renamed to jenkins.

	That's not how that works.

	It's literally storing the id of the person who built the classes.  It wasn't 'renamed' to jenkins, prior releases were actually built by and on the Jenkins infrastructure. Which was a very very bad idea:  it's insecure and pretty much against ASF policy.
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Allen Wittenauer <aw...@effectivemachines.com>]

> On Oct 5, 2016, at 10:35 PM, Akira Ajisaka <aj...@oss.nttdata.co.jp> wrote:
> Can we rename it?
> 
> AFAIK, hadoop releases were built by hortonmu in 2014 and was renamed to jenkins.

	That's not how that works.

	It's literally storing the id of the person who built the classes.  It wasn't 'renamed' to jenkins, prior releases were actually built by and on the Jenkins infrastructure. Which was a very very bad idea:  it's insecure and pretty much against ASF policy.
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Allen Wittenauer <aw...@effectivemachines.com>]

> On Oct 5, 2016, at 10:35 PM, Akira Ajisaka <aj...@oss.nttdata.co.jp> wrote:
> Can we rename it?
> 
> AFAIK, hadoop releases were built by hortonmu in 2014 and was renamed to jenkins.

	That's not how that works.

	It's literally storing the id of the person who built the classes.  It wasn't 'renamed' to jenkins, prior releases were actually built by and on the Jenkins infrastructure. Which was a very very bad idea:  it's insecure and pretty much against ASF policy.
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Akira Ajisaka <aj...@oss.nttdata.co.jp>]

Hi Sangjin,

When using binary tarball, I'm seeing
"2016-09-27T18:26Z by sjlee from branch-2.6.5" in Web UI.
Can we rename it?

AFAIK, hadoop releases were built by hortonmu in 2014 and was renamed to 
jenkins.

* 
http://mail-archives.apache.org/mod_mbox/hadoop-common-dev/201401.mbox/%3CCAJs-t7NiJAJceO=6L8vr1uOr-Es=Z1y-UfkQXr8Ya5hq3-D23Q@mail.gmail.com%3E
* https://issues.apache.org/jira/browse/HADOOP-10313

Regards,
Akira

On 10/3/16 09:12, Sangjin Lee wrote:
> Hi folks,
>
> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> release (the next maintenance release in the 2.6.x release line). RC1
> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
>
> Below are the details of this release candidate:
>
> The RC is available for validation at:
> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
>
> The RC tag in git is release-2.6.5-RC1 and its git commit is
> e8c9fe0b4c252caf2ebf1464220599650f119997.
>
> The maven artifacts are staged via repository.apache.org at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1050/.
>
> You can find my public key at
> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
>
> Please try the release and vote. The vote will run for the usual 5 days. I
> would greatly appreciate your timely vote. Thanks!
>
> Regards,
> Sangjin
>


---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Akira Ajisaka <aj...@oss.nttdata.co.jp>]

Hi Sangjin,

When using binary tarball, I'm seeing
"2016-09-27T18:26Z by sjlee from branch-2.6.5" in Web UI.
Can we rename it?

AFAIK, hadoop releases were built by hortonmu in 2014 and was renamed to 
jenkins.

* 
http://mail-archives.apache.org/mod_mbox/hadoop-common-dev/201401.mbox/%3CCAJs-t7NiJAJceO=6L8vr1uOr-Es=Z1y-UfkQXr8Ya5hq3-D23Q@mail.gmail.com%3E
* https://issues.apache.org/jira/browse/HADOOP-10313

Regards,
Akira

On 10/3/16 09:12, Sangjin Lee wrote:
> Hi folks,
>
> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> release (the next maintenance release in the 2.6.x release line). RC1
> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
>
> Below are the details of this release candidate:
>
> The RC is available for validation at:
> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
>
> The RC tag in git is release-2.6.5-RC1 and its git commit is
> e8c9fe0b4c252caf2ebf1464220599650f119997.
>
> The maven artifacts are staged via repository.apache.org at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1050/.
>
> You can find my public key at
> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
>
> Please try the release and vote. The vote will run for the usual 5 days. I
> would greatly appreciate your timely vote. Thanks!
>
> Regards,
> Sangjin
>


---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Brahma Reddy Battula <br...@apache.org>]

Thanks Sangjin!


+1 ( non- binding)


--Downloaded the source and complied

--Installed HA cluster

--Verified basic fsshell commands

--Ran pi,terasort Slive jobs, all works fine.



--Brahma Reddy Battula

On Mon, Oct 3, 2016 at 5:42 AM, Sangjin Lee <sj...@apache.org> wrote:

> Hi folks,
>
> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> release (the next maintenance release in the 2.6.x release line). RC1
> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
>
> Below are the details of this release candidate:
>
> The RC is available for validation at:
> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
>
> The RC tag in git is release-2.6.5-RC1 and its git commit is
> e8c9fe0b4c252caf2ebf1464220599650f119997.
>
> The maven artifacts are staged via repository.apache.org at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1050/.
>
> You can find my public key at
> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
>
> Please try the release and vote. The vote will run for the usual 5 days. I
> would greatly appreciate your timely vote. Thanks!
>
> Regards,
> Sangjin
>



-- 



--Brahma Reddy Battula

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Sangjin Lee <sj...@apache.org>]

Thanks everyone for checking out this release! The vote passes with 15
+1's, 7 of which are binding, and no -1's.

I'll go ahead and wrap up the release, and will send an announcement in the
next day or two.

Regards,
Sangjin

On Mon, Oct 10, 2016 at 6:38 AM, Jason Lowe <jl...@yahoo-inc.com> wrote:

> +1 (binding)
>
> - Verified signatures and digests
> - Built native from source
> - Deployed to a single-node cluster and ran some sample jobs
>
> Jason
>
>
> On Sunday, October 2, 2016 7:13 PM, Sangjin Lee <sj...@apache.org> wrote:
>
>
> Hi folks,
>
> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> release (the next maintenance release in the 2.6.x release line). RC1
> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
>
> Below are the details of this release candidate:
>
> The RC is available for validation at:
> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
>
> The RC tag in git is release-2.6.5-RC1 and its git commit is
> e8c9fe0b4c252caf2ebf1464220599650f119997.
>
> The maven artifacts are staged via repository.apache.org at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1050/.
>
> You can find my public key at
> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
>
> Please try the release and vote. The vote will run for the usual 5 days. I
> would greatly appreciate your timely vote. Thanks!
>
> Regards,
> Sangjin
>
>
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Sangjin Lee <sj...@apache.org>]

Thanks everyone for checking out this release! The vote passes with 15
+1's, 7 of which are binding, and no -1's.

I'll go ahead and wrap up the release, and will send an announcement in the
next day or two.

Regards,
Sangjin

On Mon, Oct 10, 2016 at 6:38 AM, Jason Lowe <jl...@yahoo-inc.com> wrote:

> +1 (binding)
>
> - Verified signatures and digests
> - Built native from source
> - Deployed to a single-node cluster and ran some sample jobs
>
> Jason
>
>
> On Sunday, October 2, 2016 7:13 PM, Sangjin Lee <sj...@apache.org> wrote:
>
>
> Hi folks,
>
> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> release (the next maintenance release in the 2.6.x release line). RC1
> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
>
> Below are the details of this release candidate:
>
> The RC is available for validation at:
> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
>
> The RC tag in git is release-2.6.5-RC1 and its git commit is
> e8c9fe0b4c252caf2ebf1464220599650f119997.
>
> The maven artifacts are staged via repository.apache.org at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1050/.
>
> You can find my public key at
> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
>
> Please try the release and vote. The vote will run for the usual 5 days. I
> would greatly appreciate your timely vote. Thanks!
>
> Regards,
> Sangjin
>
>
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Sangjin Lee <sj...@apache.org>]

Thanks everyone for checking out this release! The vote passes with 15
+1's, 7 of which are binding, and no -1's.

I'll go ahead and wrap up the release, and will send an announcement in the
next day or two.

Regards,
Sangjin

On Mon, Oct 10, 2016 at 6:38 AM, Jason Lowe <jl...@yahoo-inc.com> wrote:

> +1 (binding)
>
> - Verified signatures and digests
> - Built native from source
> - Deployed to a single-node cluster and ran some sample jobs
>
> Jason
>
>
> On Sunday, October 2, 2016 7:13 PM, Sangjin Lee <sj...@apache.org> wrote:
>
>
> Hi folks,
>
> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> release (the next maintenance release in the 2.6.x release line). RC1
> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
>
> Below are the details of this release candidate:
>
> The RC is available for validation at:
> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
>
> The RC tag in git is release-2.6.5-RC1 and its git commit is
> e8c9fe0b4c252caf2ebf1464220599650f119997.
>
> The maven artifacts are staged via repository.apache.org at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1050/.
>
> You can find my public key at
> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
>
> Please try the release and vote. The vote will run for the usual 5 days. I
> would greatly appreciate your timely vote. Thanks!
>
> Regards,
> Sangjin
>
>
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Sangjin Lee <sj...@apache.org>]

Thanks everyone for checking out this release! The vote passes with 15
+1's, 7 of which are binding, and no -1's.

I'll go ahead and wrap up the release, and will send an announcement in the
next day or two.

Regards,
Sangjin

On Mon, Oct 10, 2016 at 6:38 AM, Jason Lowe <jl...@yahoo-inc.com> wrote:

> +1 (binding)
>
> - Verified signatures and digests
> - Built native from source
> - Deployed to a single-node cluster and ran some sample jobs
>
> Jason
>
>
> On Sunday, October 2, 2016 7:13 PM, Sangjin Lee <sj...@apache.org> wrote:
>
>
> Hi folks,
>
> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> release (the next maintenance release in the 2.6.x release line). RC1
> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
>
> Below are the details of this release candidate:
>
> The RC is available for validation at:
> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
>
> The RC tag in git is release-2.6.5-RC1 and its git commit is
> e8c9fe0b4c252caf2ebf1464220599650f119997.
>
> The maven artifacts are staged via repository.apache.org at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1050/.
>
> You can find my public key at
> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
>
> Please try the release and vote. The vote will run for the usual 5 days. I
> would greatly appreciate your timely vote. Thanks!
>
> Regards,
> Sangjin
>
>
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Jason Lowe <jl...@yahoo-inc.com.INVALID>]

+1 (binding)
- Verified signatures and digests- Built native from source- Deployed to a single-node cluster and ran some sample jobs
Jason
 

    On Sunday, October 2, 2016 7:13 PM, Sangjin Lee <sj...@apache.org> wrote:
 

 Hi folks,

I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
release (the next maintenance release in the 2.6.x release line). RC1
contains fixes to CHANGES.txt, and is otherwise identical to RC0.

Below are the details of this release candidate:

The RC is available for validation at:
http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.

The RC tag in git is release-2.6.5-RC1 and its git commit is
e8c9fe0b4c252caf2ebf1464220599650f119997.

The maven artifacts are staged via repository.apache.org at:
https://repository.apache.org/content/repositories/orgapachehadoop-1050/.

You can find my public key at
http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.

Please try the release and vote. The vote will run for the usual 5 days. I
would greatly appreciate your timely vote. Thanks!

Regards,
Sangjin


   

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Jason Lowe <jl...@yahoo-inc.com.INVALID>]

+1 (binding)
- Verified signatures and digests- Built native from source- Deployed to a single-node cluster and ran some sample jobs
Jason
 

    On Sunday, October 2, 2016 7:13 PM, Sangjin Lee <sj...@apache.org> wrote:
 

 Hi folks,

I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
release (the next maintenance release in the 2.6.x release line). RC1
contains fixes to CHANGES.txt, and is otherwise identical to RC0.

Below are the details of this release candidate:

The RC is available for validation at:
http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.

The RC tag in git is release-2.6.5-RC1 and its git commit is
e8c9fe0b4c252caf2ebf1464220599650f119997.

The maven artifacts are staged via repository.apache.org at:
https://repository.apache.org/content/repositories/orgapachehadoop-1050/.

You can find my public key at
http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.

Please try the release and vote. The vote will run for the usual 5 days. I
would greatly appreciate your timely vote. Thanks!

Regards,
Sangjin


   

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Chris Trezzo <ct...@gmail.com>]

+1 (non-binding)

Thanks for cutting another release candidate Sangjin!

1. Diff'ed the CHANGES-*.txt files against the branch-2.6.5 git log and
verified the set of listed issues matches.
2. Verified md5 checksums and signature on src and binary tar.gz.
3. Built from source.
4. Started up a pseudo distributed cluster.
5. Successfully ran a PI job.
6. Ran the balancer.
7. Inspected UI for RM, NN, JobHistory.

On Sun, Oct 2, 2016 at 5:12 PM, Sangjin Lee <sj...@apache.org> wrote:

> Hi folks,
>
> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> release (the next maintenance release in the 2.6.x release line). RC1
> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
>
> Below are the details of this release candidate:
>
> The RC is available for validation at:
> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
>
> The RC tag in git is release-2.6.5-RC1 and its git commit is
> e8c9fe0b4c252caf2ebf1464220599650f119997.
>
> The maven artifacts are staged via repository.apache.org at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1050/.
>
> You can find my public key at
> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
>
> Please try the release and vote. The vote will run for the usual 5 days. I
> would greatly appreciate your timely vote. Thanks!
>
> Regards,
> Sangjin
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Rohith Sharma K S <ks...@gmail.com>]

+1 ( non- binding)

--Downloaded source and built from it.
--Installed 3 node cluster with HA deployed. 
—Ran sample MR jobs and tested with basics operations.
— Integrated JCarder tool to find any potential deadlock cycles. And did  not observe any potential cycles.

Thanks & Regards
Rohith Sharma K S

> On Oct 3, 2016, at 5:42 AM, Sangjin Lee <sj...@apache.org> wrote:
> 
> Hi folks,
> 
> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> release (the next maintenance release in the 2.6.x release line). RC1
> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
> 
> Below are the details of this release candidate:
> 
> The RC is available for validation at:
> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
> 
> The RC tag in git is release-2.6.5-RC1 and its git commit is
> e8c9fe0b4c252caf2ebf1464220599650f119997.
> 
> The maven artifacts are staged via repository.apache.org at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1050/.
> 
> You can find my public key at
> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
> 
> Please try the release and vote. The vote will run for the usual 5 days. I
> would greatly appreciate your timely vote. Thanks!
> 
> Regards,
> Sangjin


---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Sangjin Lee <sj...@apache.org>]

I'm casting my vote: +1 (binding)

Regards,
Sangjin

On Fri, Oct 7, 2016 at 3:12 PM, Andrew Wang <an...@cloudera.com>
wrote:

> Thanks to Chris and Sangjin for working on this release.
>
> +1 binding
>
> * Verified signatures
> * Built from source tarball
> * Started HDFS and did some basic ops
>
> Thanks,
> Andrew
>
> On Fri, Oct 7, 2016 at 2:50 PM, Wangda Tan <wh...@gmail.com> wrote:
>
> > Thanks Sangjin for cutting this release!
> >
> > +1 (Binding)
> >
> > - Downloaded binary tar ball and setup a single node cluster.
> > - Submit a few applications and which can successfully run.
> >
> > Thanks,
> > Wangda
> >
> >
> > On Fri, Oct 7, 2016 at 10:33 AM, Zhihai Xu <zh...@gmail.com>
> wrote:
> >
> > > Thanks Sangjin for creating release 2.6.5 RC1.
> > >
> > > +1 (non-binding)
> > >
> > > * Downloaded and built from source
> > > * Verified md5 checksums and signature
> > > * Deployed a pseudo cluster
> > > * verified basic HDFS operations and Pi job.
> > > * Did a sanity check for RM and NM UI.
> > >
> > > Thanks
> > > zhihai
> > >
> > > On Fri, Oct 7, 2016 at 8:16 AM, Sangjin Lee <sj...@apache.org> wrote:
> > >
> > > > Thanks Masatake!
> > > >
> > > > Today's the last day for this vote, and I'd like to ask you to try
> out
> > > the
> > > > RC and vote on this today. So far there has been no binding vote.
> > Thanks
> > > > again.
> > > >
> > > > Regards,
> > > > Sangjin
> > > >
> > > > On Fri, Oct 7, 2016 at 6:45 AM, Masatake Iwasaki <
> > > > iwasakims@oss.nttdata.co.jp> wrote:
> > > >
> > > > > +1(non-binding)
> > > > >
> > > > > * verified signature and md5.
> > > > > * built with -Pnative on CentOS6 and OpenJDK7.
> > > > > * built documentation and skimmed the contents.
> > > > > * built rpms by bigtop and ran smoke-tests of hdfs, yarn and
> > mapreduce
> > > on
> > > > > 3-node cluster.
> > > > >
> > > > > Thanks,
> > > > > Masatake Iwasaki
> > > > >
> > > > > On 10/3/16 09:12, Sangjin Lee wrote:
> > > > >
> > > > >> Hi folks,
> > > > >>
> > > > >> I have pushed a new release candidate (R1) for the Apache Hadoop
> > 2.6.5
> > > > >> release (the next maintenance release in the 2.6.x release line).
> > RC1
> > > > >> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
> > > > >>
> > > > >> Below are the details of this release candidate:
> > > > >>
> > > > >> The RC is available for validation at:
> > > > >> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
> > > > >>
> > > > >> The RC tag in git is release-2.6.5-RC1 and its git commit is
> > > > >> e8c9fe0b4c252caf2ebf1464220599650f119997.
> > > > >>
> > > > >> The maven artifacts are staged via repository.apache.org at:
> > > > >> https://repository.apache.org/content/repositories/
> > > > orgapachehadoop-1050/.
> > > > >>
> > > > >> You can find my public key at
> > > > >> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
> > > > >>
> > > > >> Please try the release and vote. The vote will run for the usual 5
> > > > days. I
> > > > >> would greatly appreciate your timely vote. Thanks!
> > > > >>
> > > > >> Regards,
> > > > >> Sangjin
> > > > >>
> > > > >>
> > > > >
> > > >
> > >
> >
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Sangjin Lee <sj...@apache.org>]

I'm casting my vote: +1 (binding)

Regards,
Sangjin

On Fri, Oct 7, 2016 at 3:12 PM, Andrew Wang <an...@cloudera.com>
wrote:

> Thanks to Chris and Sangjin for working on this release.
>
> +1 binding
>
> * Verified signatures
> * Built from source tarball
> * Started HDFS and did some basic ops
>
> Thanks,
> Andrew
>
> On Fri, Oct 7, 2016 at 2:50 PM, Wangda Tan <wh...@gmail.com> wrote:
>
> > Thanks Sangjin for cutting this release!
> >
> > +1 (Binding)
> >
> > - Downloaded binary tar ball and setup a single node cluster.
> > - Submit a few applications and which can successfully run.
> >
> > Thanks,
> > Wangda
> >
> >
> > On Fri, Oct 7, 2016 at 10:33 AM, Zhihai Xu <zh...@gmail.com>
> wrote:
> >
> > > Thanks Sangjin for creating release 2.6.5 RC1.
> > >
> > > +1 (non-binding)
> > >
> > > * Downloaded and built from source
> > > * Verified md5 checksums and signature
> > > * Deployed a pseudo cluster
> > > * verified basic HDFS operations and Pi job.
> > > * Did a sanity check for RM and NM UI.
> > >
> > > Thanks
> > > zhihai
> > >
> > > On Fri, Oct 7, 2016 at 8:16 AM, Sangjin Lee <sj...@apache.org> wrote:
> > >
> > > > Thanks Masatake!
> > > >
> > > > Today's the last day for this vote, and I'd like to ask you to try
> out
> > > the
> > > > RC and vote on this today. So far there has been no binding vote.
> > Thanks
> > > > again.
> > > >
> > > > Regards,
> > > > Sangjin
> > > >
> > > > On Fri, Oct 7, 2016 at 6:45 AM, Masatake Iwasaki <
> > > > iwasakims@oss.nttdata.co.jp> wrote:
> > > >
> > > > > +1(non-binding)
> > > > >
> > > > > * verified signature and md5.
> > > > > * built with -Pnative on CentOS6 and OpenJDK7.
> > > > > * built documentation and skimmed the contents.
> > > > > * built rpms by bigtop and ran smoke-tests of hdfs, yarn and
> > mapreduce
> > > on
> > > > > 3-node cluster.
> > > > >
> > > > > Thanks,
> > > > > Masatake Iwasaki
> > > > >
> > > > > On 10/3/16 09:12, Sangjin Lee wrote:
> > > > >
> > > > >> Hi folks,
> > > > >>
> > > > >> I have pushed a new release candidate (R1) for the Apache Hadoop
> > 2.6.5
> > > > >> release (the next maintenance release in the 2.6.x release line).
> > RC1
> > > > >> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
> > > > >>
> > > > >> Below are the details of this release candidate:
> > > > >>
> > > > >> The RC is available for validation at:
> > > > >> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
> > > > >>
> > > > >> The RC tag in git is release-2.6.5-RC1 and its git commit is
> > > > >> e8c9fe0b4c252caf2ebf1464220599650f119997.
> > > > >>
> > > > >> The maven artifacts are staged via repository.apache.org at:
> > > > >> https://repository.apache.org/content/repositories/
> > > > orgapachehadoop-1050/.
> > > > >>
> > > > >> You can find my public key at
> > > > >> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
> > > > >>
> > > > >> Please try the release and vote. The vote will run for the usual 5
> > > > days. I
> > > > >> would greatly appreciate your timely vote. Thanks!
> > > > >>
> > > > >> Regards,
> > > > >> Sangjin
> > > > >>
> > > > >>
> > > > >
> > > >
> > >
> >
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Sangjin Lee <sj...@apache.org>]

I'm casting my vote: +1 (binding)

Regards,
Sangjin

On Fri, Oct 7, 2016 at 3:12 PM, Andrew Wang <an...@cloudera.com>
wrote:

> Thanks to Chris and Sangjin for working on this release.
>
> +1 binding
>
> * Verified signatures
> * Built from source tarball
> * Started HDFS and did some basic ops
>
> Thanks,
> Andrew
>
> On Fri, Oct 7, 2016 at 2:50 PM, Wangda Tan <wh...@gmail.com> wrote:
>
> > Thanks Sangjin for cutting this release!
> >
> > +1 (Binding)
> >
> > - Downloaded binary tar ball and setup a single node cluster.
> > - Submit a few applications and which can successfully run.
> >
> > Thanks,
> > Wangda
> >
> >
> > On Fri, Oct 7, 2016 at 10:33 AM, Zhihai Xu <zh...@gmail.com>
> wrote:
> >
> > > Thanks Sangjin for creating release 2.6.5 RC1.
> > >
> > > +1 (non-binding)
> > >
> > > * Downloaded and built from source
> > > * Verified md5 checksums and signature
> > > * Deployed a pseudo cluster
> > > * verified basic HDFS operations and Pi job.
> > > * Did a sanity check for RM and NM UI.
> > >
> > > Thanks
> > > zhihai
> > >
> > > On Fri, Oct 7, 2016 at 8:16 AM, Sangjin Lee <sj...@apache.org> wrote:
> > >
> > > > Thanks Masatake!
> > > >
> > > > Today's the last day for this vote, and I'd like to ask you to try
> out
> > > the
> > > > RC and vote on this today. So far there has been no binding vote.
> > Thanks
> > > > again.
> > > >
> > > > Regards,
> > > > Sangjin
> > > >
> > > > On Fri, Oct 7, 2016 at 6:45 AM, Masatake Iwasaki <
> > > > iwasakims@oss.nttdata.co.jp> wrote:
> > > >
> > > > > +1(non-binding)
> > > > >
> > > > > * verified signature and md5.
> > > > > * built with -Pnative on CentOS6 and OpenJDK7.
> > > > > * built documentation and skimmed the contents.
> > > > > * built rpms by bigtop and ran smoke-tests of hdfs, yarn and
> > mapreduce
> > > on
> > > > > 3-node cluster.
> > > > >
> > > > > Thanks,
> > > > > Masatake Iwasaki
> > > > >
> > > > > On 10/3/16 09:12, Sangjin Lee wrote:
> > > > >
> > > > >> Hi folks,
> > > > >>
> > > > >> I have pushed a new release candidate (R1) for the Apache Hadoop
> > 2.6.5
> > > > >> release (the next maintenance release in the 2.6.x release line).
> > RC1
> > > > >> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
> > > > >>
> > > > >> Below are the details of this release candidate:
> > > > >>
> > > > >> The RC is available for validation at:
> > > > >> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
> > > > >>
> > > > >> The RC tag in git is release-2.6.5-RC1 and its git commit is
> > > > >> e8c9fe0b4c252caf2ebf1464220599650f119997.
> > > > >>
> > > > >> The maven artifacts are staged via repository.apache.org at:
> > > > >> https://repository.apache.org/content/repositories/
> > > > orgapachehadoop-1050/.
> > > > >>
> > > > >> You can find my public key at
> > > > >> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
> > > > >>
> > > > >> Please try the release and vote. The vote will run for the usual 5
> > > > days. I
> > > > >> would greatly appreciate your timely vote. Thanks!
> > > > >>
> > > > >> Regards,
> > > > >> Sangjin
> > > > >>
> > > > >>
> > > > >
> > > >
> > >
> >
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Sangjin Lee <sj...@apache.org>]

I'm casting my vote: +1 (binding)

Regards,
Sangjin

On Fri, Oct 7, 2016 at 3:12 PM, Andrew Wang <an...@cloudera.com>
wrote:

> Thanks to Chris and Sangjin for working on this release.
>
> +1 binding
>
> * Verified signatures
> * Built from source tarball
> * Started HDFS and did some basic ops
>
> Thanks,
> Andrew
>
> On Fri, Oct 7, 2016 at 2:50 PM, Wangda Tan <wh...@gmail.com> wrote:
>
> > Thanks Sangjin for cutting this release!
> >
> > +1 (Binding)
> >
> > - Downloaded binary tar ball and setup a single node cluster.
> > - Submit a few applications and which can successfully run.
> >
> > Thanks,
> > Wangda
> >
> >
> > On Fri, Oct 7, 2016 at 10:33 AM, Zhihai Xu <zh...@gmail.com>
> wrote:
> >
> > > Thanks Sangjin for creating release 2.6.5 RC1.
> > >
> > > +1 (non-binding)
> > >
> > > * Downloaded and built from source
> > > * Verified md5 checksums and signature
> > > * Deployed a pseudo cluster
> > > * verified basic HDFS operations and Pi job.
> > > * Did a sanity check for RM and NM UI.
> > >
> > > Thanks
> > > zhihai
> > >
> > > On Fri, Oct 7, 2016 at 8:16 AM, Sangjin Lee <sj...@apache.org> wrote:
> > >
> > > > Thanks Masatake!
> > > >
> > > > Today's the last day for this vote, and I'd like to ask you to try
> out
> > > the
> > > > RC and vote on this today. So far there has been no binding vote.
> > Thanks
> > > > again.
> > > >
> > > > Regards,
> > > > Sangjin
> > > >
> > > > On Fri, Oct 7, 2016 at 6:45 AM, Masatake Iwasaki <
> > > > iwasakims@oss.nttdata.co.jp> wrote:
> > > >
> > > > > +1(non-binding)
> > > > >
> > > > > * verified signature and md5.
> > > > > * built with -Pnative on CentOS6 and OpenJDK7.
> > > > > * built documentation and skimmed the contents.
> > > > > * built rpms by bigtop and ran smoke-tests of hdfs, yarn and
> > mapreduce
> > > on
> > > > > 3-node cluster.
> > > > >
> > > > > Thanks,
> > > > > Masatake Iwasaki
> > > > >
> > > > > On 10/3/16 09:12, Sangjin Lee wrote:
> > > > >
> > > > >> Hi folks,
> > > > >>
> > > > >> I have pushed a new release candidate (R1) for the Apache Hadoop
> > 2.6.5
> > > > >> release (the next maintenance release in the 2.6.x release line).
> > RC1
> > > > >> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
> > > > >>
> > > > >> Below are the details of this release candidate:
> > > > >>
> > > > >> The RC is available for validation at:
> > > > >> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
> > > > >>
> > > > >> The RC tag in git is release-2.6.5-RC1 and its git commit is
> > > > >> e8c9fe0b4c252caf2ebf1464220599650f119997.
> > > > >>
> > > > >> The maven artifacts are staged via repository.apache.org at:
> > > > >> https://repository.apache.org/content/repositories/
> > > > orgapachehadoop-1050/.
> > > > >>
> > > > >> You can find my public key at
> > > > >> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
> > > > >>
> > > > >> Please try the release and vote. The vote will run for the usual 5
> > > > days. I
> > > > >> would greatly appreciate your timely vote. Thanks!
> > > > >>
> > > > >> Regards,
> > > > >> Sangjin
> > > > >>
> > > > >>
> > > > >
> > > >
> > >
> >
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Andrew Wang <an...@cloudera.com>]

Thanks to Chris and Sangjin for working on this release.

+1 binding

* Verified signatures
* Built from source tarball
* Started HDFS and did some basic ops

Thanks,
Andrew

On Fri, Oct 7, 2016 at 2:50 PM, Wangda Tan <wh...@gmail.com> wrote:

> Thanks Sangjin for cutting this release!
>
> +1 (Binding)
>
> - Downloaded binary tar ball and setup a single node cluster.
> - Submit a few applications and which can successfully run.
>
> Thanks,
> Wangda
>
>
> On Fri, Oct 7, 2016 at 10:33 AM, Zhihai Xu <zh...@gmail.com> wrote:
>
> > Thanks Sangjin for creating release 2.6.5 RC1.
> >
> > +1 (non-binding)
> >
> > * Downloaded and built from source
> > * Verified md5 checksums and signature
> > * Deployed a pseudo cluster
> > * verified basic HDFS operations and Pi job.
> > * Did a sanity check for RM and NM UI.
> >
> > Thanks
> > zhihai
> >
> > On Fri, Oct 7, 2016 at 8:16 AM, Sangjin Lee <sj...@apache.org> wrote:
> >
> > > Thanks Masatake!
> > >
> > > Today's the last day for this vote, and I'd like to ask you to try out
> > the
> > > RC and vote on this today. So far there has been no binding vote.
> Thanks
> > > again.
> > >
> > > Regards,
> > > Sangjin
> > >
> > > On Fri, Oct 7, 2016 at 6:45 AM, Masatake Iwasaki <
> > > iwasakims@oss.nttdata.co.jp> wrote:
> > >
> > > > +1(non-binding)
> > > >
> > > > * verified signature and md5.
> > > > * built with -Pnative on CentOS6 and OpenJDK7.
> > > > * built documentation and skimmed the contents.
> > > > * built rpms by bigtop and ran smoke-tests of hdfs, yarn and
> mapreduce
> > on
> > > > 3-node cluster.
> > > >
> > > > Thanks,
> > > > Masatake Iwasaki
> > > >
> > > > On 10/3/16 09:12, Sangjin Lee wrote:
> > > >
> > > >> Hi folks,
> > > >>
> > > >> I have pushed a new release candidate (R1) for the Apache Hadoop
> 2.6.5
> > > >> release (the next maintenance release in the 2.6.x release line).
> RC1
> > > >> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
> > > >>
> > > >> Below are the details of this release candidate:
> > > >>
> > > >> The RC is available for validation at:
> > > >> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
> > > >>
> > > >> The RC tag in git is release-2.6.5-RC1 and its git commit is
> > > >> e8c9fe0b4c252caf2ebf1464220599650f119997.
> > > >>
> > > >> The maven artifacts are staged via repository.apache.org at:
> > > >> https://repository.apache.org/content/repositories/
> > > orgapachehadoop-1050/.
> > > >>
> > > >> You can find my public key at
> > > >> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
> > > >>
> > > >> Please try the release and vote. The vote will run for the usual 5
> > > days. I
> > > >> would greatly appreciate your timely vote. Thanks!
> > > >>
> > > >> Regards,
> > > >> Sangjin
> > > >>
> > > >>
> > > >
> > >
> >
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Andrew Wang <an...@cloudera.com>]

Thanks to Chris and Sangjin for working on this release.

+1 binding

* Verified signatures
* Built from source tarball
* Started HDFS and did some basic ops

Thanks,
Andrew

On Fri, Oct 7, 2016 at 2:50 PM, Wangda Tan <wh...@gmail.com> wrote:

> Thanks Sangjin for cutting this release!
>
> +1 (Binding)
>
> - Downloaded binary tar ball and setup a single node cluster.
> - Submit a few applications and which can successfully run.
>
> Thanks,
> Wangda
>
>
> On Fri, Oct 7, 2016 at 10:33 AM, Zhihai Xu <zh...@gmail.com> wrote:
>
> > Thanks Sangjin for creating release 2.6.5 RC1.
> >
> > +1 (non-binding)
> >
> > * Downloaded and built from source
> > * Verified md5 checksums and signature
> > * Deployed a pseudo cluster
> > * verified basic HDFS operations and Pi job.
> > * Did a sanity check for RM and NM UI.
> >
> > Thanks
> > zhihai
> >
> > On Fri, Oct 7, 2016 at 8:16 AM, Sangjin Lee <sj...@apache.org> wrote:
> >
> > > Thanks Masatake!
> > >
> > > Today's the last day for this vote, and I'd like to ask you to try out
> > the
> > > RC and vote on this today. So far there has been no binding vote.
> Thanks
> > > again.
> > >
> > > Regards,
> > > Sangjin
> > >
> > > On Fri, Oct 7, 2016 at 6:45 AM, Masatake Iwasaki <
> > > iwasakims@oss.nttdata.co.jp> wrote:
> > >
> > > > +1(non-binding)
> > > >
> > > > * verified signature and md5.
> > > > * built with -Pnative on CentOS6 and OpenJDK7.
> > > > * built documentation and skimmed the contents.
> > > > * built rpms by bigtop and ran smoke-tests of hdfs, yarn and
> mapreduce
> > on
> > > > 3-node cluster.
> > > >
> > > > Thanks,
> > > > Masatake Iwasaki
> > > >
> > > > On 10/3/16 09:12, Sangjin Lee wrote:
> > > >
> > > >> Hi folks,
> > > >>
> > > >> I have pushed a new release candidate (R1) for the Apache Hadoop
> 2.6.5
> > > >> release (the next maintenance release in the 2.6.x release line).
> RC1
> > > >> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
> > > >>
> > > >> Below are the details of this release candidate:
> > > >>
> > > >> The RC is available for validation at:
> > > >> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
> > > >>
> > > >> The RC tag in git is release-2.6.5-RC1 and its git commit is
> > > >> e8c9fe0b4c252caf2ebf1464220599650f119997.
> > > >>
> > > >> The maven artifacts are staged via repository.apache.org at:
> > > >> https://repository.apache.org/content/repositories/
> > > orgapachehadoop-1050/.
> > > >>
> > > >> You can find my public key at
> > > >> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
> > > >>
> > > >> Please try the release and vote. The vote will run for the usual 5
> > > days. I
> > > >> would greatly appreciate your timely vote. Thanks!
> > > >>
> > > >> Regards,
> > > >> Sangjin
> > > >>
> > > >>
> > > >
> > >
> >
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Andrew Wang <an...@cloudera.com>]

Thanks to Chris and Sangjin for working on this release.

+1 binding

* Verified signatures
* Built from source tarball
* Started HDFS and did some basic ops

Thanks,
Andrew

On Fri, Oct 7, 2016 at 2:50 PM, Wangda Tan <wh...@gmail.com> wrote:

> Thanks Sangjin for cutting this release!
>
> +1 (Binding)
>
> - Downloaded binary tar ball and setup a single node cluster.
> - Submit a few applications and which can successfully run.
>
> Thanks,
> Wangda
>
>
> On Fri, Oct 7, 2016 at 10:33 AM, Zhihai Xu <zh...@gmail.com> wrote:
>
> > Thanks Sangjin for creating release 2.6.5 RC1.
> >
> > +1 (non-binding)
> >
> > * Downloaded and built from source
> > * Verified md5 checksums and signature
> > * Deployed a pseudo cluster
> > * verified basic HDFS operations and Pi job.
> > * Did a sanity check for RM and NM UI.
> >
> > Thanks
> > zhihai
> >
> > On Fri, Oct 7, 2016 at 8:16 AM, Sangjin Lee <sj...@apache.org> wrote:
> >
> > > Thanks Masatake!
> > >
> > > Today's the last day for this vote, and I'd like to ask you to try out
> > the
> > > RC and vote on this today. So far there has been no binding vote.
> Thanks
> > > again.
> > >
> > > Regards,
> > > Sangjin
> > >
> > > On Fri, Oct 7, 2016 at 6:45 AM, Masatake Iwasaki <
> > > iwasakims@oss.nttdata.co.jp> wrote:
> > >
> > > > +1(non-binding)
> > > >
> > > > * verified signature and md5.
> > > > * built with -Pnative on CentOS6 and OpenJDK7.
> > > > * built documentation and skimmed the contents.
> > > > * built rpms by bigtop and ran smoke-tests of hdfs, yarn and
> mapreduce
> > on
> > > > 3-node cluster.
> > > >
> > > > Thanks,
> > > > Masatake Iwasaki
> > > >
> > > > On 10/3/16 09:12, Sangjin Lee wrote:
> > > >
> > > >> Hi folks,
> > > >>
> > > >> I have pushed a new release candidate (R1) for the Apache Hadoop
> 2.6.5
> > > >> release (the next maintenance release in the 2.6.x release line).
> RC1
> > > >> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
> > > >>
> > > >> Below are the details of this release candidate:
> > > >>
> > > >> The RC is available for validation at:
> > > >> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
> > > >>
> > > >> The RC tag in git is release-2.6.5-RC1 and its git commit is
> > > >> e8c9fe0b4c252caf2ebf1464220599650f119997.
> > > >>
> > > >> The maven artifacts are staged via repository.apache.org at:
> > > >> https://repository.apache.org/content/repositories/
> > > orgapachehadoop-1050/.
> > > >>
> > > >> You can find my public key at
> > > >> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
> > > >>
> > > >> Please try the release and vote. The vote will run for the usual 5
> > > days. I
> > > >> would greatly appreciate your timely vote. Thanks!
> > > >>
> > > >> Regards,
> > > >> Sangjin
> > > >>
> > > >>
> > > >
> > >
> >
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Andrew Wang <an...@cloudera.com>]

Thanks to Chris and Sangjin for working on this release.

+1 binding

* Verified signatures
* Built from source tarball
* Started HDFS and did some basic ops

Thanks,
Andrew

On Fri, Oct 7, 2016 at 2:50 PM, Wangda Tan <wh...@gmail.com> wrote:

> Thanks Sangjin for cutting this release!
>
> +1 (Binding)
>
> - Downloaded binary tar ball and setup a single node cluster.
> - Submit a few applications and which can successfully run.
>
> Thanks,
> Wangda
>
>
> On Fri, Oct 7, 2016 at 10:33 AM, Zhihai Xu <zh...@gmail.com> wrote:
>
> > Thanks Sangjin for creating release 2.6.5 RC1.
> >
> > +1 (non-binding)
> >
> > * Downloaded and built from source
> > * Verified md5 checksums and signature
> > * Deployed a pseudo cluster
> > * verified basic HDFS operations and Pi job.
> > * Did a sanity check for RM and NM UI.
> >
> > Thanks
> > zhihai
> >
> > On Fri, Oct 7, 2016 at 8:16 AM, Sangjin Lee <sj...@apache.org> wrote:
> >
> > > Thanks Masatake!
> > >
> > > Today's the last day for this vote, and I'd like to ask you to try out
> > the
> > > RC and vote on this today. So far there has been no binding vote.
> Thanks
> > > again.
> > >
> > > Regards,
> > > Sangjin
> > >
> > > On Fri, Oct 7, 2016 at 6:45 AM, Masatake Iwasaki <
> > > iwasakims@oss.nttdata.co.jp> wrote:
> > >
> > > > +1(non-binding)
> > > >
> > > > * verified signature and md5.
> > > > * built with -Pnative on CentOS6 and OpenJDK7.
> > > > * built documentation and skimmed the contents.
> > > > * built rpms by bigtop and ran smoke-tests of hdfs, yarn and
> mapreduce
> > on
> > > > 3-node cluster.
> > > >
> > > > Thanks,
> > > > Masatake Iwasaki
> > > >
> > > > On 10/3/16 09:12, Sangjin Lee wrote:
> > > >
> > > >> Hi folks,
> > > >>
> > > >> I have pushed a new release candidate (R1) for the Apache Hadoop
> 2.6.5
> > > >> release (the next maintenance release in the 2.6.x release line).
> RC1
> > > >> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
> > > >>
> > > >> Below are the details of this release candidate:
> > > >>
> > > >> The RC is available for validation at:
> > > >> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
> > > >>
> > > >> The RC tag in git is release-2.6.5-RC1 and its git commit is
> > > >> e8c9fe0b4c252caf2ebf1464220599650f119997.
> > > >>
> > > >> The maven artifacts are staged via repository.apache.org at:
> > > >> https://repository.apache.org/content/repositories/
> > > orgapachehadoop-1050/.
> > > >>
> > > >> You can find my public key at
> > > >> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
> > > >>
> > > >> Please try the release and vote. The vote will run for the usual 5
> > > days. I
> > > >> would greatly appreciate your timely vote. Thanks!
> > > >>
> > > >> Regards,
> > > >> Sangjin
> > > >>
> > > >>
> > > >
> > >
> >
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Wangda Tan <wh...@gmail.com>]

Thanks Sangjin for cutting this release!

+1 (Binding)

- Downloaded binary tar ball and setup a single node cluster.
- Submit a few applications and which can successfully run.

Thanks,
Wangda


On Fri, Oct 7, 2016 at 10:33 AM, Zhihai Xu <zh...@gmail.com> wrote:

> Thanks Sangjin for creating release 2.6.5 RC1.
>
> +1 (non-binding)
>
> * Downloaded and built from source
> * Verified md5 checksums and signature
> * Deployed a pseudo cluster
> * verified basic HDFS operations and Pi job.
> * Did a sanity check for RM and NM UI.
>
> Thanks
> zhihai
>
> On Fri, Oct 7, 2016 at 8:16 AM, Sangjin Lee <sj...@apache.org> wrote:
>
> > Thanks Masatake!
> >
> > Today's the last day for this vote, and I'd like to ask you to try out
> the
> > RC and vote on this today. So far there has been no binding vote. Thanks
> > again.
> >
> > Regards,
> > Sangjin
> >
> > On Fri, Oct 7, 2016 at 6:45 AM, Masatake Iwasaki <
> > iwasakims@oss.nttdata.co.jp> wrote:
> >
> > > +1(non-binding)
> > >
> > > * verified signature and md5.
> > > * built with -Pnative on CentOS6 and OpenJDK7.
> > > * built documentation and skimmed the contents.
> > > * built rpms by bigtop and ran smoke-tests of hdfs, yarn and mapreduce
> on
> > > 3-node cluster.
> > >
> > > Thanks,
> > > Masatake Iwasaki
> > >
> > > On 10/3/16 09:12, Sangjin Lee wrote:
> > >
> > >> Hi folks,
> > >>
> > >> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> > >> release (the next maintenance release in the 2.6.x release line). RC1
> > >> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
> > >>
> > >> Below are the details of this release candidate:
> > >>
> > >> The RC is available for validation at:
> > >> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
> > >>
> > >> The RC tag in git is release-2.6.5-RC1 and its git commit is
> > >> e8c9fe0b4c252caf2ebf1464220599650f119997.
> > >>
> > >> The maven artifacts are staged via repository.apache.org at:
> > >> https://repository.apache.org/content/repositories/
> > orgapachehadoop-1050/.
> > >>
> > >> You can find my public key at
> > >> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
> > >>
> > >> Please try the release and vote. The vote will run for the usual 5
> > days. I
> > >> would greatly appreciate your timely vote. Thanks!
> > >>
> > >> Regards,
> > >> Sangjin
> > >>
> > >>
> > >
> >
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Wangda Tan <wh...@gmail.com>]

Thanks Sangjin for cutting this release!

+1 (Binding)

- Downloaded binary tar ball and setup a single node cluster.
- Submit a few applications and which can successfully run.

Thanks,
Wangda


On Fri, Oct 7, 2016 at 10:33 AM, Zhihai Xu <zh...@gmail.com> wrote:

> Thanks Sangjin for creating release 2.6.5 RC1.
>
> +1 (non-binding)
>
> * Downloaded and built from source
> * Verified md5 checksums and signature
> * Deployed a pseudo cluster
> * verified basic HDFS operations and Pi job.
> * Did a sanity check for RM and NM UI.
>
> Thanks
> zhihai
>
> On Fri, Oct 7, 2016 at 8:16 AM, Sangjin Lee <sj...@apache.org> wrote:
>
> > Thanks Masatake!
> >
> > Today's the last day for this vote, and I'd like to ask you to try out
> the
> > RC and vote on this today. So far there has been no binding vote. Thanks
> > again.
> >
> > Regards,
> > Sangjin
> >
> > On Fri, Oct 7, 2016 at 6:45 AM, Masatake Iwasaki <
> > iwasakims@oss.nttdata.co.jp> wrote:
> >
> > > +1(non-binding)
> > >
> > > * verified signature and md5.
> > > * built with -Pnative on CentOS6 and OpenJDK7.
> > > * built documentation and skimmed the contents.
> > > * built rpms by bigtop and ran smoke-tests of hdfs, yarn and mapreduce
> on
> > > 3-node cluster.
> > >
> > > Thanks,
> > > Masatake Iwasaki
> > >
> > > On 10/3/16 09:12, Sangjin Lee wrote:
> > >
> > >> Hi folks,
> > >>
> > >> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> > >> release (the next maintenance release in the 2.6.x release line). RC1
> > >> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
> > >>
> > >> Below are the details of this release candidate:
> > >>
> > >> The RC is available for validation at:
> > >> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
> > >>
> > >> The RC tag in git is release-2.6.5-RC1 and its git commit is
> > >> e8c9fe0b4c252caf2ebf1464220599650f119997.
> > >>
> > >> The maven artifacts are staged via repository.apache.org at:
> > >> https://repository.apache.org/content/repositories/
> > orgapachehadoop-1050/.
> > >>
> > >> You can find my public key at
> > >> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
> > >>
> > >> Please try the release and vote. The vote will run for the usual 5
> > days. I
> > >> would greatly appreciate your timely vote. Thanks!
> > >>
> > >> Regards,
> > >> Sangjin
> > >>
> > >>
> > >
> >
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Wangda Tan <wh...@gmail.com>]

Thanks Sangjin for cutting this release!

+1 (Binding)

- Downloaded binary tar ball and setup a single node cluster.
- Submit a few applications and which can successfully run.

Thanks,
Wangda


On Fri, Oct 7, 2016 at 10:33 AM, Zhihai Xu <zh...@gmail.com> wrote:

> Thanks Sangjin for creating release 2.6.5 RC1.
>
> +1 (non-binding)
>
> * Downloaded and built from source
> * Verified md5 checksums and signature
> * Deployed a pseudo cluster
> * verified basic HDFS operations and Pi job.
> * Did a sanity check for RM and NM UI.
>
> Thanks
> zhihai
>
> On Fri, Oct 7, 2016 at 8:16 AM, Sangjin Lee <sj...@apache.org> wrote:
>
> > Thanks Masatake!
> >
> > Today's the last day for this vote, and I'd like to ask you to try out
> the
> > RC and vote on this today. So far there has been no binding vote. Thanks
> > again.
> >
> > Regards,
> > Sangjin
> >
> > On Fri, Oct 7, 2016 at 6:45 AM, Masatake Iwasaki <
> > iwasakims@oss.nttdata.co.jp> wrote:
> >
> > > +1(non-binding)
> > >
> > > * verified signature and md5.
> > > * built with -Pnative on CentOS6 and OpenJDK7.
> > > * built documentation and skimmed the contents.
> > > * built rpms by bigtop and ran smoke-tests of hdfs, yarn and mapreduce
> on
> > > 3-node cluster.
> > >
> > > Thanks,
> > > Masatake Iwasaki
> > >
> > > On 10/3/16 09:12, Sangjin Lee wrote:
> > >
> > >> Hi folks,
> > >>
> > >> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> > >> release (the next maintenance release in the 2.6.x release line). RC1
> > >> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
> > >>
> > >> Below are the details of this release candidate:
> > >>
> > >> The RC is available for validation at:
> > >> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
> > >>
> > >> The RC tag in git is release-2.6.5-RC1 and its git commit is
> > >> e8c9fe0b4c252caf2ebf1464220599650f119997.
> > >>
> > >> The maven artifacts are staged via repository.apache.org at:
> > >> https://repository.apache.org/content/repositories/
> > orgapachehadoop-1050/.
> > >>
> > >> You can find my public key at
> > >> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
> > >>
> > >> Please try the release and vote. The vote will run for the usual 5
> > days. I
> > >> would greatly appreciate your timely vote. Thanks!
> > >>
> > >> Regards,
> > >> Sangjin
> > >>
> > >>
> > >
> >
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Wangda Tan <wh...@gmail.com>]

Thanks Sangjin for cutting this release!

+1 (Binding)

- Downloaded binary tar ball and setup a single node cluster.
- Submit a few applications and which can successfully run.

Thanks,
Wangda


On Fri, Oct 7, 2016 at 10:33 AM, Zhihai Xu <zh...@gmail.com> wrote:

> Thanks Sangjin for creating release 2.6.5 RC1.
>
> +1 (non-binding)
>
> * Downloaded and built from source
> * Verified md5 checksums and signature
> * Deployed a pseudo cluster
> * verified basic HDFS operations and Pi job.
> * Did a sanity check for RM and NM UI.
>
> Thanks
> zhihai
>
> On Fri, Oct 7, 2016 at 8:16 AM, Sangjin Lee <sj...@apache.org> wrote:
>
> > Thanks Masatake!
> >
> > Today's the last day for this vote, and I'd like to ask you to try out
> the
> > RC and vote on this today. So far there has been no binding vote. Thanks
> > again.
> >
> > Regards,
> > Sangjin
> >
> > On Fri, Oct 7, 2016 at 6:45 AM, Masatake Iwasaki <
> > iwasakims@oss.nttdata.co.jp> wrote:
> >
> > > +1(non-binding)
> > >
> > > * verified signature and md5.
> > > * built with -Pnative on CentOS6 and OpenJDK7.
> > > * built documentation and skimmed the contents.
> > > * built rpms by bigtop and ran smoke-tests of hdfs, yarn and mapreduce
> on
> > > 3-node cluster.
> > >
> > > Thanks,
> > > Masatake Iwasaki
> > >
> > > On 10/3/16 09:12, Sangjin Lee wrote:
> > >
> > >> Hi folks,
> > >>
> > >> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> > >> release (the next maintenance release in the 2.6.x release line). RC1
> > >> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
> > >>
> > >> Below are the details of this release candidate:
> > >>
> > >> The RC is available for validation at:
> > >> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
> > >>
> > >> The RC tag in git is release-2.6.5-RC1 and its git commit is
> > >> e8c9fe0b4c252caf2ebf1464220599650f119997.
> > >>
> > >> The maven artifacts are staged via repository.apache.org at:
> > >> https://repository.apache.org/content/repositories/
> > orgapachehadoop-1050/.
> > >>
> > >> You can find my public key at
> > >> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
> > >>
> > >> Please try the release and vote. The vote will run for the usual 5
> > days. I
> > >> would greatly appreciate your timely vote. Thanks!
> > >>
> > >> Regards,
> > >> Sangjin
> > >>
> > >>
> > >
> >
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Zhihai Xu <zh...@gmail.com>]

Thanks Sangjin for creating release 2.6.5 RC1.

+1 (non-binding)

* Downloaded and built from source
* Verified md5 checksums and signature
* Deployed a pseudo cluster
* verified basic HDFS operations and Pi job.
* Did a sanity check for RM and NM UI.

Thanks
zhihai

On Fri, Oct 7, 2016 at 8:16 AM, Sangjin Lee <sj...@apache.org> wrote:

> Thanks Masatake!
>
> Today's the last day for this vote, and I'd like to ask you to try out the
> RC and vote on this today. So far there has been no binding vote. Thanks
> again.
>
> Regards,
> Sangjin
>
> On Fri, Oct 7, 2016 at 6:45 AM, Masatake Iwasaki <
> iwasakims@oss.nttdata.co.jp> wrote:
>
> > +1(non-binding)
> >
> > * verified signature and md5.
> > * built with -Pnative on CentOS6 and OpenJDK7.
> > * built documentation and skimmed the contents.
> > * built rpms by bigtop and ran smoke-tests of hdfs, yarn and mapreduce on
> > 3-node cluster.
> >
> > Thanks,
> > Masatake Iwasaki
> >
> > On 10/3/16 09:12, Sangjin Lee wrote:
> >
> >> Hi folks,
> >>
> >> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> >> release (the next maintenance release in the 2.6.x release line). RC1
> >> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
> >>
> >> Below are the details of this release candidate:
> >>
> >> The RC is available for validation at:
> >> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
> >>
> >> The RC tag in git is release-2.6.5-RC1 and its git commit is
> >> e8c9fe0b4c252caf2ebf1464220599650f119997.
> >>
> >> The maven artifacts are staged via repository.apache.org at:
> >> https://repository.apache.org/content/repositories/
> orgapachehadoop-1050/.
> >>
> >> You can find my public key at
> >> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
> >>
> >> Please try the release and vote. The vote will run for the usual 5
> days. I
> >> would greatly appreciate your timely vote. Thanks!
> >>
> >> Regards,
> >> Sangjin
> >>
> >>
> >
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Zhihai Xu <zh...@gmail.com>]

Thanks Sangjin for creating release 2.6.5 RC1.

+1 (non-binding)

* Downloaded and built from source
* Verified md5 checksums and signature
* Deployed a pseudo cluster
* verified basic HDFS operations and Pi job.
* Did a sanity check for RM and NM UI.

Thanks
zhihai

On Fri, Oct 7, 2016 at 8:16 AM, Sangjin Lee <sj...@apache.org> wrote:

> Thanks Masatake!
>
> Today's the last day for this vote, and I'd like to ask you to try out the
> RC and vote on this today. So far there has been no binding vote. Thanks
> again.
>
> Regards,
> Sangjin
>
> On Fri, Oct 7, 2016 at 6:45 AM, Masatake Iwasaki <
> iwasakims@oss.nttdata.co.jp> wrote:
>
> > +1(non-binding)
> >
> > * verified signature and md5.
> > * built with -Pnative on CentOS6 and OpenJDK7.
> > * built documentation and skimmed the contents.
> > * built rpms by bigtop and ran smoke-tests of hdfs, yarn and mapreduce on
> > 3-node cluster.
> >
> > Thanks,
> > Masatake Iwasaki
> >
> > On 10/3/16 09:12, Sangjin Lee wrote:
> >
> >> Hi folks,
> >>
> >> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> >> release (the next maintenance release in the 2.6.x release line). RC1
> >> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
> >>
> >> Below are the details of this release candidate:
> >>
> >> The RC is available for validation at:
> >> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
> >>
> >> The RC tag in git is release-2.6.5-RC1 and its git commit is
> >> e8c9fe0b4c252caf2ebf1464220599650f119997.
> >>
> >> The maven artifacts are staged via repository.apache.org at:
> >> https://repository.apache.org/content/repositories/
> orgapachehadoop-1050/.
> >>
> >> You can find my public key at
> >> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
> >>
> >> Please try the release and vote. The vote will run for the usual 5
> days. I
> >> would greatly appreciate your timely vote. Thanks!
> >>
> >> Regards,
> >> Sangjin
> >>
> >>
> >
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Zhihai Xu <zh...@gmail.com>]

Thanks Sangjin for creating release 2.6.5 RC1.

+1 (non-binding)

* Downloaded and built from source
* Verified md5 checksums and signature
* Deployed a pseudo cluster
* verified basic HDFS operations and Pi job.
* Did a sanity check for RM and NM UI.

Thanks
zhihai

On Fri, Oct 7, 2016 at 8:16 AM, Sangjin Lee <sj...@apache.org> wrote:

> Thanks Masatake!
>
> Today's the last day for this vote, and I'd like to ask you to try out the
> RC and vote on this today. So far there has been no binding vote. Thanks
> again.
>
> Regards,
> Sangjin
>
> On Fri, Oct 7, 2016 at 6:45 AM, Masatake Iwasaki <
> iwasakims@oss.nttdata.co.jp> wrote:
>
> > +1(non-binding)
> >
> > * verified signature and md5.
> > * built with -Pnative on CentOS6 and OpenJDK7.
> > * built documentation and skimmed the contents.
> > * built rpms by bigtop and ran smoke-tests of hdfs, yarn and mapreduce on
> > 3-node cluster.
> >
> > Thanks,
> > Masatake Iwasaki
> >
> > On 10/3/16 09:12, Sangjin Lee wrote:
> >
> >> Hi folks,
> >>
> >> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> >> release (the next maintenance release in the 2.6.x release line). RC1
> >> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
> >>
> >> Below are the details of this release candidate:
> >>
> >> The RC is available for validation at:
> >> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
> >>
> >> The RC tag in git is release-2.6.5-RC1 and its git commit is
> >> e8c9fe0b4c252caf2ebf1464220599650f119997.
> >>
> >> The maven artifacts are staged via repository.apache.org at:
> >> https://repository.apache.org/content/repositories/
> orgapachehadoop-1050/.
> >>
> >> You can find my public key at
> >> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
> >>
> >> Please try the release and vote. The vote will run for the usual 5
> days. I
> >> would greatly appreciate your timely vote. Thanks!
> >>
> >> Regards,
> >> Sangjin
> >>
> >>
> >
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Zhihai Xu <zh...@gmail.com>]

Thanks Sangjin for creating release 2.6.5 RC1.

+1 (non-binding)

* Downloaded and built from source
* Verified md5 checksums and signature
* Deployed a pseudo cluster
* verified basic HDFS operations and Pi job.
* Did a sanity check for RM and NM UI.

Thanks
zhihai

On Fri, Oct 7, 2016 at 8:16 AM, Sangjin Lee <sj...@apache.org> wrote:

> Thanks Masatake!
>
> Today's the last day for this vote, and I'd like to ask you to try out the
> RC and vote on this today. So far there has been no binding vote. Thanks
> again.
>
> Regards,
> Sangjin
>
> On Fri, Oct 7, 2016 at 6:45 AM, Masatake Iwasaki <
> iwasakims@oss.nttdata.co.jp> wrote:
>
> > +1(non-binding)
> >
> > * verified signature and md5.
> > * built with -Pnative on CentOS6 and OpenJDK7.
> > * built documentation and skimmed the contents.
> > * built rpms by bigtop and ran smoke-tests of hdfs, yarn and mapreduce on
> > 3-node cluster.
> >
> > Thanks,
> > Masatake Iwasaki
> >
> > On 10/3/16 09:12, Sangjin Lee wrote:
> >
> >> Hi folks,
> >>
> >> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> >> release (the next maintenance release in the 2.6.x release line). RC1
> >> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
> >>
> >> Below are the details of this release candidate:
> >>
> >> The RC is available for validation at:
> >> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
> >>
> >> The RC tag in git is release-2.6.5-RC1 and its git commit is
> >> e8c9fe0b4c252caf2ebf1464220599650f119997.
> >>
> >> The maven artifacts are staged via repository.apache.org at:
> >> https://repository.apache.org/content/repositories/
> orgapachehadoop-1050/.
> >>
> >> You can find my public key at
> >> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
> >>
> >> Please try the release and vote. The vote will run for the usual 5
> days. I
> >> would greatly appreciate your timely vote. Thanks!
> >>
> >> Regards,
> >> Sangjin
> >>
> >>
> >
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Sangjin Lee <sj...@apache.org>]

Thanks Masatake!

Today's the last day for this vote, and I'd like to ask you to try out the
RC and vote on this today. So far there has been no binding vote. Thanks
again.

Regards,
Sangjin

On Fri, Oct 7, 2016 at 6:45 AM, Masatake Iwasaki <
iwasakims@oss.nttdata.co.jp> wrote:

> +1(non-binding)
>
> * verified signature and md5.
> * built with -Pnative on CentOS6 and OpenJDK7.
> * built documentation and skimmed the contents.
> * built rpms by bigtop and ran smoke-tests of hdfs, yarn and mapreduce on
> 3-node cluster.
>
> Thanks,
> Masatake Iwasaki
>
> On 10/3/16 09:12, Sangjin Lee wrote:
>
>> Hi folks,
>>
>> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
>> release (the next maintenance release in the 2.6.x release line). RC1
>> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
>>
>> Below are the details of this release candidate:
>>
>> The RC is available for validation at:
>> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
>>
>> The RC tag in git is release-2.6.5-RC1 and its git commit is
>> e8c9fe0b4c252caf2ebf1464220599650f119997.
>>
>> The maven artifacts are staged via repository.apache.org at:
>> https://repository.apache.org/content/repositories/orgapachehadoop-1050/.
>>
>> You can find my public key at
>> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
>>
>> Please try the release and vote. The vote will run for the usual 5 days. I
>> would greatly appreciate your timely vote. Thanks!
>>
>> Regards,
>> Sangjin
>>
>>
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Sangjin Lee <sj...@apache.org>]

Thanks Masatake!

Today's the last day for this vote, and I'd like to ask you to try out the
RC and vote on this today. So far there has been no binding vote. Thanks
again.

Regards,
Sangjin

On Fri, Oct 7, 2016 at 6:45 AM, Masatake Iwasaki <
iwasakims@oss.nttdata.co.jp> wrote:

> +1(non-binding)
>
> * verified signature and md5.
> * built with -Pnative on CentOS6 and OpenJDK7.
> * built documentation and skimmed the contents.
> * built rpms by bigtop and ran smoke-tests of hdfs, yarn and mapreduce on
> 3-node cluster.
>
> Thanks,
> Masatake Iwasaki
>
> On 10/3/16 09:12, Sangjin Lee wrote:
>
>> Hi folks,
>>
>> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
>> release (the next maintenance release in the 2.6.x release line). RC1
>> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
>>
>> Below are the details of this release candidate:
>>
>> The RC is available for validation at:
>> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
>>
>> The RC tag in git is release-2.6.5-RC1 and its git commit is
>> e8c9fe0b4c252caf2ebf1464220599650f119997.
>>
>> The maven artifacts are staged via repository.apache.org at:
>> https://repository.apache.org/content/repositories/orgapachehadoop-1050/.
>>
>> You can find my public key at
>> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
>>
>> Please try the release and vote. The vote will run for the usual 5 days. I
>> would greatly appreciate your timely vote. Thanks!
>>
>> Regards,
>> Sangjin
>>
>>
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Sangjin Lee <sj...@apache.org>]

Thanks Masatake!

Today's the last day for this vote, and I'd like to ask you to try out the
RC and vote on this today. So far there has been no binding vote. Thanks
again.

Regards,
Sangjin

On Fri, Oct 7, 2016 at 6:45 AM, Masatake Iwasaki <
iwasakims@oss.nttdata.co.jp> wrote:

> +1(non-binding)
>
> * verified signature and md5.
> * built with -Pnative on CentOS6 and OpenJDK7.
> * built documentation and skimmed the contents.
> * built rpms by bigtop and ran smoke-tests of hdfs, yarn and mapreduce on
> 3-node cluster.
>
> Thanks,
> Masatake Iwasaki
>
> On 10/3/16 09:12, Sangjin Lee wrote:
>
>> Hi folks,
>>
>> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
>> release (the next maintenance release in the 2.6.x release line). RC1
>> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
>>
>> Below are the details of this release candidate:
>>
>> The RC is available for validation at:
>> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
>>
>> The RC tag in git is release-2.6.5-RC1 and its git commit is
>> e8c9fe0b4c252caf2ebf1464220599650f119997.
>>
>> The maven artifacts are staged via repository.apache.org at:
>> https://repository.apache.org/content/repositories/orgapachehadoop-1050/.
>>
>> You can find my public key at
>> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
>>
>> Please try the release and vote. The vote will run for the usual 5 days. I
>> would greatly appreciate your timely vote. Thanks!
>>
>> Regards,
>> Sangjin
>>
>>
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Sangjin Lee <sj...@apache.org>]

Thanks Masatake!

Today's the last day for this vote, and I'd like to ask you to try out the
RC and vote on this today. So far there has been no binding vote. Thanks
again.

Regards,
Sangjin

On Fri, Oct 7, 2016 at 6:45 AM, Masatake Iwasaki <
iwasakims@oss.nttdata.co.jp> wrote:

> +1(non-binding)
>
> * verified signature and md5.
> * built with -Pnative on CentOS6 and OpenJDK7.
> * built documentation and skimmed the contents.
> * built rpms by bigtop and ran smoke-tests of hdfs, yarn and mapreduce on
> 3-node cluster.
>
> Thanks,
> Masatake Iwasaki
>
> On 10/3/16 09:12, Sangjin Lee wrote:
>
>> Hi folks,
>>
>> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
>> release (the next maintenance release in the 2.6.x release line). RC1
>> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
>>
>> Below are the details of this release candidate:
>>
>> The RC is available for validation at:
>> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
>>
>> The RC tag in git is release-2.6.5-RC1 and its git commit is
>> e8c9fe0b4c252caf2ebf1464220599650f119997.
>>
>> The maven artifacts are staged via repository.apache.org at:
>> https://repository.apache.org/content/repositories/orgapachehadoop-1050/.
>>
>> You can find my public key at
>> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
>>
>> Please try the release and vote. The vote will run for the usual 5 days. I
>> would greatly appreciate your timely vote. Thanks!
>>
>> Regards,
>> Sangjin
>>
>>
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Masatake Iwasaki <iw...@oss.nttdata.co.jp>]

+1(non-binding)

* verified signature and md5.
* built with -Pnative on CentOS6 and OpenJDK7.
* built documentation and skimmed the contents.
* built rpms by bigtop and ran smoke-tests of hdfs, yarn and mapreduce 
on 3-node cluster.

Thanks,
Masatake Iwasaki

On 10/3/16 09:12, Sangjin Lee wrote:
> Hi folks,
>
> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> release (the next maintenance release in the 2.6.x release line). RC1
> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
>
> Below are the details of this release candidate:
>
> The RC is available for validation at:
> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
>
> The RC tag in git is release-2.6.5-RC1 and its git commit is
> e8c9fe0b4c252caf2ebf1464220599650f119997.
>
> The maven artifacts are staged via repository.apache.org at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1050/.
>
> You can find my public key at
> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
>
> Please try the release and vote. The vote will run for the usual 5 days. I
> would greatly appreciate your timely vote. Thanks!
>
> Regards,
> Sangjin
>


---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Akira Ajisaka <aj...@oss.nttdata.co.jp>]

Hi Sangjin,

When using binary tarball, I'm seeing
"2016-09-27T18:26Z by sjlee from branch-2.6.5" in Web UI.
Can we rename it?

AFAIK, hadoop releases were built by hortonmu in 2014 and was renamed to 
jenkins.

* 
http://mail-archives.apache.org/mod_mbox/hadoop-common-dev/201401.mbox/%3CCAJs-t7NiJAJceO=6L8vr1uOr-Es=Z1y-UfkQXr8Ya5hq3-D23Q@mail.gmail.com%3E
* https://issues.apache.org/jira/browse/HADOOP-10313

Regards,
Akira

On 10/3/16 09:12, Sangjin Lee wrote:
> Hi folks,
>
> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> release (the next maintenance release in the 2.6.x release line). RC1
> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
>
> Below are the details of this release candidate:
>
> The RC is available for validation at:
> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
>
> The RC tag in git is release-2.6.5-RC1 and its git commit is
> e8c9fe0b4c252caf2ebf1464220599650f119997.
>
> The maven artifacts are staged via repository.apache.org at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1050/.
>
> You can find my public key at
> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
>
> Please try the release and vote. The vote will run for the usual 5 days. I
> would greatly appreciate your timely vote. Thanks!
>
> Regards,
> Sangjin
>


---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Masatake Iwasaki <iw...@oss.nttdata.co.jp>]

+1(non-binding)

* verified signature and md5.
* built with -Pnative on CentOS6 and OpenJDK7.
* built documentation and skimmed the contents.
* built rpms by bigtop and ran smoke-tests of hdfs, yarn and mapreduce 
on 3-node cluster.

Thanks,
Masatake Iwasaki

On 10/3/16 09:12, Sangjin Lee wrote:
> Hi folks,
>
> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> release (the next maintenance release in the 2.6.x release line). RC1
> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
>
> Below are the details of this release candidate:
>
> The RC is available for validation at:
> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
>
> The RC tag in git is release-2.6.5-RC1 and its git commit is
> e8c9fe0b4c252caf2ebf1464220599650f119997.
>
> The maven artifacts are staged via repository.apache.org at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1050/.
>
> You can find my public key at
> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
>
> Please try the release and vote. The vote will run for the usual 5 days. I
> would greatly appreciate your timely vote. Thanks!
>
> Regards,
> Sangjin
>


---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Brahma Reddy Battula <br...@apache.org>]

Thanks Sangjin!


+1 ( non- binding)


--Downloaded the source and complied

--Installed HA cluster

--Verified basic fsshell commands

--Ran pi,terasort Slive jobs, all works fine.



--Brahma Reddy Battula

On Mon, Oct 3, 2016 at 5:42 AM, Sangjin Lee <sj...@apache.org> wrote:

> Hi folks,
>
> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> release (the next maintenance release in the 2.6.x release line). RC1
> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
>
> Below are the details of this release candidate:
>
> The RC is available for validation at:
> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
>
> The RC tag in git is release-2.6.5-RC1 and its git commit is
> e8c9fe0b4c252caf2ebf1464220599650f119997.
>
> The maven artifacts are staged via repository.apache.org at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1050/.
>
> You can find my public key at
> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
>
> Please try the release and vote. The vote will run for the usual 5 days. I
> would greatly appreciate your timely vote. Thanks!
>
> Regards,
> Sangjin
>



-- 



--Brahma Reddy Battula

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Rohith Sharma K S <ks...@gmail.com>]

+1 ( non- binding)

--Downloaded source and built from it.
--Installed 3 node cluster with HA deployed. 
—Ran sample MR jobs and tested with basics operations.
— Integrated JCarder tool to find any potential deadlock cycles. And did  not observe any potential cycles.

Thanks & Regards
Rohith Sharma K S

> On Oct 3, 2016, at 5:42 AM, Sangjin Lee <sj...@apache.org> wrote:
> 
> Hi folks,
> 
> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> release (the next maintenance release in the 2.6.x release line). RC1
> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
> 
> Below are the details of this release candidate:
> 
> The RC is available for validation at:
> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
> 
> The RC tag in git is release-2.6.5-RC1 and its git commit is
> e8c9fe0b4c252caf2ebf1464220599650f119997.
> 
> The maven artifacts are staged via repository.apache.org at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1050/.
> 
> You can find my public key at
> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
> 
> Please try the release and vote. The vote will run for the usual 5 days. I
> would greatly appreciate your timely vote. Thanks!
> 
> Regards,
> Sangjin


---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Jason Lowe <jl...@yahoo-inc.com.INVALID>]

+1 (binding)
- Verified signatures and digests- Built native from source- Deployed to a single-node cluster and ran some sample jobs
Jason
 

    On Sunday, October 2, 2016 7:13 PM, Sangjin Lee <sj...@apache.org> wrote:
 

 Hi folks,

I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
release (the next maintenance release in the 2.6.x release line). RC1
contains fixes to CHANGES.txt, and is otherwise identical to RC0.

Below are the details of this release candidate:

The RC is available for validation at:
http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.

The RC tag in git is release-2.6.5-RC1 and its git commit is
e8c9fe0b4c252caf2ebf1464220599650f119997.

The maven artifacts are staged via repository.apache.org at:
https://repository.apache.org/content/repositories/orgapachehadoop-1050/.

You can find my public key at
http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.

Please try the release and vote. The vote will run for the usual 5 days. I
would greatly appreciate your timely vote. Thanks!

Regards,
Sangjin


   

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[John Zhuge <jz...@cloudera.com>]

+1 (non-binding)

- Verified checksums and signatures of the tarballs
- Built source with Java 1.7.0_111 on Centos 6.6 with native
- Verified licenses and notices using verify-license-notice.sh
- Deployed a pseudo cluster

- Ran basic dfs, distcp, ACL commands
- Ran MapReduce wordcount example
- Ran balancer


Thanks,
John

John Zhuge
Software Engineer, Cloudera

On Sun, Oct 2, 2016 at 5:12 PM, Sangjin Lee <sj...@apache.org> wrote:

> Hi folks,
>
> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> release (the next maintenance release in the 2.6.x release line). RC1
> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
>
> Below are the details of this release candidate:
>
> The RC is available for validation at:
> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
>
> The RC tag in git is release-2.6.5-RC1 and its git commit is
> e8c9fe0b4c252caf2ebf1464220599650f119997.
>
> The maven artifacts are staged via repository.apache.org at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1050/.
>
> You can find my public key at
> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
>
> Please try the release and vote. The vote will run for the usual 5 days. I
> would greatly appreciate your timely vote. Thanks!
>
> Regards,
> Sangjin
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Rohith Sharma K S <ks...@gmail.com>]

+1 ( non- binding)

--Downloaded source and built from it.
--Installed 3 node cluster with HA deployed. 
—Ran sample MR jobs and tested with basics operations.
— Integrated JCarder tool to find any potential deadlock cycles. And did  not observe any potential cycles.

Thanks & Regards
Rohith Sharma K S

> On Oct 3, 2016, at 5:42 AM, Sangjin Lee <sj...@apache.org> wrote:
> 
> Hi folks,
> 
> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> release (the next maintenance release in the 2.6.x release line). RC1
> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
> 
> Below are the details of this release candidate:
> 
> The RC is available for validation at:
> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
> 
> The RC tag in git is release-2.6.5-RC1 and its git commit is
> e8c9fe0b4c252caf2ebf1464220599650f119997.
> 
> The maven artifacts are staged via repository.apache.org at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1050/.
> 
> You can find my public key at
> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
> 
> Please try the release and vote. The vote will run for the usual 5 days. I
> would greatly appreciate your timely vote. Thanks!
> 
> Regards,
> Sangjin


---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Jason Lowe <jl...@yahoo-inc.com.INVALID>]

+1 (binding)
- Verified signatures and digests- Built native from source- Deployed to a single-node cluster and ran some sample jobs
Jason
 

    On Sunday, October 2, 2016 7:13 PM, Sangjin Lee <sj...@apache.org> wrote:
 

 Hi folks,

I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
release (the next maintenance release in the 2.6.x release line). RC1
contains fixes to CHANGES.txt, and is otherwise identical to RC0.

Below are the details of this release candidate:

The RC is available for validation at:
http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.

The RC tag in git is release-2.6.5-RC1 and its git commit is
e8c9fe0b4c252caf2ebf1464220599650f119997.

The maven artifacts are staged via repository.apache.org at:
https://repository.apache.org/content/repositories/orgapachehadoop-1050/.

You can find my public key at
http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.

Please try the release and vote. The vote will run for the usual 5 days. I
would greatly appreciate your timely vote. Thanks!

Regards,
Sangjin


   

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Chris Trezzo <ct...@gmail.com>]

+1 (non-binding)

Thanks for cutting another release candidate Sangjin!

1. Diff'ed the CHANGES-*.txt files against the branch-2.6.5 git log and
verified the set of listed issues matches.
2. Verified md5 checksums and signature on src and binary tar.gz.
3. Built from source.
4. Started up a pseudo distributed cluster.
5. Successfully ran a PI job.
6. Ran the balancer.
7. Inspected UI for RM, NN, JobHistory.

On Sun, Oct 2, 2016 at 5:12 PM, Sangjin Lee <sj...@apache.org> wrote:

> Hi folks,
>
> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> release (the next maintenance release in the 2.6.x release line). RC1
> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
>
> Below are the details of this release candidate:
>
> The RC is available for validation at:
> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
>
> The RC tag in git is release-2.6.5-RC1 and its git commit is
> e8c9fe0b4c252caf2ebf1464220599650f119997.
>
> The maven artifacts are staged via repository.apache.org at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1050/.
>
> You can find my public key at
> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
>
> Please try the release and vote. The vote will run for the usual 5 days. I
> would greatly appreciate your timely vote. Thanks!
>
> Regards,
> Sangjin
>

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Rohith Sharma K S <ks...@gmail.com>]

+1 ( non- binding)

--Downloaded source and built from it.
--Installed 3 node cluster with HA deployed. 
—Ran sample MR jobs and tested with basics operations.
— Integrated JCarder tool to find any potential deadlock cycles. And did  not observe any potential cycles.

Thanks & Regards
Rohith Sharma K S

> On Oct 3, 2016, at 5:42 AM, Sangjin Lee <sj...@apache.org> wrote:
> 
> Hi folks,
> 
> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> release (the next maintenance release in the 2.6.x release line). RC1
> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
> 
> Below are the details of this release candidate:
> 
> The RC is available for validation at:
> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
> 
> The RC tag in git is release-2.6.5-RC1 and its git commit is
> e8c9fe0b4c252caf2ebf1464220599650f119997.
> 
> The maven artifacts are staged via repository.apache.org at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1050/.
> 
> You can find my public key at
> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
> 
> Please try the release and vote. The vote will run for the usual 5 days. I
> would greatly appreciate your timely vote. Thanks!
> 
> Regards,
> Sangjin


---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Akira Ajisaka <aj...@oss.nttdata.co.jp>]

Hi Sangjin,

When using binary tarball, I'm seeing
"2016-09-27T18:26Z by sjlee from branch-2.6.5" in Web UI.
Can we rename it?

AFAIK, hadoop releases were built by hortonmu in 2014 and was renamed to 
jenkins.

* 
http://mail-archives.apache.org/mod_mbox/hadoop-common-dev/201401.mbox/%3CCAJs-t7NiJAJceO=6L8vr1uOr-Es=Z1y-UfkQXr8Ya5hq3-D23Q@mail.gmail.com%3E
* https://issues.apache.org/jira/browse/HADOOP-10313

Regards,
Akira

On 10/3/16 09:12, Sangjin Lee wrote:
> Hi folks,
>
> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> release (the next maintenance release in the 2.6.x release line). RC1
> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
>
> Below are the details of this release candidate:
>
> The RC is available for validation at:
> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
>
> The RC tag in git is release-2.6.5-RC1 and its git commit is
> e8c9fe0b4c252caf2ebf1464220599650f119997.
>
> The maven artifacts are staged via repository.apache.org at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1050/.
>
> You can find my public key at
> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
>
> Please try the release and vote. The vote will run for the usual 5 days. I
> would greatly appreciate your timely vote. Thanks!
>
> Regards,
> Sangjin
>


---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Masatake Iwasaki <iw...@oss.nttdata.co.jp>]

+1(non-binding)

* verified signature and md5.
* built with -Pnative on CentOS6 and OpenJDK7.
* built documentation and skimmed the contents.
* built rpms by bigtop and ran smoke-tests of hdfs, yarn and mapreduce 
on 3-node cluster.

Thanks,
Masatake Iwasaki

On 10/3/16 09:12, Sangjin Lee wrote:
> Hi folks,
>
> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> release (the next maintenance release in the 2.6.x release line). RC1
> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
>
> Below are the details of this release candidate:
>
> The RC is available for validation at:
> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
>
> The RC tag in git is release-2.6.5-RC1 and its git commit is
> e8c9fe0b4c252caf2ebf1464220599650f119997.
>
> The maven artifacts are staged via repository.apache.org at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1050/.
>
> You can find my public key at
> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
>
> Please try the release and vote. The vote will run for the usual 5 days. I
> would greatly appreciate your timely vote. Thanks!
>
> Regards,
> Sangjin
>


---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Brahma Reddy Battula <br...@apache.org>]

Thanks Sangjin!


+1 ( non- binding)


--Downloaded the source and complied

--Installed HA cluster

--Verified basic fsshell commands

--Ran pi,terasort Slive jobs, all works fine.



--Brahma Reddy Battula

On Mon, Oct 3, 2016 at 5:42 AM, Sangjin Lee <sj...@apache.org> wrote:

> Hi folks,
>
> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> release (the next maintenance release in the 2.6.x release line). RC1
> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
>
> Below are the details of this release candidate:
>
> The RC is available for validation at:
> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
>
> The RC tag in git is release-2.6.5-RC1 and its git commit is
> e8c9fe0b4c252caf2ebf1464220599650f119997.
>
> The maven artifacts are staged via repository.apache.org at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1050/.
>
> You can find my public key at
> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
>
> Please try the release and vote. The vote will run for the usual 5 days. I
> would greatly appreciate your timely vote. Thanks!
>
> Regards,
> Sangjin
>



-- 



--Brahma Reddy Battula

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Masatake Iwasaki <iw...@oss.nttdata.co.jp>]

+1(non-binding)

* verified signature and md5.
* built with -Pnative on CentOS6 and OpenJDK7.
* built documentation and skimmed the contents.
* built rpms by bigtop and ran smoke-tests of hdfs, yarn and mapreduce 
on 3-node cluster.

Thanks,
Masatake Iwasaki

On 10/3/16 09:12, Sangjin Lee wrote:
> Hi folks,
>
> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> release (the next maintenance release in the 2.6.x release line). RC1
> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
>
> Below are the details of this release candidate:
>
> The RC is available for validation at:
> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
>
> The RC tag in git is release-2.6.5-RC1 and its git commit is
> e8c9fe0b4c252caf2ebf1464220599650f119997.
>
> The maven artifacts are staged via repository.apache.org at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1050/.
>
> You can find my public key at
> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
>
> Please try the release and vote. The vote will run for the usual 5 days. I
> would greatly appreciate your timely vote. Thanks!
>
> Regards,
> Sangjin
>


---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC1)

[Chris Trezzo <ct...@gmail.com>]

+1 (non-binding)

Thanks for cutting another release candidate Sangjin!

1. Diff'ed the CHANGES-*.txt files against the branch-2.6.5 git log and
verified the set of listed issues matches.
2. Verified md5 checksums and signature on src and binary tar.gz.
3. Built from source.
4. Started up a pseudo distributed cluster.
5. Successfully ran a PI job.
6. Ran the balancer.
7. Inspected UI for RM, NN, JobHistory.

On Sun, Oct 2, 2016 at 5:12 PM, Sangjin Lee <sj...@apache.org> wrote:

> Hi folks,
>
> I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
> release (the next maintenance release in the 2.6.x release line). RC1
> contains fixes to CHANGES.txt, and is otherwise identical to RC0.
>
> Below are the details of this release candidate:
>
> The RC is available for validation at:
> http://home.apache.org/~sjlee/hadoop-2.6.5-RC1/.
>
> The RC tag in git is release-2.6.5-RC1 and its git commit is
> e8c9fe0b4c252caf2ebf1464220599650f119997.
>
> The maven artifacts are staged via repository.apache.org at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1050/.
>
> You can find my public key at
> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS.
>
> Please try the release and vote. The vote will run for the usual 5 days. I
> would greatly appreciate your timely vote. Thanks!
>
> Regards,
> Sangjin
>