You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by Konstantin Shvachko <sh...@gmail.com> on 2017/07/29 23:29:10 UTC

[VOTE] Release Apache Hadoop 2.7.4 (RC0)

Hi everybody,

Here is the next release of Apache Hadoop 2.7 line. The previous stable
release 2.7.3 was available since 25 August, 2016.
Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
critical bug fixes and major optimizations. See more details in Release
Note:
http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html

The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/

Please give it a try and vote on this thread. The vote will run for 5 days
ending 08/04/2017.

Please note that my up to date public key are available from:
https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
Please don't forget to refresh the page if you've been there recently.
There are other place on Apache sites, which may contain my outdated key.

Thanks,
--Konstantin

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Konstantin Shvachko <sh...@gmail.com>.
Hi Wei-Chi,

There is bunch of performance jiras in Hadoop.
This one is not marked as blocker and seems to be hard to reproduce.
And I see that you are still discussing the problem and the solution with
Daryn in the jira.
I don't think it should block the release.
If this or anything else will prove to be a serious problem we can follow
up with a maintenance release containing hotfixes only.

Thanks,
--Konst

On Fri, Aug 4, 2017 at 9:24 AM, Wei-Chiu Chuang <we...@cloudera.com>
wrote:

> Hi,
> I'm sorry coming to this vote late.
> Daryn mentioned in HDFS-12136
> <https://issues.apache.org/jira/browse/HDFS-12136> that HDFS-11160
> <https://issues.apache.org/jira/browse/HDFS-11160> has a performance
> regression at DataNode due to the way it locks dataset lock.
>
> HDFS-11160 is in Hadoop 2.7.4. Would it be critical enough to warrant a
> stop for release?
>
> I myself can't reproduce the performance regression (assuming it only
> occurs under extreme workload). Would Daryn or other Yahoo folks comment?
>
> On Thu, Aug 3, 2017 at 10:31 PM, Akira Ajisaka <aa...@apache.org>
> wrote:
>
>> +1 (binding)
>>
>> - Verified the checksum and the signature of the source tarball
>> - Built from source with CentOS 7.2 and OpenJDK 1.8.0_141
>> - Built Hive 2.1.0/2.3.0 and Tez 0.8.5/0.9.0 with Hadoop 2.7.4 artifacts
>> - Built single node cluster and ran some Hive on Tez queries successfully
>>
>> Regards,
>> Akira
>>
>>
>> On 2017/08/04 0:25, Kuhu Shukla wrote:
>>
>>> +1 (non-binding)
>>>
>>> 1. Verified signatures and digests.
>>> 2. Built source.
>>> 3. Installed on a pseudo-distributed cluster.
>>> 4. Ran sample MR jobs and Tez example jobs like orderedwordcount
>>> successfully.
>>>
>>> Thank you Konstantin and others for this release.
>>>
>>> Regards,
>>> Kuhu
>>>
>>>
>>>
>>> On Thursday, August 3, 2017, 7:19:07 AM CDT, Sunil G <su...@apache.org>
>>> wrote:
>>>
>>>
>>> Thanks Konstantin
>>>
>>> +1 (binding)
>>>
>>> 1. Build tar ball from source package
>>> 2. Ran basic MR jobs and verified UI.
>>> 3. Enabled node labels and ran sleep job. Works fine.
>>> 4. Verified CLI commands related to node labels and its working fine.
>>> 5. RM WorkPreserving restart cases are also verified, and looks fine
>>>
>>> Thanks
>>> Sunil
>>>
>>>
>>>
>>> On Sun, Jul 30, 2017 at 4:59 AM Konstantin Shvachko <
>>> shv.hadoop@gmail.com>
>>> wrote:
>>>
>>> Hi everybody,
>>>>
>>>> Here is the next release of Apache Hadoop 2.7 line. The previous stable
>>>> release 2.7.3 was available since 25 August, 2016.
>>>> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
>>>> critical bug fixes and major optimizations. See more details in Release
>>>> Note:
>>>> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>>>>
>>>> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>>>>
>>>> Please give it a try and vote on this thread. The vote will run for 5
>>>> days
>>>> ending 08/04/2017.
>>>>
>>>> Please note that my up to date public key are available from:
>>>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
>>>> Please don't forget to refresh the page if you've been there recently.
>>>> There are other place on Apache sites, which may contain my outdated
>>>> key.
>>>>
>>>> Thanks,
>>>> --Konstantin
>>>>
>>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>>
>>
>
>
> --
> A very happy Clouderan
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Konstantin Shvachko <sh...@gmail.com>.
Hi Wei-Chi,

There is bunch of performance jiras in Hadoop.
This one is not marked as blocker and seems to be hard to reproduce.
And I see that you are still discussing the problem and the solution with
Daryn in the jira.
I don't think it should block the release.
If this or anything else will prove to be a serious problem we can follow
up with a maintenance release containing hotfixes only.

Thanks,
--Konst

On Fri, Aug 4, 2017 at 9:24 AM, Wei-Chiu Chuang <we...@cloudera.com>
wrote:

> Hi,
> I'm sorry coming to this vote late.
> Daryn mentioned in HDFS-12136
> <https://issues.apache.org/jira/browse/HDFS-12136> that HDFS-11160
> <https://issues.apache.org/jira/browse/HDFS-11160> has a performance
> regression at DataNode due to the way it locks dataset lock.
>
> HDFS-11160 is in Hadoop 2.7.4. Would it be critical enough to warrant a
> stop for release?
>
> I myself can't reproduce the performance regression (assuming it only
> occurs under extreme workload). Would Daryn or other Yahoo folks comment?
>
> On Thu, Aug 3, 2017 at 10:31 PM, Akira Ajisaka <aa...@apache.org>
> wrote:
>
>> +1 (binding)
>>
>> - Verified the checksum and the signature of the source tarball
>> - Built from source with CentOS 7.2 and OpenJDK 1.8.0_141
>> - Built Hive 2.1.0/2.3.0 and Tez 0.8.5/0.9.0 with Hadoop 2.7.4 artifacts
>> - Built single node cluster and ran some Hive on Tez queries successfully
>>
>> Regards,
>> Akira
>>
>>
>> On 2017/08/04 0:25, Kuhu Shukla wrote:
>>
>>> +1 (non-binding)
>>>
>>> 1. Verified signatures and digests.
>>> 2. Built source.
>>> 3. Installed on a pseudo-distributed cluster.
>>> 4. Ran sample MR jobs and Tez example jobs like orderedwordcount
>>> successfully.
>>>
>>> Thank you Konstantin and others for this release.
>>>
>>> Regards,
>>> Kuhu
>>>
>>>
>>>
>>> On Thursday, August 3, 2017, 7:19:07 AM CDT, Sunil G <su...@apache.org>
>>> wrote:
>>>
>>>
>>> Thanks Konstantin
>>>
>>> +1 (binding)
>>>
>>> 1. Build tar ball from source package
>>> 2. Ran basic MR jobs and verified UI.
>>> 3. Enabled node labels and ran sleep job. Works fine.
>>> 4. Verified CLI commands related to node labels and its working fine.
>>> 5. RM WorkPreserving restart cases are also verified, and looks fine
>>>
>>> Thanks
>>> Sunil
>>>
>>>
>>>
>>> On Sun, Jul 30, 2017 at 4:59 AM Konstantin Shvachko <
>>> shv.hadoop@gmail.com>
>>> wrote:
>>>
>>> Hi everybody,
>>>>
>>>> Here is the next release of Apache Hadoop 2.7 line. The previous stable
>>>> release 2.7.3 was available since 25 August, 2016.
>>>> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
>>>> critical bug fixes and major optimizations. See more details in Release
>>>> Note:
>>>> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>>>>
>>>> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>>>>
>>>> Please give it a try and vote on this thread. The vote will run for 5
>>>> days
>>>> ending 08/04/2017.
>>>>
>>>> Please note that my up to date public key are available from:
>>>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
>>>> Please don't forget to refresh the page if you've been there recently.
>>>> There are other place on Apache sites, which may contain my outdated
>>>> key.
>>>>
>>>> Thanks,
>>>> --Konstantin
>>>>
>>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>>
>>
>
>
> --
> A very happy Clouderan
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Konstantin Shvachko <sh...@gmail.com>.
Hi Wei-Chi,

There is bunch of performance jiras in Hadoop.
This one is not marked as blocker and seems to be hard to reproduce.
And I see that you are still discussing the problem and the solution with
Daryn in the jira.
I don't think it should block the release.
If this or anything else will prove to be a serious problem we can follow
up with a maintenance release containing hotfixes only.

Thanks,
--Konst

On Fri, Aug 4, 2017 at 9:24 AM, Wei-Chiu Chuang <we...@cloudera.com>
wrote:

> Hi,
> I'm sorry coming to this vote late.
> Daryn mentioned in HDFS-12136
> <https://issues.apache.org/jira/browse/HDFS-12136> that HDFS-11160
> <https://issues.apache.org/jira/browse/HDFS-11160> has a performance
> regression at DataNode due to the way it locks dataset lock.
>
> HDFS-11160 is in Hadoop 2.7.4. Would it be critical enough to warrant a
> stop for release?
>
> I myself can't reproduce the performance regression (assuming it only
> occurs under extreme workload). Would Daryn or other Yahoo folks comment?
>
> On Thu, Aug 3, 2017 at 10:31 PM, Akira Ajisaka <aa...@apache.org>
> wrote:
>
>> +1 (binding)
>>
>> - Verified the checksum and the signature of the source tarball
>> - Built from source with CentOS 7.2 and OpenJDK 1.8.0_141
>> - Built Hive 2.1.0/2.3.0 and Tez 0.8.5/0.9.0 with Hadoop 2.7.4 artifacts
>> - Built single node cluster and ran some Hive on Tez queries successfully
>>
>> Regards,
>> Akira
>>
>>
>> On 2017/08/04 0:25, Kuhu Shukla wrote:
>>
>>> +1 (non-binding)
>>>
>>> 1. Verified signatures and digests.
>>> 2. Built source.
>>> 3. Installed on a pseudo-distributed cluster.
>>> 4. Ran sample MR jobs and Tez example jobs like orderedwordcount
>>> successfully.
>>>
>>> Thank you Konstantin and others for this release.
>>>
>>> Regards,
>>> Kuhu
>>>
>>>
>>>
>>> On Thursday, August 3, 2017, 7:19:07 AM CDT, Sunil G <su...@apache.org>
>>> wrote:
>>>
>>>
>>> Thanks Konstantin
>>>
>>> +1 (binding)
>>>
>>> 1. Build tar ball from source package
>>> 2. Ran basic MR jobs and verified UI.
>>> 3. Enabled node labels and ran sleep job. Works fine.
>>> 4. Verified CLI commands related to node labels and its working fine.
>>> 5. RM WorkPreserving restart cases are also verified, and looks fine
>>>
>>> Thanks
>>> Sunil
>>>
>>>
>>>
>>> On Sun, Jul 30, 2017 at 4:59 AM Konstantin Shvachko <
>>> shv.hadoop@gmail.com>
>>> wrote:
>>>
>>> Hi everybody,
>>>>
>>>> Here is the next release of Apache Hadoop 2.7 line. The previous stable
>>>> release 2.7.3 was available since 25 August, 2016.
>>>> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
>>>> critical bug fixes and major optimizations. See more details in Release
>>>> Note:
>>>> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>>>>
>>>> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>>>>
>>>> Please give it a try and vote on this thread. The vote will run for 5
>>>> days
>>>> ending 08/04/2017.
>>>>
>>>> Please note that my up to date public key are available from:
>>>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
>>>> Please don't forget to refresh the page if you've been there recently.
>>>> There are other place on Apache sites, which may contain my outdated
>>>> key.
>>>>
>>>> Thanks,
>>>> --Konstantin
>>>>
>>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>>
>>
>
>
> --
> A very happy Clouderan
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Konstantin Shvachko <sh...@gmail.com>.
Hi Wei-Chi,

There is bunch of performance jiras in Hadoop.
This one is not marked as blocker and seems to be hard to reproduce.
And I see that you are still discussing the problem and the solution with
Daryn in the jira.
I don't think it should block the release.
If this or anything else will prove to be a serious problem we can follow
up with a maintenance release containing hotfixes only.

Thanks,
--Konst

On Fri, Aug 4, 2017 at 9:24 AM, Wei-Chiu Chuang <we...@cloudera.com>
wrote:

> Hi,
> I'm sorry coming to this vote late.
> Daryn mentioned in HDFS-12136
> <https://issues.apache.org/jira/browse/HDFS-12136> that HDFS-11160
> <https://issues.apache.org/jira/browse/HDFS-11160> has a performance
> regression at DataNode due to the way it locks dataset lock.
>
> HDFS-11160 is in Hadoop 2.7.4. Would it be critical enough to warrant a
> stop for release?
>
> I myself can't reproduce the performance regression (assuming it only
> occurs under extreme workload). Would Daryn or other Yahoo folks comment?
>
> On Thu, Aug 3, 2017 at 10:31 PM, Akira Ajisaka <aa...@apache.org>
> wrote:
>
>> +1 (binding)
>>
>> - Verified the checksum and the signature of the source tarball
>> - Built from source with CentOS 7.2 and OpenJDK 1.8.0_141
>> - Built Hive 2.1.0/2.3.0 and Tez 0.8.5/0.9.0 with Hadoop 2.7.4 artifacts
>> - Built single node cluster and ran some Hive on Tez queries successfully
>>
>> Regards,
>> Akira
>>
>>
>> On 2017/08/04 0:25, Kuhu Shukla wrote:
>>
>>> +1 (non-binding)
>>>
>>> 1. Verified signatures and digests.
>>> 2. Built source.
>>> 3. Installed on a pseudo-distributed cluster.
>>> 4. Ran sample MR jobs and Tez example jobs like orderedwordcount
>>> successfully.
>>>
>>> Thank you Konstantin and others for this release.
>>>
>>> Regards,
>>> Kuhu
>>>
>>>
>>>
>>> On Thursday, August 3, 2017, 7:19:07 AM CDT, Sunil G <su...@apache.org>
>>> wrote:
>>>
>>>
>>> Thanks Konstantin
>>>
>>> +1 (binding)
>>>
>>> 1. Build tar ball from source package
>>> 2. Ran basic MR jobs and verified UI.
>>> 3. Enabled node labels and ran sleep job. Works fine.
>>> 4. Verified CLI commands related to node labels and its working fine.
>>> 5. RM WorkPreserving restart cases are also verified, and looks fine
>>>
>>> Thanks
>>> Sunil
>>>
>>>
>>>
>>> On Sun, Jul 30, 2017 at 4:59 AM Konstantin Shvachko <
>>> shv.hadoop@gmail.com>
>>> wrote:
>>>
>>> Hi everybody,
>>>>
>>>> Here is the next release of Apache Hadoop 2.7 line. The previous stable
>>>> release 2.7.3 was available since 25 August, 2016.
>>>> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
>>>> critical bug fixes and major optimizations. See more details in Release
>>>> Note:
>>>> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>>>>
>>>> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>>>>
>>>> Please give it a try and vote on this thread. The vote will run for 5
>>>> days
>>>> ending 08/04/2017.
>>>>
>>>> Please note that my up to date public key are available from:
>>>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
>>>> Please don't forget to refresh the page if you've been there recently.
>>>> There are other place on Apache sites, which may contain my outdated
>>>> key.
>>>>
>>>> Thanks,
>>>> --Konstantin
>>>>
>>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>>
>>
>
>
> --
> A very happy Clouderan
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Erik Krogen <ek...@linkedin.com>.
Forgot to mention, also did Namenode performance testing using Dynamometer (see http://mail-archives.apache.org/mod_mbox/hadoop-common-dev/201707.mbox/%3CCAGkyFnM7Ltpb-C_rxP43VUguRXb1bvxPH7GMqdSweE2iJx7i%2Bg%40mail.gmail.com%3E). Reran production traces from multi-thousand node clusters and did not see any noticeable performance regressions as compared to previous releases.

Erik

On 8/4/17, 11:38 AM, "Erik Krogen" <ek...@linkedin.com> wrote:

    +1 (non-binding)
    
    - Verified checksum and signature of source and binary tarballs
    - Built from source, macOS Sierra 10.12.3 and RHEL 6.6, Oracle JDK 1.8.0_72
    - Ran basic HDFS commands and some MR example jobs (using 2.7.4 client) against a 2.6.1 cluster
    - Started MiniCluster, ran basic HDFS commands and some MR example jobs as well as some MR jobs compiled against 2.6.1
    
    Erik
    
    On 8/4/17, 9:24 AM, "Wei-Chiu Chuang" <we...@cloudera.com> wrote:
    
        Hi,
        I'm sorry coming to this vote late.
        Daryn mentioned in HDFS-12136
        <https://issues.apache.org/jira/browse/HDFS-12136> that HDFS-11160
        <https://issues.apache.org/jira/browse/HDFS-11160> has a performance
        regression at DataNode due to the way it locks dataset lock.
        
        HDFS-11160 is in Hadoop 2.7.4. Would it be critical enough to warrant a
        stop for release?
        
        I myself can't reproduce the performance regression (assuming it only
        occurs under extreme workload). Would Daryn or other Yahoo folks comment?
        
        On Thu, Aug 3, 2017 at 10:31 PM, Akira Ajisaka <aa...@apache.org> wrote:
        
        > +1 (binding)
        >
        > - Verified the checksum and the signature of the source tarball
        > - Built from source with CentOS 7.2 and OpenJDK 1.8.0_141
        > - Built Hive 2.1.0/2.3.0 and Tez 0.8.5/0.9.0 with Hadoop 2.7.4 artifacts
        > - Built single node cluster and ran some Hive on Tez queries successfully
        >
        > Regards,
        > Akira
        >
        >
        > On 2017/08/04 0:25, Kuhu Shukla wrote:
        >
        >> +1 (non-binding)
        >>
        >> 1. Verified signatures and digests.
        >> 2. Built source.
        >> 3. Installed on a pseudo-distributed cluster.
        >> 4. Ran sample MR jobs and Tez example jobs like orderedwordcount
        >> successfully.
        >>
        >> Thank you Konstantin and others for this release.
        >>
        >> Regards,
        >> Kuhu
        >>
        >>
        >>
        >> On Thursday, August 3, 2017, 7:19:07 AM CDT, Sunil G <su...@apache.org>
        >> wrote:
        >>
        >>
        >> Thanks Konstantin
        >>
        >> +1 (binding)
        >>
        >> 1. Build tar ball from source package
        >> 2. Ran basic MR jobs and verified UI.
        >> 3. Enabled node labels and ran sleep job. Works fine.
        >> 4. Verified CLI commands related to node labels and its working fine.
        >> 5. RM WorkPreserving restart cases are also verified, and looks fine
        >>
        >> Thanks
        >> Sunil
        >>
        >>
        >>
        >> On Sun, Jul 30, 2017 at 4:59 AM Konstantin Shvachko <shv.hadoop@gmail.com
        >> >
        >> wrote:
        >>
        >> Hi everybody,
        >>>
        >>> Here is the next release of Apache Hadoop 2.7 line. The previous stable
        >>> release 2.7.3 was available since 25 August, 2016.
        >>> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
        >>> critical bug fixes and major optimizations. See more details in Release
        >>> Note:
        >>> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
        >>>
        >>> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
        >>>
        >>> Please give it a try and vote on this thread. The vote will run for 5
        >>> days
        >>> ending 08/04/2017.
        >>>
        >>> Please note that my up to date public key are available from:
        >>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
        >>> Please don't forget to refresh the page if you've been there recently.
        >>> There are other place on Apache sites, which may contain my outdated key.
        >>>
        >>> Thanks,
        >>> --Konstantin
        >>>
        >>>
        > ---------------------------------------------------------------------
        > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
        > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
        >
        >
        
        
        -- 
        A very happy Clouderan
        
    
    
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
    For additional commands, e-mail: hdfs-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.7.4 (RC0)

Posted by Erik Krogen <ek...@linkedin.com>.
Forgot to mention, also did Namenode performance testing using Dynamometer (see http://mail-archives.apache.org/mod_mbox/hadoop-common-dev/201707.mbox/%3CCAGkyFnM7Ltpb-C_rxP43VUguRXb1bvxPH7GMqdSweE2iJx7i%2Bg%40mail.gmail.com%3E). Reran production traces from multi-thousand node clusters and did not see any noticeable performance regressions as compared to previous releases.

Erik

On 8/4/17, 11:38 AM, "Erik Krogen" <ek...@linkedin.com> wrote:

    +1 (non-binding)
    
    - Verified checksum and signature of source and binary tarballs
    - Built from source, macOS Sierra 10.12.3 and RHEL 6.6, Oracle JDK 1.8.0_72
    - Ran basic HDFS commands and some MR example jobs (using 2.7.4 client) against a 2.6.1 cluster
    - Started MiniCluster, ran basic HDFS commands and some MR example jobs as well as some MR jobs compiled against 2.6.1
    
    Erik
    
    On 8/4/17, 9:24 AM, "Wei-Chiu Chuang" <we...@cloudera.com> wrote:
    
        Hi,
        I'm sorry coming to this vote late.
        Daryn mentioned in HDFS-12136
        <https://issues.apache.org/jira/browse/HDFS-12136> that HDFS-11160
        <https://issues.apache.org/jira/browse/HDFS-11160> has a performance
        regression at DataNode due to the way it locks dataset lock.
        
        HDFS-11160 is in Hadoop 2.7.4. Would it be critical enough to warrant a
        stop for release?
        
        I myself can't reproduce the performance regression (assuming it only
        occurs under extreme workload). Would Daryn or other Yahoo folks comment?
        
        On Thu, Aug 3, 2017 at 10:31 PM, Akira Ajisaka <aa...@apache.org> wrote:
        
        > +1 (binding)
        >
        > - Verified the checksum and the signature of the source tarball
        > - Built from source with CentOS 7.2 and OpenJDK 1.8.0_141
        > - Built Hive 2.1.0/2.3.0 and Tez 0.8.5/0.9.0 with Hadoop 2.7.4 artifacts
        > - Built single node cluster and ran some Hive on Tez queries successfully
        >
        > Regards,
        > Akira
        >
        >
        > On 2017/08/04 0:25, Kuhu Shukla wrote:
        >
        >> +1 (non-binding)
        >>
        >> 1. Verified signatures and digests.
        >> 2. Built source.
        >> 3. Installed on a pseudo-distributed cluster.
        >> 4. Ran sample MR jobs and Tez example jobs like orderedwordcount
        >> successfully.
        >>
        >> Thank you Konstantin and others for this release.
        >>
        >> Regards,
        >> Kuhu
        >>
        >>
        >>
        >> On Thursday, August 3, 2017, 7:19:07 AM CDT, Sunil G <su...@apache.org>
        >> wrote:
        >>
        >>
        >> Thanks Konstantin
        >>
        >> +1 (binding)
        >>
        >> 1. Build tar ball from source package
        >> 2. Ran basic MR jobs and verified UI.
        >> 3. Enabled node labels and ran sleep job. Works fine.
        >> 4. Verified CLI commands related to node labels and its working fine.
        >> 5. RM WorkPreserving restart cases are also verified, and looks fine
        >>
        >> Thanks
        >> Sunil
        >>
        >>
        >>
        >> On Sun, Jul 30, 2017 at 4:59 AM Konstantin Shvachko <shv.hadoop@gmail.com
        >> >
        >> wrote:
        >>
        >> Hi everybody,
        >>>
        >>> Here is the next release of Apache Hadoop 2.7 line. The previous stable
        >>> release 2.7.3 was available since 25 August, 2016.
        >>> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
        >>> critical bug fixes and major optimizations. See more details in Release
        >>> Note:
        >>> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
        >>>
        >>> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
        >>>
        >>> Please give it a try and vote on this thread. The vote will run for 5
        >>> days
        >>> ending 08/04/2017.
        >>>
        >>> Please note that my up to date public key are available from:
        >>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
        >>> Please don't forget to refresh the page if you've been there recently.
        >>> There are other place on Apache sites, which may contain my outdated key.
        >>>
        >>> Thanks,
        >>> --Konstantin
        >>>
        >>>
        > ---------------------------------------------------------------------
        > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
        > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
        >
        >
        
        
        -- 
        A very happy Clouderan
        
    
    
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
    For additional commands, e-mail: hdfs-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.7.4 (RC0)

Posted by Erik Krogen <ek...@linkedin.com>.
+1 (non-binding)

- Verified checksum and signature of source and binary tarballs
- Built from source, macOS Sierra 10.12.3 and RHEL 6.6, Oracle JDK 1.8.0_72
- Ran basic HDFS commands and some MR example jobs (using 2.7.4 client) against a 2.6.1 cluster
- Started MiniCluster, ran basic HDFS commands and some MR example jobs as well as some MR jobs compiled against 2.6.1

Erik

On 8/4/17, 9:24 AM, "Wei-Chiu Chuang" <we...@cloudera.com> wrote:

    Hi,
    I'm sorry coming to this vote late.
    Daryn mentioned in HDFS-12136
    <https://issues.apache.org/jira/browse/HDFS-12136> that HDFS-11160
    <https://issues.apache.org/jira/browse/HDFS-11160> has a performance
    regression at DataNode due to the way it locks dataset lock.
    
    HDFS-11160 is in Hadoop 2.7.4. Would it be critical enough to warrant a
    stop for release?
    
    I myself can't reproduce the performance regression (assuming it only
    occurs under extreme workload). Would Daryn or other Yahoo folks comment?
    
    On Thu, Aug 3, 2017 at 10:31 PM, Akira Ajisaka <aa...@apache.org> wrote:
    
    > +1 (binding)
    >
    > - Verified the checksum and the signature of the source tarball
    > - Built from source with CentOS 7.2 and OpenJDK 1.8.0_141
    > - Built Hive 2.1.0/2.3.0 and Tez 0.8.5/0.9.0 with Hadoop 2.7.4 artifacts
    > - Built single node cluster and ran some Hive on Tez queries successfully
    >
    > Regards,
    > Akira
    >
    >
    > On 2017/08/04 0:25, Kuhu Shukla wrote:
    >
    >> +1 (non-binding)
    >>
    >> 1. Verified signatures and digests.
    >> 2. Built source.
    >> 3. Installed on a pseudo-distributed cluster.
    >> 4. Ran sample MR jobs and Tez example jobs like orderedwordcount
    >> successfully.
    >>
    >> Thank you Konstantin and others for this release.
    >>
    >> Regards,
    >> Kuhu
    >>
    >>
    >>
    >> On Thursday, August 3, 2017, 7:19:07 AM CDT, Sunil G <su...@apache.org>
    >> wrote:
    >>
    >>
    >> Thanks Konstantin
    >>
    >> +1 (binding)
    >>
    >> 1. Build tar ball from source package
    >> 2. Ran basic MR jobs and verified UI.
    >> 3. Enabled node labels and ran sleep job. Works fine.
    >> 4. Verified CLI commands related to node labels and its working fine.
    >> 5. RM WorkPreserving restart cases are also verified, and looks fine
    >>
    >> Thanks
    >> Sunil
    >>
    >>
    >>
    >> On Sun, Jul 30, 2017 at 4:59 AM Konstantin Shvachko <shv.hadoop@gmail.com
    >> >
    >> wrote:
    >>
    >> Hi everybody,
    >>>
    >>> Here is the next release of Apache Hadoop 2.7 line. The previous stable
    >>> release 2.7.3 was available since 25 August, 2016.
    >>> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
    >>> critical bug fixes and major optimizations. See more details in Release
    >>> Note:
    >>> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
    >>>
    >>> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
    >>>
    >>> Please give it a try and vote on this thread. The vote will run for 5
    >>> days
    >>> ending 08/04/2017.
    >>>
    >>> Please note that my up to date public key are available from:
    >>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
    >>> Please don't forget to refresh the page if you've been there recently.
    >>> There are other place on Apache sites, which may contain my outdated key.
    >>>
    >>> Thanks,
    >>> --Konstantin
    >>>
    >>>
    > ---------------------------------------------------------------------
    > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
    > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
    >
    >
    
    
    -- 
    A very happy Clouderan
    


---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Erik Krogen <ek...@linkedin.com>.
+1 (non-binding)

- Verified checksum and signature of source and binary tarballs
- Built from source, macOS Sierra 10.12.3 and RHEL 6.6, Oracle JDK 1.8.0_72
- Ran basic HDFS commands and some MR example jobs (using 2.7.4 client) against a 2.6.1 cluster
- Started MiniCluster, ran basic HDFS commands and some MR example jobs as well as some MR jobs compiled against 2.6.1

Erik

On 8/4/17, 9:24 AM, "Wei-Chiu Chuang" <we...@cloudera.com> wrote:

    Hi,
    I'm sorry coming to this vote late.
    Daryn mentioned in HDFS-12136
    <https://issues.apache.org/jira/browse/HDFS-12136> that HDFS-11160
    <https://issues.apache.org/jira/browse/HDFS-11160> has a performance
    regression at DataNode due to the way it locks dataset lock.
    
    HDFS-11160 is in Hadoop 2.7.4. Would it be critical enough to warrant a
    stop for release?
    
    I myself can't reproduce the performance regression (assuming it only
    occurs under extreme workload). Would Daryn or other Yahoo folks comment?
    
    On Thu, Aug 3, 2017 at 10:31 PM, Akira Ajisaka <aa...@apache.org> wrote:
    
    > +1 (binding)
    >
    > - Verified the checksum and the signature of the source tarball
    > - Built from source with CentOS 7.2 and OpenJDK 1.8.0_141
    > - Built Hive 2.1.0/2.3.0 and Tez 0.8.5/0.9.0 with Hadoop 2.7.4 artifacts
    > - Built single node cluster and ran some Hive on Tez queries successfully
    >
    > Regards,
    > Akira
    >
    >
    > On 2017/08/04 0:25, Kuhu Shukla wrote:
    >
    >> +1 (non-binding)
    >>
    >> 1. Verified signatures and digests.
    >> 2. Built source.
    >> 3. Installed on a pseudo-distributed cluster.
    >> 4. Ran sample MR jobs and Tez example jobs like orderedwordcount
    >> successfully.
    >>
    >> Thank you Konstantin and others for this release.
    >>
    >> Regards,
    >> Kuhu
    >>
    >>
    >>
    >> On Thursday, August 3, 2017, 7:19:07 AM CDT, Sunil G <su...@apache.org>
    >> wrote:
    >>
    >>
    >> Thanks Konstantin
    >>
    >> +1 (binding)
    >>
    >> 1. Build tar ball from source package
    >> 2. Ran basic MR jobs and verified UI.
    >> 3. Enabled node labels and ran sleep job. Works fine.
    >> 4. Verified CLI commands related to node labels and its working fine.
    >> 5. RM WorkPreserving restart cases are also verified, and looks fine
    >>
    >> Thanks
    >> Sunil
    >>
    >>
    >>
    >> On Sun, Jul 30, 2017 at 4:59 AM Konstantin Shvachko <shv.hadoop@gmail.com
    >> >
    >> wrote:
    >>
    >> Hi everybody,
    >>>
    >>> Here is the next release of Apache Hadoop 2.7 line. The previous stable
    >>> release 2.7.3 was available since 25 August, 2016.
    >>> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
    >>> critical bug fixes and major optimizations. See more details in Release
    >>> Note:
    >>> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
    >>>
    >>> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
    >>>
    >>> Please give it a try and vote on this thread. The vote will run for 5
    >>> days
    >>> ending 08/04/2017.
    >>>
    >>> Please note that my up to date public key are available from:
    >>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
    >>> Please don't forget to refresh the page if you've been there recently.
    >>> There are other place on Apache sites, which may contain my outdated key.
    >>>
    >>> Thanks,
    >>> --Konstantin
    >>>
    >>>
    > ---------------------------------------------------------------------
    > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
    > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
    >
    >
    
    
    -- 
    A very happy Clouderan
    


---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Wei-Chiu Chuang <we...@cloudera.com>.
Hi,
I'm sorry coming to this vote late.
Daryn mentioned in HDFS-12136
<https://issues.apache.org/jira/browse/HDFS-12136> that HDFS-11160
<https://issues.apache.org/jira/browse/HDFS-11160> has a performance
regression at DataNode due to the way it locks dataset lock.

HDFS-11160 is in Hadoop 2.7.4. Would it be critical enough to warrant a
stop for release?

I myself can't reproduce the performance regression (assuming it only
occurs under extreme workload). Would Daryn or other Yahoo folks comment?

On Thu, Aug 3, 2017 at 10:31 PM, Akira Ajisaka <aa...@apache.org> wrote:

> +1 (binding)
>
> - Verified the checksum and the signature of the source tarball
> - Built from source with CentOS 7.2 and OpenJDK 1.8.0_141
> - Built Hive 2.1.0/2.3.0 and Tez 0.8.5/0.9.0 with Hadoop 2.7.4 artifacts
> - Built single node cluster and ran some Hive on Tez queries successfully
>
> Regards,
> Akira
>
>
> On 2017/08/04 0:25, Kuhu Shukla wrote:
>
>> +1 (non-binding)
>>
>> 1. Verified signatures and digests.
>> 2. Built source.
>> 3. Installed on a pseudo-distributed cluster.
>> 4. Ran sample MR jobs and Tez example jobs like orderedwordcount
>> successfully.
>>
>> Thank you Konstantin and others for this release.
>>
>> Regards,
>> Kuhu
>>
>>
>>
>> On Thursday, August 3, 2017, 7:19:07 AM CDT, Sunil G <su...@apache.org>
>> wrote:
>>
>>
>> Thanks Konstantin
>>
>> +1 (binding)
>>
>> 1. Build tar ball from source package
>> 2. Ran basic MR jobs and verified UI.
>> 3. Enabled node labels and ran sleep job. Works fine.
>> 4. Verified CLI commands related to node labels and its working fine.
>> 5. RM WorkPreserving restart cases are also verified, and looks fine
>>
>> Thanks
>> Sunil
>>
>>
>>
>> On Sun, Jul 30, 2017 at 4:59 AM Konstantin Shvachko <shv.hadoop@gmail.com
>> >
>> wrote:
>>
>> Hi everybody,
>>>
>>> Here is the next release of Apache Hadoop 2.7 line. The previous stable
>>> release 2.7.3 was available since 25 August, 2016.
>>> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
>>> critical bug fixes and major optimizations. See more details in Release
>>> Note:
>>> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>>>
>>> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>>>
>>> Please give it a try and vote on this thread. The vote will run for 5
>>> days
>>> ending 08/04/2017.
>>>
>>> Please note that my up to date public key are available from:
>>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
>>> Please don't forget to refresh the page if you've been there recently.
>>> There are other place on Apache sites, which may contain my outdated key.
>>>
>>> Thanks,
>>> --Konstantin
>>>
>>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
>


-- 
A very happy Clouderan

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Wei-Chiu Chuang <we...@cloudera.com>.
Hi,
I'm sorry coming to this vote late.
Daryn mentioned in HDFS-12136
<https://issues.apache.org/jira/browse/HDFS-12136> that HDFS-11160
<https://issues.apache.org/jira/browse/HDFS-11160> has a performance
regression at DataNode due to the way it locks dataset lock.

HDFS-11160 is in Hadoop 2.7.4. Would it be critical enough to warrant a
stop for release?

I myself can't reproduce the performance regression (assuming it only
occurs under extreme workload). Would Daryn or other Yahoo folks comment?

On Thu, Aug 3, 2017 at 10:31 PM, Akira Ajisaka <aa...@apache.org> wrote:

> +1 (binding)
>
> - Verified the checksum and the signature of the source tarball
> - Built from source with CentOS 7.2 and OpenJDK 1.8.0_141
> - Built Hive 2.1.0/2.3.0 and Tez 0.8.5/0.9.0 with Hadoop 2.7.4 artifacts
> - Built single node cluster and ran some Hive on Tez queries successfully
>
> Regards,
> Akira
>
>
> On 2017/08/04 0:25, Kuhu Shukla wrote:
>
>> +1 (non-binding)
>>
>> 1. Verified signatures and digests.
>> 2. Built source.
>> 3. Installed on a pseudo-distributed cluster.
>> 4. Ran sample MR jobs and Tez example jobs like orderedwordcount
>> successfully.
>>
>> Thank you Konstantin and others for this release.
>>
>> Regards,
>> Kuhu
>>
>>
>>
>> On Thursday, August 3, 2017, 7:19:07 AM CDT, Sunil G <su...@apache.org>
>> wrote:
>>
>>
>> Thanks Konstantin
>>
>> +1 (binding)
>>
>> 1. Build tar ball from source package
>> 2. Ran basic MR jobs and verified UI.
>> 3. Enabled node labels and ran sleep job. Works fine.
>> 4. Verified CLI commands related to node labels and its working fine.
>> 5. RM WorkPreserving restart cases are also verified, and looks fine
>>
>> Thanks
>> Sunil
>>
>>
>>
>> On Sun, Jul 30, 2017 at 4:59 AM Konstantin Shvachko <shv.hadoop@gmail.com
>> >
>> wrote:
>>
>> Hi everybody,
>>>
>>> Here is the next release of Apache Hadoop 2.7 line. The previous stable
>>> release 2.7.3 was available since 25 August, 2016.
>>> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
>>> critical bug fixes and major optimizations. See more details in Release
>>> Note:
>>> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>>>
>>> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>>>
>>> Please give it a try and vote on this thread. The vote will run for 5
>>> days
>>> ending 08/04/2017.
>>>
>>> Please note that my up to date public key are available from:
>>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
>>> Please don't forget to refresh the page if you've been there recently.
>>> There are other place on Apache sites, which may contain my outdated key.
>>>
>>> Thanks,
>>> --Konstantin
>>>
>>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
>


-- 
A very happy Clouderan

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Wei-Chiu Chuang <we...@cloudera.com>.
Hi,
I'm sorry coming to this vote late.
Daryn mentioned in HDFS-12136
<https://issues.apache.org/jira/browse/HDFS-12136> that HDFS-11160
<https://issues.apache.org/jira/browse/HDFS-11160> has a performance
regression at DataNode due to the way it locks dataset lock.

HDFS-11160 is in Hadoop 2.7.4. Would it be critical enough to warrant a
stop for release?

I myself can't reproduce the performance regression (assuming it only
occurs under extreme workload). Would Daryn or other Yahoo folks comment?

On Thu, Aug 3, 2017 at 10:31 PM, Akira Ajisaka <aa...@apache.org> wrote:

> +1 (binding)
>
> - Verified the checksum and the signature of the source tarball
> - Built from source with CentOS 7.2 and OpenJDK 1.8.0_141
> - Built Hive 2.1.0/2.3.0 and Tez 0.8.5/0.9.0 with Hadoop 2.7.4 artifacts
> - Built single node cluster and ran some Hive on Tez queries successfully
>
> Regards,
> Akira
>
>
> On 2017/08/04 0:25, Kuhu Shukla wrote:
>
>> +1 (non-binding)
>>
>> 1. Verified signatures and digests.
>> 2. Built source.
>> 3. Installed on a pseudo-distributed cluster.
>> 4. Ran sample MR jobs and Tez example jobs like orderedwordcount
>> successfully.
>>
>> Thank you Konstantin and others for this release.
>>
>> Regards,
>> Kuhu
>>
>>
>>
>> On Thursday, August 3, 2017, 7:19:07 AM CDT, Sunil G <su...@apache.org>
>> wrote:
>>
>>
>> Thanks Konstantin
>>
>> +1 (binding)
>>
>> 1. Build tar ball from source package
>> 2. Ran basic MR jobs and verified UI.
>> 3. Enabled node labels and ran sleep job. Works fine.
>> 4. Verified CLI commands related to node labels and its working fine.
>> 5. RM WorkPreserving restart cases are also verified, and looks fine
>>
>> Thanks
>> Sunil
>>
>>
>>
>> On Sun, Jul 30, 2017 at 4:59 AM Konstantin Shvachko <shv.hadoop@gmail.com
>> >
>> wrote:
>>
>> Hi everybody,
>>>
>>> Here is the next release of Apache Hadoop 2.7 line. The previous stable
>>> release 2.7.3 was available since 25 August, 2016.
>>> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
>>> critical bug fixes and major optimizations. See more details in Release
>>> Note:
>>> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>>>
>>> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>>>
>>> Please give it a try and vote on this thread. The vote will run for 5
>>> days
>>> ending 08/04/2017.
>>>
>>> Please note that my up to date public key are available from:
>>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
>>> Please don't forget to refresh the page if you've been there recently.
>>> There are other place on Apache sites, which may contain my outdated key.
>>>
>>> Thanks,
>>> --Konstantin
>>>
>>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
>


-- 
A very happy Clouderan

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Wei-Chiu Chuang <we...@cloudera.com>.
Hi,
I'm sorry coming to this vote late.
Daryn mentioned in HDFS-12136
<https://issues.apache.org/jira/browse/HDFS-12136> that HDFS-11160
<https://issues.apache.org/jira/browse/HDFS-11160> has a performance
regression at DataNode due to the way it locks dataset lock.

HDFS-11160 is in Hadoop 2.7.4. Would it be critical enough to warrant a
stop for release?

I myself can't reproduce the performance regression (assuming it only
occurs under extreme workload). Would Daryn or other Yahoo folks comment?

On Thu, Aug 3, 2017 at 10:31 PM, Akira Ajisaka <aa...@apache.org> wrote:

> +1 (binding)
>
> - Verified the checksum and the signature of the source tarball
> - Built from source with CentOS 7.2 and OpenJDK 1.8.0_141
> - Built Hive 2.1.0/2.3.0 and Tez 0.8.5/0.9.0 with Hadoop 2.7.4 artifacts
> - Built single node cluster and ran some Hive on Tez queries successfully
>
> Regards,
> Akira
>
>
> On 2017/08/04 0:25, Kuhu Shukla wrote:
>
>> +1 (non-binding)
>>
>> 1. Verified signatures and digests.
>> 2. Built source.
>> 3. Installed on a pseudo-distributed cluster.
>> 4. Ran sample MR jobs and Tez example jobs like orderedwordcount
>> successfully.
>>
>> Thank you Konstantin and others for this release.
>>
>> Regards,
>> Kuhu
>>
>>
>>
>> On Thursday, August 3, 2017, 7:19:07 AM CDT, Sunil G <su...@apache.org>
>> wrote:
>>
>>
>> Thanks Konstantin
>>
>> +1 (binding)
>>
>> 1. Build tar ball from source package
>> 2. Ran basic MR jobs and verified UI.
>> 3. Enabled node labels and ran sleep job. Works fine.
>> 4. Verified CLI commands related to node labels and its working fine.
>> 5. RM WorkPreserving restart cases are also verified, and looks fine
>>
>> Thanks
>> Sunil
>>
>>
>>
>> On Sun, Jul 30, 2017 at 4:59 AM Konstantin Shvachko <shv.hadoop@gmail.com
>> >
>> wrote:
>>
>> Hi everybody,
>>>
>>> Here is the next release of Apache Hadoop 2.7 line. The previous stable
>>> release 2.7.3 was available since 25 August, 2016.
>>> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
>>> critical bug fixes and major optimizations. See more details in Release
>>> Note:
>>> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>>>
>>> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>>>
>>> Please give it a try and vote on this thread. The vote will run for 5
>>> days
>>> ending 08/04/2017.
>>>
>>> Please note that my up to date public key are available from:
>>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
>>> Please don't forget to refresh the page if you've been there recently.
>>> There are other place on Apache sites, which may contain my outdated key.
>>>
>>> Thanks,
>>> --Konstantin
>>>
>>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
>


-- 
A very happy Clouderan

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Akira Ajisaka <aa...@apache.org>.
+1 (binding)

- Verified the checksum and the signature of the source tarball
- Built from source with CentOS 7.2 and OpenJDK 1.8.0_141
- Built Hive 2.1.0/2.3.0 and Tez 0.8.5/0.9.0 with Hadoop 2.7.4 artifacts
- Built single node cluster and ran some Hive on Tez queries successfully

Regards,
Akira

On 2017/08/04 0:25, Kuhu Shukla wrote:
> +1 (non-binding)
>
> 1. Verified signatures and digests.
> 2. Built source.
> 3. Installed on a pseudo-distributed cluster.
> 4. Ran sample MR jobs and Tez example jobs like orderedwordcount successfully.
>
> Thank you Konstantin and others for this release.
>
> Regards,
> Kuhu
>
>
>
> On Thursday, August 3, 2017, 7:19:07 AM CDT, Sunil G <su...@apache.org> wrote:
>
>
> Thanks Konstantin
>
> +1 (binding)
>
> 1. Build tar ball from source package
> 2. Ran basic MR jobs and verified UI.
> 3. Enabled node labels and ran sleep job. Works fine.
> 4. Verified CLI commands related to node labels and its working fine.
> 5. RM WorkPreserving restart cases are also verified, and looks fine
>
> Thanks
> Sunil
>
>
>
> On Sun, Jul 30, 2017 at 4:59 AM Konstantin Shvachko <sh...@gmail.com>
> wrote:
>
>> Hi everybody,
>>
>> Here is the next release of Apache Hadoop 2.7 line. The previous stable
>> release 2.7.3 was available since 25 August, 2016.
>> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
>> critical bug fixes and major optimizations. See more details in Release
>> Note:
>> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>>
>> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>>
>> Please give it a try and vote on this thread. The vote will run for 5 days
>> ending 08/04/2017.
>>
>> Please note that my up to date public key are available from:
>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
>> Please don't forget to refresh the page if you've been there recently.
>> There are other place on Apache sites, which may contain my outdated key.
>>
>> Thanks,
>> --Konstantin
>>

---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Akira Ajisaka <aa...@apache.org>.
+1 (binding)

- Verified the checksum and the signature of the source tarball
- Built from source with CentOS 7.2 and OpenJDK 1.8.0_141
- Built Hive 2.1.0/2.3.0 and Tez 0.8.5/0.9.0 with Hadoop 2.7.4 artifacts
- Built single node cluster and ran some Hive on Tez queries successfully

Regards,
Akira

On 2017/08/04 0:25, Kuhu Shukla wrote:
> +1 (non-binding)
>
> 1. Verified signatures and digests.
> 2. Built source.
> 3. Installed on a pseudo-distributed cluster.
> 4. Ran sample MR jobs and Tez example jobs like orderedwordcount successfully.
>
> Thank you Konstantin and others for this release.
>
> Regards,
> Kuhu
>
>
>
> On Thursday, August 3, 2017, 7:19:07 AM CDT, Sunil G <su...@apache.org> wrote:
>
>
> Thanks Konstantin
>
> +1 (binding)
>
> 1. Build tar ball from source package
> 2. Ran basic MR jobs and verified UI.
> 3. Enabled node labels and ran sleep job. Works fine.
> 4. Verified CLI commands related to node labels and its working fine.
> 5. RM WorkPreserving restart cases are also verified, and looks fine
>
> Thanks
> Sunil
>
>
>
> On Sun, Jul 30, 2017 at 4:59 AM Konstantin Shvachko <sh...@gmail.com>
> wrote:
>
>> Hi everybody,
>>
>> Here is the next release of Apache Hadoop 2.7 line. The previous stable
>> release 2.7.3 was available since 25 August, 2016.
>> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
>> critical bug fixes and major optimizations. See more details in Release
>> Note:
>> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>>
>> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>>
>> Please give it a try and vote on this thread. The vote will run for 5 days
>> ending 08/04/2017.
>>
>> Please note that my up to date public key are available from:
>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
>> Please don't forget to refresh the page if you've been there recently.
>> There are other place on Apache sites, which may contain my outdated key.
>>
>> Thanks,
>> --Konstantin
>>

---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Akira Ajisaka <aa...@apache.org>.
+1 (binding)

- Verified the checksum and the signature of the source tarball
- Built from source with CentOS 7.2 and OpenJDK 1.8.0_141
- Built Hive 2.1.0/2.3.0 and Tez 0.8.5/0.9.0 with Hadoop 2.7.4 artifacts
- Built single node cluster and ran some Hive on Tez queries successfully

Regards,
Akira

On 2017/08/04 0:25, Kuhu Shukla wrote:
> +1 (non-binding)
>
> 1. Verified signatures and digests.
> 2. Built source.
> 3. Installed on a pseudo-distributed cluster.
> 4. Ran sample MR jobs and Tez example jobs like orderedwordcount successfully.
>
> Thank you Konstantin and others for this release.
>
> Regards,
> Kuhu
>
>
>
> On Thursday, August 3, 2017, 7:19:07 AM CDT, Sunil G <su...@apache.org> wrote:
>
>
> Thanks Konstantin
>
> +1 (binding)
>
> 1. Build tar ball from source package
> 2. Ran basic MR jobs and verified UI.
> 3. Enabled node labels and ran sleep job. Works fine.
> 4. Verified CLI commands related to node labels and its working fine.
> 5. RM WorkPreserving restart cases are also verified, and looks fine
>
> Thanks
> Sunil
>
>
>
> On Sun, Jul 30, 2017 at 4:59 AM Konstantin Shvachko <sh...@gmail.com>
> wrote:
>
>> Hi everybody,
>>
>> Here is the next release of Apache Hadoop 2.7 line. The previous stable
>> release 2.7.3 was available since 25 August, 2016.
>> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
>> critical bug fixes and major optimizations. See more details in Release
>> Note:
>> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>>
>> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>>
>> Please give it a try and vote on this thread. The vote will run for 5 days
>> ending 08/04/2017.
>>
>> Please note that my up to date public key are available from:
>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
>> Please don't forget to refresh the page if you've been there recently.
>> There are other place on Apache sites, which may contain my outdated key.
>>
>> Thanks,
>> --Konstantin
>>

---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Akira Ajisaka <aa...@apache.org>.
+1 (binding)

- Verified the checksum and the signature of the source tarball
- Built from source with CentOS 7.2 and OpenJDK 1.8.0_141
- Built Hive 2.1.0/2.3.0 and Tez 0.8.5/0.9.0 with Hadoop 2.7.4 artifacts
- Built single node cluster and ran some Hive on Tez queries successfully

Regards,
Akira

On 2017/08/04 0:25, Kuhu Shukla wrote:
> +1 (non-binding)
>
> 1. Verified signatures and digests.
> 2. Built source.
> 3. Installed on a pseudo-distributed cluster.
> 4. Ran sample MR jobs and Tez example jobs like orderedwordcount successfully.
>
> Thank you Konstantin and others for this release.
>
> Regards,
> Kuhu
>
>
>
> On Thursday, August 3, 2017, 7:19:07 AM CDT, Sunil G <su...@apache.org> wrote:
>
>
> Thanks Konstantin
>
> +1 (binding)
>
> 1. Build tar ball from source package
> 2. Ran basic MR jobs and verified UI.
> 3. Enabled node labels and ran sleep job. Works fine.
> 4. Verified CLI commands related to node labels and its working fine.
> 5. RM WorkPreserving restart cases are also verified, and looks fine
>
> Thanks
> Sunil
>
>
>
> On Sun, Jul 30, 2017 at 4:59 AM Konstantin Shvachko <sh...@gmail.com>
> wrote:
>
>> Hi everybody,
>>
>> Here is the next release of Apache Hadoop 2.7 line. The previous stable
>> release 2.7.3 was available since 25 August, 2016.
>> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
>> critical bug fixes and major optimizations. See more details in Release
>> Note:
>> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>>
>> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>>
>> Please give it a try and vote on this thread. The vote will run for 5 days
>> ending 08/04/2017.
>>
>> Please note that my up to date public key are available from:
>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
>> Please don't forget to refresh the page if you've been there recently.
>> There are other place on Apache sites, which may contain my outdated key.
>>
>> Thanks,
>> --Konstantin
>>

---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Kuhu Shukla <ks...@yahoo-inc.com.INVALID>.
+1 (non-binding)

1. Verified signatures and digests.
2. Built source.
3. Installed on a pseudo-distributed cluster.
4. Ran sample MR jobs and Tez example jobs like orderedwordcount successfully.

Thank you Konstantin and others for this release.

Regards,
Kuhu



On Thursday, August 3, 2017, 7:19:07 AM CDT, Sunil G <su...@apache.org> wrote:


Thanks Konstantin

+1 (binding)

1. Build tar ball from source package
2. Ran basic MR jobs and verified UI.
3. Enabled node labels and ran sleep job. Works fine.
4. Verified CLI commands related to node labels and its working fine.
5. RM WorkPreserving restart cases are also verified, and looks fine

Thanks
Sunil



On Sun, Jul 30, 2017 at 4:59 AM Konstantin Shvachko <sh...@gmail.com>
wrote:

> Hi everybody,
>
> Here is the next release of Apache Hadoop 2.7 line. The previous stable
> release 2.7.3 was available since 25 August, 2016.
> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
> critical bug fixes and major optimizations. See more details in Release
> Note:
> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>
> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>
> Please give it a try and vote on this thread. The vote will run for 5 days
> ending 08/04/2017.
>
> Please note that my up to date public key are available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> Please don't forget to refresh the page if you've been there recently.
> There are other place on Apache sites, which may contain my outdated key.
>
> Thanks,
> --Konstantin
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Kuhu Shukla <ks...@yahoo-inc.com.INVALID>.
+1 (non-binding)

1. Verified signatures and digests.
2. Built source.
3. Installed on a pseudo-distributed cluster.
4. Ran sample MR jobs and Tez example jobs like orderedwordcount successfully.

Thank you Konstantin and others for this release.

Regards,
Kuhu



On Thursday, August 3, 2017, 7:19:07 AM CDT, Sunil G <su...@apache.org> wrote:


Thanks Konstantin

+1 (binding)

1. Build tar ball from source package
2. Ran basic MR jobs and verified UI.
3. Enabled node labels and ran sleep job. Works fine.
4. Verified CLI commands related to node labels and its working fine.
5. RM WorkPreserving restart cases are also verified, and looks fine

Thanks
Sunil



On Sun, Jul 30, 2017 at 4:59 AM Konstantin Shvachko <sh...@gmail.com>
wrote:

> Hi everybody,
>
> Here is the next release of Apache Hadoop 2.7 line. The previous stable
> release 2.7.3 was available since 25 August, 2016.
> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
> critical bug fixes and major optimizations. See more details in Release
> Note:
> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>
> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>
> Please give it a try and vote on this thread. The vote will run for 5 days
> ending 08/04/2017.
>
> Please note that my up to date public key are available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> Please don't forget to refresh the page if you've been there recently.
> There are other place on Apache sites, which may contain my outdated key.
>
> Thanks,
> --Konstantin
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Kuhu Shukla <ks...@yahoo-inc.com.INVALID>.
+1 (non-binding)

1. Verified signatures and digests.
2. Built source.
3. Installed on a pseudo-distributed cluster.
4. Ran sample MR jobs and Tez example jobs like orderedwordcount successfully.

Thank you Konstantin and others for this release.

Regards,
Kuhu



On Thursday, August 3, 2017, 7:19:07 AM CDT, Sunil G <su...@apache.org> wrote:


Thanks Konstantin

+1 (binding)

1. Build tar ball from source package
2. Ran basic MR jobs and verified UI.
3. Enabled node labels and ran sleep job. Works fine.
4. Verified CLI commands related to node labels and its working fine.
5. RM WorkPreserving restart cases are also verified, and looks fine

Thanks
Sunil



On Sun, Jul 30, 2017 at 4:59 AM Konstantin Shvachko <sh...@gmail.com>
wrote:

> Hi everybody,
>
> Here is the next release of Apache Hadoop 2.7 line. The previous stable
> release 2.7.3 was available since 25 August, 2016.
> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
> critical bug fixes and major optimizations. See more details in Release
> Note:
> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>
> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>
> Please give it a try and vote on this thread. The vote will run for 5 days
> ending 08/04/2017.
>
> Please note that my up to date public key are available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> Please don't forget to refresh the page if you've been there recently.
> There are other place on Apache sites, which may contain my outdated key.
>
> Thanks,
> --Konstantin
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Kuhu Shukla <ks...@yahoo-inc.com.INVALID>.
+1 (non-binding)

1. Verified signatures and digests.
2. Built source.
3. Installed on a pseudo-distributed cluster.
4. Ran sample MR jobs and Tez example jobs like orderedwordcount successfully.

Thank you Konstantin and others for this release.

Regards,
Kuhu



On Thursday, August 3, 2017, 7:19:07 AM CDT, Sunil G <su...@apache.org> wrote:


Thanks Konstantin

+1 (binding)

1. Build tar ball from source package
2. Ran basic MR jobs and verified UI.
3. Enabled node labels and ran sleep job. Works fine.
4. Verified CLI commands related to node labels and its working fine.
5. RM WorkPreserving restart cases are also verified, and looks fine

Thanks
Sunil



On Sun, Jul 30, 2017 at 4:59 AM Konstantin Shvachko <sh...@gmail.com>
wrote:

> Hi everybody,
>
> Here is the next release of Apache Hadoop 2.7 line. The previous stable
> release 2.7.3 was available since 25 August, 2016.
> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
> critical bug fixes and major optimizations. See more details in Release
> Note:
> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>
> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>
> Please give it a try and vote on this thread. The vote will run for 5 days
> ending 08/04/2017.
>
> Please note that my up to date public key are available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> Please don't forget to refresh the page if you've been there recently.
> There are other place on Apache sites, which may contain my outdated key.
>
> Thanks,
> --Konstantin
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Sunil G <su...@apache.org>.
Thanks Konstantin

+1 (binding)

1. Build tar ball from source package
2. Ran basic MR jobs and verified UI.
3. Enabled node labels and ran sleep job. Works fine.
4. Verified CLI commands related to node labels and its working fine.
5. RM WorkPreserving restart cases are also verified, and looks fine

Thanks
Sunil



On Sun, Jul 30, 2017 at 4:59 AM Konstantin Shvachko <sh...@gmail.com>
wrote:

> Hi everybody,
>
> Here is the next release of Apache Hadoop 2.7 line. The previous stable
> release 2.7.3 was available since 25 August, 2016.
> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
> critical bug fixes and major optimizations. See more details in Release
> Note:
> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>
> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>
> Please give it a try and vote on this thread. The vote will run for 5 days
> ending 08/04/2017.
>
> Please note that my up to date public key are available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> Please don't forget to refresh the page if you've been there recently.
> There are other place on Apache sites, which may contain my outdated key.
>
> Thanks,
> --Konstantin
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Hanisha Koneru <hk...@hortonworks.com>.
Hi Konstantin,

Thanks for preparing the 2.7.4-RC0 release.

- Built from source on Mac OS X 10.11.6 with Java 1.7.0_79
- Deployed both binary and built source to a pseudo cluster
- Passed the following sanity checks
    - Basic dfs operations
    - Wordcount


+1 (non-binding)


Thanks,
Hanisha








On 7/31/17, 1:56 PM, "John Zhuge" <jo...@gmail.com> wrote:

>Just confirmed that HADOOP-13707 does fix the NN servlet issuet in
>branch-2.7.
>
>On Mon, Jul 31, 2017 at 11:38 AM, Konstantin Shvachko <sh...@gmail.com>
>wrote:
>
>> Hi John,
>>
>> Thank you for checking and voting.
>> As far as I know test failures on 2.7.4 are intermittent. We have a jira
>> for that
>> https://issues.apache.org/jira/browse/HDFS-11985
>> but decided it should not block the release.
>> The "dr,who" thing is a configuration issue. This page may be helpful:
>> http://hadoop.apache.org/docs/stable/hadoop-hdfs-httpfs/ServerSetup.html
>>
>> Thanks,
>> --Konstantin
>>
>> On Sun, Jul 30, 2017 at 11:24 PM, John Zhuge <jo...@gmail.com> wrote:
>>
>>> Hi Konstantin,
>>>
>>> Thanks a lot for the effort to prepare the 2.7.4-RC0 release!
>>>
>>> +1 (non-binding)
>>>
>>>    - Verified checksums and signatures of all tarballs
>>>    - Built source with native, Java 1.8.0_131-b11 on Mac OS X 10.12.6
>>>    - Verified cloud connectors:
>>>       - All S3A integration tests
>>>    - Deployed both binary and built source to a pseudo cluster, passed
>>>    the following sanity tests in insecure, SSL, and SSL+Kerberos mode:
>>>       - HDFS basic and ACL
>>>       - DistCp basic
>>>       - MapReduce wordcount (only failed in SSL+Kerberos mode for binary
>>>       tarball, probably unrelated)
>>>       - KMS and HttpFS basic
>>>       - Balancer start/stop
>>>
>>> Shall we worry this test failures? Likely fixed by
>>> https://issues.apache.org/jira/browse/HADOOP-13707.
>>>
>>>    - Got “curl: (22) The requested URL returned error: 403 User dr.who
>>>    is unauthorized to access this page.” when accessing NameNode web servlet
>>>    /jmx, /conf, /logLevel, and /stacks. It passed in branch-2.8.
>>>
>>>
>>> On Sat, Jul 29, 2017 at 4:29 PM, Konstantin Shvachko <
>>> shv.hadoop@gmail.com> wrote:
>>>
>>>> Hi everybody,
>>>>
>>>> Here is the next release of Apache Hadoop 2.7 line. The previous stable
>>>> release 2.7.3 was available since 25 August, 2016.
>>>> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
>>>> critical bug fixes and major optimizations. See more details in Release
>>>> Note:
>>>> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>>>>
>>>> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>>>>
>>>> Please give it a try and vote on this thread. The vote will run for 5
>>>> days
>>>> ending 08/04/2017.
>>>>
>>>> Please note that my up to date public key are available from:
>>>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
>>>> Please don't forget to refresh the page if you've been there recently.
>>>> There are other place on Apache sites, which may contain my outdated key.
>>>>
>>>> Thanks,
>>>> --Konstantin
>>>>
>>>
>>>
>>>
>>> --
>>> John
>>>
>>
>>
>
>
>-- 
>John

---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Hanisha Koneru <hk...@hortonworks.com>.
Hi Konstantin,

Thanks for preparing the 2.7.4-RC0 release.

- Built from source on Mac OS X 10.11.6 with Java 1.7.0_79
- Deployed both binary and built source to a pseudo cluster
- Passed the following sanity checks
    - Basic dfs operations
    - Wordcount


+1 (non-binding)


Thanks,
Hanisha








On 7/31/17, 1:56 PM, "John Zhuge" <jo...@gmail.com> wrote:

>Just confirmed that HADOOP-13707 does fix the NN servlet issuet in
>branch-2.7.
>
>On Mon, Jul 31, 2017 at 11:38 AM, Konstantin Shvachko <sh...@gmail.com>
>wrote:
>
>> Hi John,
>>
>> Thank you for checking and voting.
>> As far as I know test failures on 2.7.4 are intermittent. We have a jira
>> for that
>> https://issues.apache.org/jira/browse/HDFS-11985
>> but decided it should not block the release.
>> The "dr,who" thing is a configuration issue. This page may be helpful:
>> http://hadoop.apache.org/docs/stable/hadoop-hdfs-httpfs/ServerSetup.html
>>
>> Thanks,
>> --Konstantin
>>
>> On Sun, Jul 30, 2017 at 11:24 PM, John Zhuge <jo...@gmail.com> wrote:
>>
>>> Hi Konstantin,
>>>
>>> Thanks a lot for the effort to prepare the 2.7.4-RC0 release!
>>>
>>> +1 (non-binding)
>>>
>>>    - Verified checksums and signatures of all tarballs
>>>    - Built source with native, Java 1.8.0_131-b11 on Mac OS X 10.12.6
>>>    - Verified cloud connectors:
>>>       - All S3A integration tests
>>>    - Deployed both binary and built source to a pseudo cluster, passed
>>>    the following sanity tests in insecure, SSL, and SSL+Kerberos mode:
>>>       - HDFS basic and ACL
>>>       - DistCp basic
>>>       - MapReduce wordcount (only failed in SSL+Kerberos mode for binary
>>>       tarball, probably unrelated)
>>>       - KMS and HttpFS basic
>>>       - Balancer start/stop
>>>
>>> Shall we worry this test failures? Likely fixed by
>>> https://issues.apache.org/jira/browse/HADOOP-13707.
>>>
>>>    - Got “curl: (22) The requested URL returned error: 403 User dr.who
>>>    is unauthorized to access this page.” when accessing NameNode web servlet
>>>    /jmx, /conf, /logLevel, and /stacks. It passed in branch-2.8.
>>>
>>>
>>> On Sat, Jul 29, 2017 at 4:29 PM, Konstantin Shvachko <
>>> shv.hadoop@gmail.com> wrote:
>>>
>>>> Hi everybody,
>>>>
>>>> Here is the next release of Apache Hadoop 2.7 line. The previous stable
>>>> release 2.7.3 was available since 25 August, 2016.
>>>> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
>>>> critical bug fixes and major optimizations. See more details in Release
>>>> Note:
>>>> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>>>>
>>>> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>>>>
>>>> Please give it a try and vote on this thread. The vote will run for 5
>>>> days
>>>> ending 08/04/2017.
>>>>
>>>> Please note that my up to date public key are available from:
>>>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
>>>> Please don't forget to refresh the page if you've been there recently.
>>>> There are other place on Apache sites, which may contain my outdated key.
>>>>
>>>> Thanks,
>>>> --Konstantin
>>>>
>>>
>>>
>>>
>>> --
>>> John
>>>
>>
>>
>
>
>-- 
>John

---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Hanisha Koneru <hk...@hortonworks.com>.
Hi Konstantin,

Thanks for preparing the 2.7.4-RC0 release.

- Built from source on Mac OS X 10.11.6 with Java 1.7.0_79
- Deployed both binary and built source to a pseudo cluster
- Passed the following sanity checks
    - Basic dfs operations
    - Wordcount


+1 (non-binding)


Thanks,
Hanisha








On 7/31/17, 1:56 PM, "John Zhuge" <jo...@gmail.com> wrote:

>Just confirmed that HADOOP-13707 does fix the NN servlet issuet in
>branch-2.7.
>
>On Mon, Jul 31, 2017 at 11:38 AM, Konstantin Shvachko <sh...@gmail.com>
>wrote:
>
>> Hi John,
>>
>> Thank you for checking and voting.
>> As far as I know test failures on 2.7.4 are intermittent. We have a jira
>> for that
>> https://issues.apache.org/jira/browse/HDFS-11985
>> but decided it should not block the release.
>> The "dr,who" thing is a configuration issue. This page may be helpful:
>> http://hadoop.apache.org/docs/stable/hadoop-hdfs-httpfs/ServerSetup.html
>>
>> Thanks,
>> --Konstantin
>>
>> On Sun, Jul 30, 2017 at 11:24 PM, John Zhuge <jo...@gmail.com> wrote:
>>
>>> Hi Konstantin,
>>>
>>> Thanks a lot for the effort to prepare the 2.7.4-RC0 release!
>>>
>>> +1 (non-binding)
>>>
>>>    - Verified checksums and signatures of all tarballs
>>>    - Built source with native, Java 1.8.0_131-b11 on Mac OS X 10.12.6
>>>    - Verified cloud connectors:
>>>       - All S3A integration tests
>>>    - Deployed both binary and built source to a pseudo cluster, passed
>>>    the following sanity tests in insecure, SSL, and SSL+Kerberos mode:
>>>       - HDFS basic and ACL
>>>       - DistCp basic
>>>       - MapReduce wordcount (only failed in SSL+Kerberos mode for binary
>>>       tarball, probably unrelated)
>>>       - KMS and HttpFS basic
>>>       - Balancer start/stop
>>>
>>> Shall we worry this test failures? Likely fixed by
>>> https://issues.apache.org/jira/browse/HADOOP-13707.
>>>
>>>    - Got “curl: (22) The requested URL returned error: 403 User dr.who
>>>    is unauthorized to access this page.” when accessing NameNode web servlet
>>>    /jmx, /conf, /logLevel, and /stacks. It passed in branch-2.8.
>>>
>>>
>>> On Sat, Jul 29, 2017 at 4:29 PM, Konstantin Shvachko <
>>> shv.hadoop@gmail.com> wrote:
>>>
>>>> Hi everybody,
>>>>
>>>> Here is the next release of Apache Hadoop 2.7 line. The previous stable
>>>> release 2.7.3 was available since 25 August, 2016.
>>>> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
>>>> critical bug fixes and major optimizations. See more details in Release
>>>> Note:
>>>> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>>>>
>>>> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>>>>
>>>> Please give it a try and vote on this thread. The vote will run for 5
>>>> days
>>>> ending 08/04/2017.
>>>>
>>>> Please note that my up to date public key are available from:
>>>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
>>>> Please don't forget to refresh the page if you've been there recently.
>>>> There are other place on Apache sites, which may contain my outdated key.
>>>>
>>>> Thanks,
>>>> --Konstantin
>>>>
>>>
>>>
>>>
>>> --
>>> John
>>>
>>
>>
>
>
>-- 
>John

---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Hanisha Koneru <hk...@hortonworks.com>.
Hi Konstantin,

Thanks for preparing the 2.7.4-RC0 release.

- Built from source on Mac OS X 10.11.6 with Java 1.7.0_79
- Deployed both binary and built source to a pseudo cluster
- Passed the following sanity checks
    - Basic dfs operations
    - Wordcount


+1 (non-binding)


Thanks,
Hanisha








On 7/31/17, 1:56 PM, "John Zhuge" <jo...@gmail.com> wrote:

>Just confirmed that HADOOP-13707 does fix the NN servlet issuet in
>branch-2.7.
>
>On Mon, Jul 31, 2017 at 11:38 AM, Konstantin Shvachko <sh...@gmail.com>
>wrote:
>
>> Hi John,
>>
>> Thank you for checking and voting.
>> As far as I know test failures on 2.7.4 are intermittent. We have a jira
>> for that
>> https://issues.apache.org/jira/browse/HDFS-11985
>> but decided it should not block the release.
>> The "dr,who" thing is a configuration issue. This page may be helpful:
>> http://hadoop.apache.org/docs/stable/hadoop-hdfs-httpfs/ServerSetup.html
>>
>> Thanks,
>> --Konstantin
>>
>> On Sun, Jul 30, 2017 at 11:24 PM, John Zhuge <jo...@gmail.com> wrote:
>>
>>> Hi Konstantin,
>>>
>>> Thanks a lot for the effort to prepare the 2.7.4-RC0 release!
>>>
>>> +1 (non-binding)
>>>
>>>    - Verified checksums and signatures of all tarballs
>>>    - Built source with native, Java 1.8.0_131-b11 on Mac OS X 10.12.6
>>>    - Verified cloud connectors:
>>>       - All S3A integration tests
>>>    - Deployed both binary and built source to a pseudo cluster, passed
>>>    the following sanity tests in insecure, SSL, and SSL+Kerberos mode:
>>>       - HDFS basic and ACL
>>>       - DistCp basic
>>>       - MapReduce wordcount (only failed in SSL+Kerberos mode for binary
>>>       tarball, probably unrelated)
>>>       - KMS and HttpFS basic
>>>       - Balancer start/stop
>>>
>>> Shall we worry this test failures? Likely fixed by
>>> https://issues.apache.org/jira/browse/HADOOP-13707.
>>>
>>>    - Got “curl: (22) The requested URL returned error: 403 User dr.who
>>>    is unauthorized to access this page.” when accessing NameNode web servlet
>>>    /jmx, /conf, /logLevel, and /stacks. It passed in branch-2.8.
>>>
>>>
>>> On Sat, Jul 29, 2017 at 4:29 PM, Konstantin Shvachko <
>>> shv.hadoop@gmail.com> wrote:
>>>
>>>> Hi everybody,
>>>>
>>>> Here is the next release of Apache Hadoop 2.7 line. The previous stable
>>>> release 2.7.3 was available since 25 August, 2016.
>>>> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
>>>> critical bug fixes and major optimizations. See more details in Release
>>>> Note:
>>>> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>>>>
>>>> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>>>>
>>>> Please give it a try and vote on this thread. The vote will run for 5
>>>> days
>>>> ending 08/04/2017.
>>>>
>>>> Please note that my up to date public key are available from:
>>>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
>>>> Please don't forget to refresh the page if you've been there recently.
>>>> There are other place on Apache sites, which may contain my outdated key.
>>>>
>>>> Thanks,
>>>> --Konstantin
>>>>
>>>
>>>
>>>
>>> --
>>> John
>>>
>>
>>
>
>
>-- 
>John

---------------------------------------------------------------------
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.7.4 (RC0)

Posted by John Zhuge <jo...@gmail.com>.
Just confirmed that HADOOP-13707 does fix the NN servlet issuet in
branch-2.7.

On Mon, Jul 31, 2017 at 11:38 AM, Konstantin Shvachko <sh...@gmail.com>
wrote:

> Hi John,
>
> Thank you for checking and voting.
> As far as I know test failures on 2.7.4 are intermittent. We have a jira
> for that
> https://issues.apache.org/jira/browse/HDFS-11985
> but decided it should not block the release.
> The "dr,who" thing is a configuration issue. This page may be helpful:
> http://hadoop.apache.org/docs/stable/hadoop-hdfs-httpfs/ServerSetup.html
>
> Thanks,
> --Konstantin
>
> On Sun, Jul 30, 2017 at 11:24 PM, John Zhuge <jo...@gmail.com> wrote:
>
>> Hi Konstantin,
>>
>> Thanks a lot for the effort to prepare the 2.7.4-RC0 release!
>>
>> +1 (non-binding)
>>
>>    - Verified checksums and signatures of all tarballs
>>    - Built source with native, Java 1.8.0_131-b11 on Mac OS X 10.12.6
>>    - Verified cloud connectors:
>>       - All S3A integration tests
>>    - Deployed both binary and built source to a pseudo cluster, passed
>>    the following sanity tests in insecure, SSL, and SSL+Kerberos mode:
>>       - HDFS basic and ACL
>>       - DistCp basic
>>       - MapReduce wordcount (only failed in SSL+Kerberos mode for binary
>>       tarball, probably unrelated)
>>       - KMS and HttpFS basic
>>       - Balancer start/stop
>>
>> Shall we worry this test failures? Likely fixed by
>> https://issues.apache.org/jira/browse/HADOOP-13707.
>>
>>    - Got “curl: (22) The requested URL returned error: 403 User dr.who
>>    is unauthorized to access this page.” when accessing NameNode web servlet
>>    /jmx, /conf, /logLevel, and /stacks. It passed in branch-2.8.
>>
>>
>> On Sat, Jul 29, 2017 at 4:29 PM, Konstantin Shvachko <
>> shv.hadoop@gmail.com> wrote:
>>
>>> Hi everybody,
>>>
>>> Here is the next release of Apache Hadoop 2.7 line. The previous stable
>>> release 2.7.3 was available since 25 August, 2016.
>>> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
>>> critical bug fixes and major optimizations. See more details in Release
>>> Note:
>>> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>>>
>>> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>>>
>>> Please give it a try and vote on this thread. The vote will run for 5
>>> days
>>> ending 08/04/2017.
>>>
>>> Please note that my up to date public key are available from:
>>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
>>> Please don't forget to refresh the page if you've been there recently.
>>> There are other place on Apache sites, which may contain my outdated key.
>>>
>>> Thanks,
>>> --Konstantin
>>>
>>
>>
>>
>> --
>> John
>>
>
>


-- 
John

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by John Zhuge <jo...@gmail.com>.
Just confirmed that HADOOP-13707 does fix the NN servlet issuet in
branch-2.7.

On Mon, Jul 31, 2017 at 11:38 AM, Konstantin Shvachko <sh...@gmail.com>
wrote:

> Hi John,
>
> Thank you for checking and voting.
> As far as I know test failures on 2.7.4 are intermittent. We have a jira
> for that
> https://issues.apache.org/jira/browse/HDFS-11985
> but decided it should not block the release.
> The "dr,who" thing is a configuration issue. This page may be helpful:
> http://hadoop.apache.org/docs/stable/hadoop-hdfs-httpfs/ServerSetup.html
>
> Thanks,
> --Konstantin
>
> On Sun, Jul 30, 2017 at 11:24 PM, John Zhuge <jo...@gmail.com> wrote:
>
>> Hi Konstantin,
>>
>> Thanks a lot for the effort to prepare the 2.7.4-RC0 release!
>>
>> +1 (non-binding)
>>
>>    - Verified checksums and signatures of all tarballs
>>    - Built source with native, Java 1.8.0_131-b11 on Mac OS X 10.12.6
>>    - Verified cloud connectors:
>>       - All S3A integration tests
>>    - Deployed both binary and built source to a pseudo cluster, passed
>>    the following sanity tests in insecure, SSL, and SSL+Kerberos mode:
>>       - HDFS basic and ACL
>>       - DistCp basic
>>       - MapReduce wordcount (only failed in SSL+Kerberos mode for binary
>>       tarball, probably unrelated)
>>       - KMS and HttpFS basic
>>       - Balancer start/stop
>>
>> Shall we worry this test failures? Likely fixed by
>> https://issues.apache.org/jira/browse/HADOOP-13707.
>>
>>    - Got “curl: (22) The requested URL returned error: 403 User dr.who
>>    is unauthorized to access this page.” when accessing NameNode web servlet
>>    /jmx, /conf, /logLevel, and /stacks. It passed in branch-2.8.
>>
>>
>> On Sat, Jul 29, 2017 at 4:29 PM, Konstantin Shvachko <
>> shv.hadoop@gmail.com> wrote:
>>
>>> Hi everybody,
>>>
>>> Here is the next release of Apache Hadoop 2.7 line. The previous stable
>>> release 2.7.3 was available since 25 August, 2016.
>>> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
>>> critical bug fixes and major optimizations. See more details in Release
>>> Note:
>>> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>>>
>>> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>>>
>>> Please give it a try and vote on this thread. The vote will run for 5
>>> days
>>> ending 08/04/2017.
>>>
>>> Please note that my up to date public key are available from:
>>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
>>> Please don't forget to refresh the page if you've been there recently.
>>> There are other place on Apache sites, which may contain my outdated key.
>>>
>>> Thanks,
>>> --Konstantin
>>>
>>
>>
>>
>> --
>> John
>>
>
>


-- 
John

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by John Zhuge <jo...@gmail.com>.
Just confirmed that HADOOP-13707 does fix the NN servlet issuet in
branch-2.7.

On Mon, Jul 31, 2017 at 11:38 AM, Konstantin Shvachko <sh...@gmail.com>
wrote:

> Hi John,
>
> Thank you for checking and voting.
> As far as I know test failures on 2.7.4 are intermittent. We have a jira
> for that
> https://issues.apache.org/jira/browse/HDFS-11985
> but decided it should not block the release.
> The "dr,who" thing is a configuration issue. This page may be helpful:
> http://hadoop.apache.org/docs/stable/hadoop-hdfs-httpfs/ServerSetup.html
>
> Thanks,
> --Konstantin
>
> On Sun, Jul 30, 2017 at 11:24 PM, John Zhuge <jo...@gmail.com> wrote:
>
>> Hi Konstantin,
>>
>> Thanks a lot for the effort to prepare the 2.7.4-RC0 release!
>>
>> +1 (non-binding)
>>
>>    - Verified checksums and signatures of all tarballs
>>    - Built source with native, Java 1.8.0_131-b11 on Mac OS X 10.12.6
>>    - Verified cloud connectors:
>>       - All S3A integration tests
>>    - Deployed both binary and built source to a pseudo cluster, passed
>>    the following sanity tests in insecure, SSL, and SSL+Kerberos mode:
>>       - HDFS basic and ACL
>>       - DistCp basic
>>       - MapReduce wordcount (only failed in SSL+Kerberos mode for binary
>>       tarball, probably unrelated)
>>       - KMS and HttpFS basic
>>       - Balancer start/stop
>>
>> Shall we worry this test failures? Likely fixed by
>> https://issues.apache.org/jira/browse/HADOOP-13707.
>>
>>    - Got “curl: (22) The requested URL returned error: 403 User dr.who
>>    is unauthorized to access this page.” when accessing NameNode web servlet
>>    /jmx, /conf, /logLevel, and /stacks. It passed in branch-2.8.
>>
>>
>> On Sat, Jul 29, 2017 at 4:29 PM, Konstantin Shvachko <
>> shv.hadoop@gmail.com> wrote:
>>
>>> Hi everybody,
>>>
>>> Here is the next release of Apache Hadoop 2.7 line. The previous stable
>>> release 2.7.3 was available since 25 August, 2016.
>>> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
>>> critical bug fixes and major optimizations. See more details in Release
>>> Note:
>>> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>>>
>>> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>>>
>>> Please give it a try and vote on this thread. The vote will run for 5
>>> days
>>> ending 08/04/2017.
>>>
>>> Please note that my up to date public key are available from:
>>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
>>> Please don't forget to refresh the page if you've been there recently.
>>> There are other place on Apache sites, which may contain my outdated key.
>>>
>>> Thanks,
>>> --Konstantin
>>>
>>
>>
>>
>> --
>> John
>>
>
>


-- 
John

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by John Zhuge <jo...@gmail.com>.
Just confirmed that HADOOP-13707 does fix the NN servlet issuet in
branch-2.7.

On Mon, Jul 31, 2017 at 11:38 AM, Konstantin Shvachko <sh...@gmail.com>
wrote:

> Hi John,
>
> Thank you for checking and voting.
> As far as I know test failures on 2.7.4 are intermittent. We have a jira
> for that
> https://issues.apache.org/jira/browse/HDFS-11985
> but decided it should not block the release.
> The "dr,who" thing is a configuration issue. This page may be helpful:
> http://hadoop.apache.org/docs/stable/hadoop-hdfs-httpfs/ServerSetup.html
>
> Thanks,
> --Konstantin
>
> On Sun, Jul 30, 2017 at 11:24 PM, John Zhuge <jo...@gmail.com> wrote:
>
>> Hi Konstantin,
>>
>> Thanks a lot for the effort to prepare the 2.7.4-RC0 release!
>>
>> +1 (non-binding)
>>
>>    - Verified checksums and signatures of all tarballs
>>    - Built source with native, Java 1.8.0_131-b11 on Mac OS X 10.12.6
>>    - Verified cloud connectors:
>>       - All S3A integration tests
>>    - Deployed both binary and built source to a pseudo cluster, passed
>>    the following sanity tests in insecure, SSL, and SSL+Kerberos mode:
>>       - HDFS basic and ACL
>>       - DistCp basic
>>       - MapReduce wordcount (only failed in SSL+Kerberos mode for binary
>>       tarball, probably unrelated)
>>       - KMS and HttpFS basic
>>       - Balancer start/stop
>>
>> Shall we worry this test failures? Likely fixed by
>> https://issues.apache.org/jira/browse/HADOOP-13707.
>>
>>    - Got “curl: (22) The requested URL returned error: 403 User dr.who
>>    is unauthorized to access this page.” when accessing NameNode web servlet
>>    /jmx, /conf, /logLevel, and /stacks. It passed in branch-2.8.
>>
>>
>> On Sat, Jul 29, 2017 at 4:29 PM, Konstantin Shvachko <
>> shv.hadoop@gmail.com> wrote:
>>
>>> Hi everybody,
>>>
>>> Here is the next release of Apache Hadoop 2.7 line. The previous stable
>>> release 2.7.3 was available since 25 August, 2016.
>>> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
>>> critical bug fixes and major optimizations. See more details in Release
>>> Note:
>>> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>>>
>>> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>>>
>>> Please give it a try and vote on this thread. The vote will run for 5
>>> days
>>> ending 08/04/2017.
>>>
>>> Please note that my up to date public key are available from:
>>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
>>> Please don't forget to refresh the page if you've been there recently.
>>> There are other place on Apache sites, which may contain my outdated key.
>>>
>>> Thanks,
>>> --Konstantin
>>>
>>
>>
>>
>> --
>> John
>>
>
>


-- 
John

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Konstantin Shvachko <sh...@gmail.com>.
Hi John,

Thank you for checking and voting.
As far as I know test failures on 2.7.4 are intermittent. We have a jira
for that
https://issues.apache.org/jira/browse/HDFS-11985
but decided it should not block the release.
The "dr,who" thing is a configuration issue. This page may be helpful:
http://hadoop.apache.org/docs/stable/hadoop-hdfs-httpfs/ServerSetup.html

Thanks,
--Konstantin

On Sun, Jul 30, 2017 at 11:24 PM, John Zhuge <jo...@gmail.com> wrote:

> Hi Konstantin,
>
> Thanks a lot for the effort to prepare the 2.7.4-RC0 release!
>
> +1 (non-binding)
>
>    - Verified checksums and signatures of all tarballs
>    - Built source with native, Java 1.8.0_131-b11 on Mac OS X 10.12.6
>    - Verified cloud connectors:
>       - All S3A integration tests
>    - Deployed both binary and built source to a pseudo cluster, passed
>    the following sanity tests in insecure, SSL, and SSL+Kerberos mode:
>       - HDFS basic and ACL
>       - DistCp basic
>       - MapReduce wordcount (only failed in SSL+Kerberos mode for binary
>       tarball, probably unrelated)
>       - KMS and HttpFS basic
>       - Balancer start/stop
>
> Shall we worry this test failures? Likely fixed by
> https://issues.apache.org/jira/browse/HADOOP-13707.
>
>    - Got “curl: (22) The requested URL returned error: 403 User dr.who is
>    unauthorized to access this page.” when accessing NameNode web servlet
>    /jmx, /conf, /logLevel, and /stacks. It passed in branch-2.8.
>
>
> On Sat, Jul 29, 2017 at 4:29 PM, Konstantin Shvachko <shv.hadoop@gmail.com
> > wrote:
>
>> Hi everybody,
>>
>> Here is the next release of Apache Hadoop 2.7 line. The previous stable
>> release 2.7.3 was available since 25 August, 2016.
>> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
>> critical bug fixes and major optimizations. See more details in Release
>> Note:
>> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>>
>> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>>
>> Please give it a try and vote on this thread. The vote will run for 5 days
>> ending 08/04/2017.
>>
>> Please note that my up to date public key are available from:
>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
>> Please don't forget to refresh the page if you've been there recently.
>> There are other place on Apache sites, which may contain my outdated key.
>>
>> Thanks,
>> --Konstantin
>>
>
>
>
> --
> John
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Konstantin Shvachko <sh...@gmail.com>.
Hi John,

Thank you for checking and voting.
As far as I know test failures on 2.7.4 are intermittent. We have a jira
for that
https://issues.apache.org/jira/browse/HDFS-11985
but decided it should not block the release.
The "dr,who" thing is a configuration issue. This page may be helpful:
http://hadoop.apache.org/docs/stable/hadoop-hdfs-httpfs/ServerSetup.html

Thanks,
--Konstantin

On Sun, Jul 30, 2017 at 11:24 PM, John Zhuge <jo...@gmail.com> wrote:

> Hi Konstantin,
>
> Thanks a lot for the effort to prepare the 2.7.4-RC0 release!
>
> +1 (non-binding)
>
>    - Verified checksums and signatures of all tarballs
>    - Built source with native, Java 1.8.0_131-b11 on Mac OS X 10.12.6
>    - Verified cloud connectors:
>       - All S3A integration tests
>    - Deployed both binary and built source to a pseudo cluster, passed
>    the following sanity tests in insecure, SSL, and SSL+Kerberos mode:
>       - HDFS basic and ACL
>       - DistCp basic
>       - MapReduce wordcount (only failed in SSL+Kerberos mode for binary
>       tarball, probably unrelated)
>       - KMS and HttpFS basic
>       - Balancer start/stop
>
> Shall we worry this test failures? Likely fixed by
> https://issues.apache.org/jira/browse/HADOOP-13707.
>
>    - Got “curl: (22) The requested URL returned error: 403 User dr.who is
>    unauthorized to access this page.” when accessing NameNode web servlet
>    /jmx, /conf, /logLevel, and /stacks. It passed in branch-2.8.
>
>
> On Sat, Jul 29, 2017 at 4:29 PM, Konstantin Shvachko <shv.hadoop@gmail.com
> > wrote:
>
>> Hi everybody,
>>
>> Here is the next release of Apache Hadoop 2.7 line. The previous stable
>> release 2.7.3 was available since 25 August, 2016.
>> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
>> critical bug fixes and major optimizations. See more details in Release
>> Note:
>> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>>
>> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>>
>> Please give it a try and vote on this thread. The vote will run for 5 days
>> ending 08/04/2017.
>>
>> Please note that my up to date public key are available from:
>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
>> Please don't forget to refresh the page if you've been there recently.
>> There are other place on Apache sites, which may contain my outdated key.
>>
>> Thanks,
>> --Konstantin
>>
>
>
>
> --
> John
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Konstantin Shvachko <sh...@gmail.com>.
Hi John,

Thank you for checking and voting.
As far as I know test failures on 2.7.4 are intermittent. We have a jira
for that
https://issues.apache.org/jira/browse/HDFS-11985
but decided it should not block the release.
The "dr,who" thing is a configuration issue. This page may be helpful:
http://hadoop.apache.org/docs/stable/hadoop-hdfs-httpfs/ServerSetup.html

Thanks,
--Konstantin

On Sun, Jul 30, 2017 at 11:24 PM, John Zhuge <jo...@gmail.com> wrote:

> Hi Konstantin,
>
> Thanks a lot for the effort to prepare the 2.7.4-RC0 release!
>
> +1 (non-binding)
>
>    - Verified checksums and signatures of all tarballs
>    - Built source with native, Java 1.8.0_131-b11 on Mac OS X 10.12.6
>    - Verified cloud connectors:
>       - All S3A integration tests
>    - Deployed both binary and built source to a pseudo cluster, passed
>    the following sanity tests in insecure, SSL, and SSL+Kerberos mode:
>       - HDFS basic and ACL
>       - DistCp basic
>       - MapReduce wordcount (only failed in SSL+Kerberos mode for binary
>       tarball, probably unrelated)
>       - KMS and HttpFS basic
>       - Balancer start/stop
>
> Shall we worry this test failures? Likely fixed by
> https://issues.apache.org/jira/browse/HADOOP-13707.
>
>    - Got “curl: (22) The requested URL returned error: 403 User dr.who is
>    unauthorized to access this page.” when accessing NameNode web servlet
>    /jmx, /conf, /logLevel, and /stacks. It passed in branch-2.8.
>
>
> On Sat, Jul 29, 2017 at 4:29 PM, Konstantin Shvachko <shv.hadoop@gmail.com
> > wrote:
>
>> Hi everybody,
>>
>> Here is the next release of Apache Hadoop 2.7 line. The previous stable
>> release 2.7.3 was available since 25 August, 2016.
>> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
>> critical bug fixes and major optimizations. See more details in Release
>> Note:
>> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>>
>> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>>
>> Please give it a try and vote on this thread. The vote will run for 5 days
>> ending 08/04/2017.
>>
>> Please note that my up to date public key are available from:
>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
>> Please don't forget to refresh the page if you've been there recently.
>> There are other place on Apache sites, which may contain my outdated key.
>>
>> Thanks,
>> --Konstantin
>>
>
>
>
> --
> John
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Konstantin Shvachko <sh...@gmail.com>.
Hi John,

Thank you for checking and voting.
As far as I know test failures on 2.7.4 are intermittent. We have a jira
for that
https://issues.apache.org/jira/browse/HDFS-11985
but decided it should not block the release.
The "dr,who" thing is a configuration issue. This page may be helpful:
http://hadoop.apache.org/docs/stable/hadoop-hdfs-httpfs/ServerSetup.html

Thanks,
--Konstantin

On Sun, Jul 30, 2017 at 11:24 PM, John Zhuge <jo...@gmail.com> wrote:

> Hi Konstantin,
>
> Thanks a lot for the effort to prepare the 2.7.4-RC0 release!
>
> +1 (non-binding)
>
>    - Verified checksums and signatures of all tarballs
>    - Built source with native, Java 1.8.0_131-b11 on Mac OS X 10.12.6
>    - Verified cloud connectors:
>       - All S3A integration tests
>    - Deployed both binary and built source to a pseudo cluster, passed
>    the following sanity tests in insecure, SSL, and SSL+Kerberos mode:
>       - HDFS basic and ACL
>       - DistCp basic
>       - MapReduce wordcount (only failed in SSL+Kerberos mode for binary
>       tarball, probably unrelated)
>       - KMS and HttpFS basic
>       - Balancer start/stop
>
> Shall we worry this test failures? Likely fixed by
> https://issues.apache.org/jira/browse/HADOOP-13707.
>
>    - Got “curl: (22) The requested URL returned error: 403 User dr.who is
>    unauthorized to access this page.” when accessing NameNode web servlet
>    /jmx, /conf, /logLevel, and /stacks. It passed in branch-2.8.
>
>
> On Sat, Jul 29, 2017 at 4:29 PM, Konstantin Shvachko <shv.hadoop@gmail.com
> > wrote:
>
>> Hi everybody,
>>
>> Here is the next release of Apache Hadoop 2.7 line. The previous stable
>> release 2.7.3 was available since 25 August, 2016.
>> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
>> critical bug fixes and major optimizations. See more details in Release
>> Note:
>> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>>
>> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>>
>> Please give it a try and vote on this thread. The vote will run for 5 days
>> ending 08/04/2017.
>>
>> Please note that my up to date public key are available from:
>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
>> Please don't forget to refresh the page if you've been there recently.
>> There are other place on Apache sites, which may contain my outdated key.
>>
>> Thanks,
>> --Konstantin
>>
>
>
>
> --
> John
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by John Zhuge <jo...@gmail.com>.
Hi Konstantin,

Thanks a lot for the effort to prepare the 2.7.4-RC0 release!

+1 (non-binding)

   - Verified checksums and signatures of all tarballs
   - Built source with native, Java 1.8.0_131-b11 on Mac OS X 10.12.6
   - Verified cloud connectors:
      - All S3A integration tests
   - Deployed both binary and built source to a pseudo cluster, passed the
   following sanity tests in insecure, SSL, and SSL+Kerberos mode:
      - HDFS basic and ACL
      - DistCp basic
      - MapReduce wordcount (only failed in SSL+Kerberos mode for binary
      tarball, probably unrelated)
      - KMS and HttpFS basic
      - Balancer start/stop

Shall we worry this test failures? Likely fixed by
https://issues.apache.org/jira/browse/HADOOP-13707.

   - Got “curl: (22) The requested URL returned error: 403 User dr.who is
   unauthorized to access this page.” when accessing NameNode web servlet
   /jmx, /conf, /logLevel, and /stacks. It passed in branch-2.8.


On Sat, Jul 29, 2017 at 4:29 PM, Konstantin Shvachko <sh...@gmail.com>
wrote:

> Hi everybody,
>
> Here is the next release of Apache Hadoop 2.7 line. The previous stable
> release 2.7.3 was available since 25 August, 2016.
> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
> critical bug fixes and major optimizations. See more details in Release
> Note:
> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>
> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>
> Please give it a try and vote on this thread. The vote will run for 5 days
> ending 08/04/2017.
>
> Please note that my up to date public key are available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> Please don't forget to refresh the page if you've been there recently.
> There are other place on Apache sites, which may contain my outdated key.
>
> Thanks,
> --Konstantin
>



-- 
John

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Jason Lowe <jl...@yahoo-inc.com.INVALID>.
Thanks for driving the 2.7.4 release!
+1 (binding)
- Verified signatures and digests- Successfully built from source including native- Deployed to a single-node cluster and ran sample MapReduce jobs
Jason 

    On Saturday, July 29, 2017 6:29 PM, Konstantin Shvachko <sh...@gmail.com> wrote:
 

 Hi everybody,

Here is the next release of Apache Hadoop 2.7 line. The previous stable
release 2.7.3 was available since 25 August, 2016.
Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
critical bug fixes and major optimizations. See more details in Release
Note:
http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html

The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/

Please give it a try and vote on this thread. The vote will run for 5 days
ending 08/04/2017.

Please note that my up to date public key are available from:
https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
Please don't forget to refresh the page if you've been there recently.
There are other place on Apache sites, which may contain my outdated key.

Thanks,
--Konstantin


   

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Eric Badger <eb...@yahoo-inc.com.INVALID>.
- Verified all checksums signatures
- Built from src on macOS 10.12.6 with Java 1.8.0u65
- Deployed single node pseudo cluster
- Successfully ran sleep and pi jobs
- Navigated the various UIs 

+1 (non-binding)

Thanks,

Eric


On Wednesday, August 2, 2017 12:31 PM, Chris Douglas <cd...@apache.org> wrote:



On Wed, Aug 2, 2017 at 12:02 AM, Zhe Zhang <zh...@apache.org> wrote:
> Quick question for Chris: was your +1 for the RC, or to support
> Konstantin's statement regarding packaging?

For Konstantin's statement. I haven't had a chance to look through the
RC yet, but it's on my list. -C

> On Mon, Jul 31, 2017 at 3:56 PM Chris Douglas <cd...@apache.org> wrote:
>
>> On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
>> <sh...@gmail.com> wrote:
>> > For the packaging, here is the exact phrasing from the sited
>> release-policy
>> > document relevant to binaries:
>> > "As a convenience to users that might not have the appropriate tools to
>> > build a compiled version of the source, binary/bytecode packages MAY be
>> > distributed alongside official Apache releases. In all such cases, the
>> > binary/bytecode package MUST have the same version number as the source
>> > release and MUST only add binary/bytecode files that are the result of
>> > compiling that version of the source code release and its dependencies."
>> > I don't think my binary package violates any of these.
>>
>> +1 The PMC VOTE applies to source code, only. If someone wants to
>> rebuild the binary tarball with native libs and replace this one,
>> that's fine.
>>
>> My reading of the above is that source code must be distributed with
>> binaries, not that we omit the source code from binary releases... -C
>>
>> > But I'll upload an additional tar.gz with native bits and no src, as you
>> > guys requested.
>> > Will keep it as RC0 as there is no source code change and it comes from
>> the
>> > same build.
>> > Hope this is satisfactory.
>> >
>> > Thanks,
>> > --Konstantin
>> >
>> > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <an...@cloudera.com>
>> > wrote:
>> >
>> >> I agree with Brahma on the two issues flagged (having src in the binary
>> >> tarball, missing native libs). These are regressions from prior
>> releases.
>> >>
>> >> As an aside, "we release binaries as a convenience" doesn't relax the
>> >> quality bar. The binaries are linked on our website and distributed
>> through
>> >> official Apache channels. They have to adhere to Apache release
>> >> requirements. And, most users consume our work via Maven dependencies,
>> >> which are binary artifacts.
>> >>
>> >> http://www.apache.org/legal/release-policy.html goes into this in more
>> >> detail. A release must minimally include source packages, and can also
>> >> include binary artifacts.
>> >>
>> >> Best,
>> >> Andrew
>> >>
>> >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
>> >> shv.hadoop@gmail.com> wrote:
>> >>
>> >>> To avoid any confusion in this regard. I built RC0 manually in
>> compliance
>> >>> with Apache release policy
>> >>> http://www.apache.org/legal/release-policy.html
>> >>> I edited the HowToReleasePreDSBCR page to make sure people don't use
>> >>> Jenkins option for building.
>> >>>
>> >>> A side note. This particular build is broken anyways, so no worries
>> there.
>> >>> I think though it would be useful to have it working for testing and
>> as a
>> >>> packaging standard.
>> >>>
>> >>> Thanks,
>> >>> --Konstantin
>> >>>
>> >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
>> >>> aw@effectivemachines.com
>> >>> > wrote:
>> >>>
>> >>> >
>> >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
>> >>> shv.hadoop@gmail.com>
>> >>> > wrote:
>> >>> > >
>> >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
>> >>> >
>> >>> >         FYI:
>> >>> >
>> >>> >                 If you are using ASF Jenkins to create an ASF release
>> >>> > artifact, it's pretty much an automatic vote failure as any such
>> >>> release is
>> >>> > in violation of ASF policy.
>> >>> >
>> >>> >
>> >>>
>> >>
>> >>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>
>> --
> Zhe Zhang
> Apache Hadoop Committer
> http://zhe-thoughts.github.io/about/ | @oldcap


---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Eric Badger <eb...@yahoo-inc.com.INVALID>.
- Verified all checksums signatures
- Built from src on macOS 10.12.6 with Java 1.8.0u65
- Deployed single node pseudo cluster
- Successfully ran sleep and pi jobs
- Navigated the various UIs 

+1 (non-binding)

Thanks,

Eric


On Wednesday, August 2, 2017 12:31 PM, Chris Douglas <cd...@apache.org> wrote:



On Wed, Aug 2, 2017 at 12:02 AM, Zhe Zhang <zh...@apache.org> wrote:
> Quick question for Chris: was your +1 for the RC, or to support
> Konstantin's statement regarding packaging?

For Konstantin's statement. I haven't had a chance to look through the
RC yet, but it's on my list. -C

> On Mon, Jul 31, 2017 at 3:56 PM Chris Douglas <cd...@apache.org> wrote:
>
>> On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
>> <sh...@gmail.com> wrote:
>> > For the packaging, here is the exact phrasing from the sited
>> release-policy
>> > document relevant to binaries:
>> > "As a convenience to users that might not have the appropriate tools to
>> > build a compiled version of the source, binary/bytecode packages MAY be
>> > distributed alongside official Apache releases. In all such cases, the
>> > binary/bytecode package MUST have the same version number as the source
>> > release and MUST only add binary/bytecode files that are the result of
>> > compiling that version of the source code release and its dependencies."
>> > I don't think my binary package violates any of these.
>>
>> +1 The PMC VOTE applies to source code, only. If someone wants to
>> rebuild the binary tarball with native libs and replace this one,
>> that's fine.
>>
>> My reading of the above is that source code must be distributed with
>> binaries, not that we omit the source code from binary releases... -C
>>
>> > But I'll upload an additional tar.gz with native bits and no src, as you
>> > guys requested.
>> > Will keep it as RC0 as there is no source code change and it comes from
>> the
>> > same build.
>> > Hope this is satisfactory.
>> >
>> > Thanks,
>> > --Konstantin
>> >
>> > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <an...@cloudera.com>
>> > wrote:
>> >
>> >> I agree with Brahma on the two issues flagged (having src in the binary
>> >> tarball, missing native libs). These are regressions from prior
>> releases.
>> >>
>> >> As an aside, "we release binaries as a convenience" doesn't relax the
>> >> quality bar. The binaries are linked on our website and distributed
>> through
>> >> official Apache channels. They have to adhere to Apache release
>> >> requirements. And, most users consume our work via Maven dependencies,
>> >> which are binary artifacts.
>> >>
>> >> http://www.apache.org/legal/release-policy.html goes into this in more
>> >> detail. A release must minimally include source packages, and can also
>> >> include binary artifacts.
>> >>
>> >> Best,
>> >> Andrew
>> >>
>> >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
>> >> shv.hadoop@gmail.com> wrote:
>> >>
>> >>> To avoid any confusion in this regard. I built RC0 manually in
>> compliance
>> >>> with Apache release policy
>> >>> http://www.apache.org/legal/release-policy.html
>> >>> I edited the HowToReleasePreDSBCR page to make sure people don't use
>> >>> Jenkins option for building.
>> >>>
>> >>> A side note. This particular build is broken anyways, so no worries
>> there.
>> >>> I think though it would be useful to have it working for testing and
>> as a
>> >>> packaging standard.
>> >>>
>> >>> Thanks,
>> >>> --Konstantin
>> >>>
>> >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
>> >>> aw@effectivemachines.com
>> >>> > wrote:
>> >>>
>> >>> >
>> >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
>> >>> shv.hadoop@gmail.com>
>> >>> > wrote:
>> >>> > >
>> >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
>> >>> >
>> >>> >         FYI:
>> >>> >
>> >>> >                 If you are using ASF Jenkins to create an ASF release
>> >>> > artifact, it's pretty much an automatic vote failure as any such
>> >>> release is
>> >>> > in violation of ASF policy.
>> >>> >
>> >>> >
>> >>>
>> >>
>> >>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>
>> --
> Zhe Zhang
> Apache Hadoop Committer
> http://zhe-thoughts.github.io/about/ | @oldcap


---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Eric Badger <eb...@yahoo-inc.com.INVALID>.
- Verified all checksums signatures
- Built from src on macOS 10.12.6 with Java 1.8.0u65
- Deployed single node pseudo cluster
- Successfully ran sleep and pi jobs
- Navigated the various UIs 

+1 (non-binding)

Thanks,

Eric


On Wednesday, August 2, 2017 12:31 PM, Chris Douglas <cd...@apache.org> wrote:



On Wed, Aug 2, 2017 at 12:02 AM, Zhe Zhang <zh...@apache.org> wrote:
> Quick question for Chris: was your +1 for the RC, or to support
> Konstantin's statement regarding packaging?

For Konstantin's statement. I haven't had a chance to look through the
RC yet, but it's on my list. -C

> On Mon, Jul 31, 2017 at 3:56 PM Chris Douglas <cd...@apache.org> wrote:
>
>> On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
>> <sh...@gmail.com> wrote:
>> > For the packaging, here is the exact phrasing from the sited
>> release-policy
>> > document relevant to binaries:
>> > "As a convenience to users that might not have the appropriate tools to
>> > build a compiled version of the source, binary/bytecode packages MAY be
>> > distributed alongside official Apache releases. In all such cases, the
>> > binary/bytecode package MUST have the same version number as the source
>> > release and MUST only add binary/bytecode files that are the result of
>> > compiling that version of the source code release and its dependencies."
>> > I don't think my binary package violates any of these.
>>
>> +1 The PMC VOTE applies to source code, only. If someone wants to
>> rebuild the binary tarball with native libs and replace this one,
>> that's fine.
>>
>> My reading of the above is that source code must be distributed with
>> binaries, not that we omit the source code from binary releases... -C
>>
>> > But I'll upload an additional tar.gz with native bits and no src, as you
>> > guys requested.
>> > Will keep it as RC0 as there is no source code change and it comes from
>> the
>> > same build.
>> > Hope this is satisfactory.
>> >
>> > Thanks,
>> > --Konstantin
>> >
>> > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <an...@cloudera.com>
>> > wrote:
>> >
>> >> I agree with Brahma on the two issues flagged (having src in the binary
>> >> tarball, missing native libs). These are regressions from prior
>> releases.
>> >>
>> >> As an aside, "we release binaries as a convenience" doesn't relax the
>> >> quality bar. The binaries are linked on our website and distributed
>> through
>> >> official Apache channels. They have to adhere to Apache release
>> >> requirements. And, most users consume our work via Maven dependencies,
>> >> which are binary artifacts.
>> >>
>> >> http://www.apache.org/legal/release-policy.html goes into this in more
>> >> detail. A release must minimally include source packages, and can also
>> >> include binary artifacts.
>> >>
>> >> Best,
>> >> Andrew
>> >>
>> >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
>> >> shv.hadoop@gmail.com> wrote:
>> >>
>> >>> To avoid any confusion in this regard. I built RC0 manually in
>> compliance
>> >>> with Apache release policy
>> >>> http://www.apache.org/legal/release-policy.html
>> >>> I edited the HowToReleasePreDSBCR page to make sure people don't use
>> >>> Jenkins option for building.
>> >>>
>> >>> A side note. This particular build is broken anyways, so no worries
>> there.
>> >>> I think though it would be useful to have it working for testing and
>> as a
>> >>> packaging standard.
>> >>>
>> >>> Thanks,
>> >>> --Konstantin
>> >>>
>> >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
>> >>> aw@effectivemachines.com
>> >>> > wrote:
>> >>>
>> >>> >
>> >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
>> >>> shv.hadoop@gmail.com>
>> >>> > wrote:
>> >>> > >
>> >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
>> >>> >
>> >>> >         FYI:
>> >>> >
>> >>> >                 If you are using ASF Jenkins to create an ASF release
>> >>> > artifact, it's pretty much an automatic vote failure as any such
>> >>> release is
>> >>> > in violation of ASF policy.
>> >>> >
>> >>> >
>> >>>
>> >>
>> >>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>
>> --
> Zhe Zhang
> Apache Hadoop Committer
> http://zhe-thoughts.github.io/about/ | @oldcap


---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Eric Badger <eb...@yahoo-inc.com.INVALID>.
- Verified all checksums signatures
- Built from src on macOS 10.12.6 with Java 1.8.0u65
- Deployed single node pseudo cluster
- Successfully ran sleep and pi jobs
- Navigated the various UIs 

+1 (non-binding)

Thanks,

Eric


On Wednesday, August 2, 2017 12:31 PM, Chris Douglas <cd...@apache.org> wrote:



On Wed, Aug 2, 2017 at 12:02 AM, Zhe Zhang <zh...@apache.org> wrote:
> Quick question for Chris: was your +1 for the RC, or to support
> Konstantin's statement regarding packaging?

For Konstantin's statement. I haven't had a chance to look through the
RC yet, but it's on my list. -C

> On Mon, Jul 31, 2017 at 3:56 PM Chris Douglas <cd...@apache.org> wrote:
>
>> On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
>> <sh...@gmail.com> wrote:
>> > For the packaging, here is the exact phrasing from the sited
>> release-policy
>> > document relevant to binaries:
>> > "As a convenience to users that might not have the appropriate tools to
>> > build a compiled version of the source, binary/bytecode packages MAY be
>> > distributed alongside official Apache releases. In all such cases, the
>> > binary/bytecode package MUST have the same version number as the source
>> > release and MUST only add binary/bytecode files that are the result of
>> > compiling that version of the source code release and its dependencies."
>> > I don't think my binary package violates any of these.
>>
>> +1 The PMC VOTE applies to source code, only. If someone wants to
>> rebuild the binary tarball with native libs and replace this one,
>> that's fine.
>>
>> My reading of the above is that source code must be distributed with
>> binaries, not that we omit the source code from binary releases... -C
>>
>> > But I'll upload an additional tar.gz with native bits and no src, as you
>> > guys requested.
>> > Will keep it as RC0 as there is no source code change and it comes from
>> the
>> > same build.
>> > Hope this is satisfactory.
>> >
>> > Thanks,
>> > --Konstantin
>> >
>> > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <an...@cloudera.com>
>> > wrote:
>> >
>> >> I agree with Brahma on the two issues flagged (having src in the binary
>> >> tarball, missing native libs). These are regressions from prior
>> releases.
>> >>
>> >> As an aside, "we release binaries as a convenience" doesn't relax the
>> >> quality bar. The binaries are linked on our website and distributed
>> through
>> >> official Apache channels. They have to adhere to Apache release
>> >> requirements. And, most users consume our work via Maven dependencies,
>> >> which are binary artifacts.
>> >>
>> >> http://www.apache.org/legal/release-policy.html goes into this in more
>> >> detail. A release must minimally include source packages, and can also
>> >> include binary artifacts.
>> >>
>> >> Best,
>> >> Andrew
>> >>
>> >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
>> >> shv.hadoop@gmail.com> wrote:
>> >>
>> >>> To avoid any confusion in this regard. I built RC0 manually in
>> compliance
>> >>> with Apache release policy
>> >>> http://www.apache.org/legal/release-policy.html
>> >>> I edited the HowToReleasePreDSBCR page to make sure people don't use
>> >>> Jenkins option for building.
>> >>>
>> >>> A side note. This particular build is broken anyways, so no worries
>> there.
>> >>> I think though it would be useful to have it working for testing and
>> as a
>> >>> packaging standard.
>> >>>
>> >>> Thanks,
>> >>> --Konstantin
>> >>>
>> >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
>> >>> aw@effectivemachines.com
>> >>> > wrote:
>> >>>
>> >>> >
>> >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
>> >>> shv.hadoop@gmail.com>
>> >>> > wrote:
>> >>> > >
>> >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
>> >>> >
>> >>> >         FYI:
>> >>> >
>> >>> >                 If you are using ASF Jenkins to create an ASF release
>> >>> > artifact, it's pretty much an automatic vote failure as any such
>> >>> release is
>> >>> > in violation of ASF policy.
>> >>> >
>> >>> >
>> >>>
>> >>
>> >>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>
>> --
> Zhe Zhang
> Apache Hadoop Committer
> http://zhe-thoughts.github.io/about/ | @oldcap


---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Chris Douglas <cd...@apache.org>.
On Wed, Aug 2, 2017 at 12:02 AM, Zhe Zhang <zh...@apache.org> wrote:
> Quick question for Chris: was your +1 for the RC, or to support
> Konstantin's statement regarding packaging?

For Konstantin's statement. I haven't had a chance to look through the
RC yet, but it's on my list. -C

> On Mon, Jul 31, 2017 at 3:56 PM Chris Douglas <cd...@apache.org> wrote:
>
>> On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
>> <sh...@gmail.com> wrote:
>> > For the packaging, here is the exact phrasing from the sited
>> release-policy
>> > document relevant to binaries:
>> > "As a convenience to users that might not have the appropriate tools to
>> > build a compiled version of the source, binary/bytecode packages MAY be
>> > distributed alongside official Apache releases. In all such cases, the
>> > binary/bytecode package MUST have the same version number as the source
>> > release and MUST only add binary/bytecode files that are the result of
>> > compiling that version of the source code release and its dependencies."
>> > I don't think my binary package violates any of these.
>>
>> +1 The PMC VOTE applies to source code, only. If someone wants to
>> rebuild the binary tarball with native libs and replace this one,
>> that's fine.
>>
>> My reading of the above is that source code must be distributed with
>> binaries, not that we omit the source code from binary releases... -C
>>
>> > But I'll upload an additional tar.gz with native bits and no src, as you
>> > guys requested.
>> > Will keep it as RC0 as there is no source code change and it comes from
>> the
>> > same build.
>> > Hope this is satisfactory.
>> >
>> > Thanks,
>> > --Konstantin
>> >
>> > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <an...@cloudera.com>
>> > wrote:
>> >
>> >> I agree with Brahma on the two issues flagged (having src in the binary
>> >> tarball, missing native libs). These are regressions from prior
>> releases.
>> >>
>> >> As an aside, "we release binaries as a convenience" doesn't relax the
>> >> quality bar. The binaries are linked on our website and distributed
>> through
>> >> official Apache channels. They have to adhere to Apache release
>> >> requirements. And, most users consume our work via Maven dependencies,
>> >> which are binary artifacts.
>> >>
>> >> http://www.apache.org/legal/release-policy.html goes into this in more
>> >> detail. A release must minimally include source packages, and can also
>> >> include binary artifacts.
>> >>
>> >> Best,
>> >> Andrew
>> >>
>> >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
>> >> shv.hadoop@gmail.com> wrote:
>> >>
>> >>> To avoid any confusion in this regard. I built RC0 manually in
>> compliance
>> >>> with Apache release policy
>> >>> http://www.apache.org/legal/release-policy.html
>> >>> I edited the HowToReleasePreDSBCR page to make sure people don't use
>> >>> Jenkins option for building.
>> >>>
>> >>> A side note. This particular build is broken anyways, so no worries
>> there.
>> >>> I think though it would be useful to have it working for testing and
>> as a
>> >>> packaging standard.
>> >>>
>> >>> Thanks,
>> >>> --Konstantin
>> >>>
>> >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
>> >>> aw@effectivemachines.com
>> >>> > wrote:
>> >>>
>> >>> >
>> >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
>> >>> shv.hadoop@gmail.com>
>> >>> > wrote:
>> >>> > >
>> >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
>> >>> >
>> >>> >         FYI:
>> >>> >
>> >>> >                 If you are using ASF Jenkins to create an ASF release
>> >>> > artifact, it's pretty much an automatic vote failure as any such
>> >>> release is
>> >>> > in violation of ASF policy.
>> >>> >
>> >>> >
>> >>>
>> >>
>> >>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>
>> --
> Zhe Zhang
> Apache Hadoop Committer
> http://zhe-thoughts.github.io/about/ | @oldcap

---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Chris Douglas <cd...@apache.org>.
On Wed, Aug 2, 2017 at 12:02 AM, Zhe Zhang <zh...@apache.org> wrote:
> Quick question for Chris: was your +1 for the RC, or to support
> Konstantin's statement regarding packaging?

For Konstantin's statement. I haven't had a chance to look through the
RC yet, but it's on my list. -C

> On Mon, Jul 31, 2017 at 3:56 PM Chris Douglas <cd...@apache.org> wrote:
>
>> On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
>> <sh...@gmail.com> wrote:
>> > For the packaging, here is the exact phrasing from the sited
>> release-policy
>> > document relevant to binaries:
>> > "As a convenience to users that might not have the appropriate tools to
>> > build a compiled version of the source, binary/bytecode packages MAY be
>> > distributed alongside official Apache releases. In all such cases, the
>> > binary/bytecode package MUST have the same version number as the source
>> > release and MUST only add binary/bytecode files that are the result of
>> > compiling that version of the source code release and its dependencies."
>> > I don't think my binary package violates any of these.
>>
>> +1 The PMC VOTE applies to source code, only. If someone wants to
>> rebuild the binary tarball with native libs and replace this one,
>> that's fine.
>>
>> My reading of the above is that source code must be distributed with
>> binaries, not that we omit the source code from binary releases... -C
>>
>> > But I'll upload an additional tar.gz with native bits and no src, as you
>> > guys requested.
>> > Will keep it as RC0 as there is no source code change and it comes from
>> the
>> > same build.
>> > Hope this is satisfactory.
>> >
>> > Thanks,
>> > --Konstantin
>> >
>> > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <an...@cloudera.com>
>> > wrote:
>> >
>> >> I agree with Brahma on the two issues flagged (having src in the binary
>> >> tarball, missing native libs). These are regressions from prior
>> releases.
>> >>
>> >> As an aside, "we release binaries as a convenience" doesn't relax the
>> >> quality bar. The binaries are linked on our website and distributed
>> through
>> >> official Apache channels. They have to adhere to Apache release
>> >> requirements. And, most users consume our work via Maven dependencies,
>> >> which are binary artifacts.
>> >>
>> >> http://www.apache.org/legal/release-policy.html goes into this in more
>> >> detail. A release must minimally include source packages, and can also
>> >> include binary artifacts.
>> >>
>> >> Best,
>> >> Andrew
>> >>
>> >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
>> >> shv.hadoop@gmail.com> wrote:
>> >>
>> >>> To avoid any confusion in this regard. I built RC0 manually in
>> compliance
>> >>> with Apache release policy
>> >>> http://www.apache.org/legal/release-policy.html
>> >>> I edited the HowToReleasePreDSBCR page to make sure people don't use
>> >>> Jenkins option for building.
>> >>>
>> >>> A side note. This particular build is broken anyways, so no worries
>> there.
>> >>> I think though it would be useful to have it working for testing and
>> as a
>> >>> packaging standard.
>> >>>
>> >>> Thanks,
>> >>> --Konstantin
>> >>>
>> >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
>> >>> aw@effectivemachines.com
>> >>> > wrote:
>> >>>
>> >>> >
>> >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
>> >>> shv.hadoop@gmail.com>
>> >>> > wrote:
>> >>> > >
>> >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
>> >>> >
>> >>> >         FYI:
>> >>> >
>> >>> >                 If you are using ASF Jenkins to create an ASF release
>> >>> > artifact, it's pretty much an automatic vote failure as any such
>> >>> release is
>> >>> > in violation of ASF policy.
>> >>> >
>> >>> >
>> >>>
>> >>
>> >>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>
>> --
> Zhe Zhang
> Apache Hadoop Committer
> http://zhe-thoughts.github.io/about/ | @oldcap

---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Chris Douglas <cd...@apache.org>.
On Wed, Aug 2, 2017 at 12:02 AM, Zhe Zhang <zh...@apache.org> wrote:
> Quick question for Chris: was your +1 for the RC, or to support
> Konstantin's statement regarding packaging?

For Konstantin's statement. I haven't had a chance to look through the
RC yet, but it's on my list. -C

> On Mon, Jul 31, 2017 at 3:56 PM Chris Douglas <cd...@apache.org> wrote:
>
>> On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
>> <sh...@gmail.com> wrote:
>> > For the packaging, here is the exact phrasing from the sited
>> release-policy
>> > document relevant to binaries:
>> > "As a convenience to users that might not have the appropriate tools to
>> > build a compiled version of the source, binary/bytecode packages MAY be
>> > distributed alongside official Apache releases. In all such cases, the
>> > binary/bytecode package MUST have the same version number as the source
>> > release and MUST only add binary/bytecode files that are the result of
>> > compiling that version of the source code release and its dependencies."
>> > I don't think my binary package violates any of these.
>>
>> +1 The PMC VOTE applies to source code, only. If someone wants to
>> rebuild the binary tarball with native libs and replace this one,
>> that's fine.
>>
>> My reading of the above is that source code must be distributed with
>> binaries, not that we omit the source code from binary releases... -C
>>
>> > But I'll upload an additional tar.gz with native bits and no src, as you
>> > guys requested.
>> > Will keep it as RC0 as there is no source code change and it comes from
>> the
>> > same build.
>> > Hope this is satisfactory.
>> >
>> > Thanks,
>> > --Konstantin
>> >
>> > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <an...@cloudera.com>
>> > wrote:
>> >
>> >> I agree with Brahma on the two issues flagged (having src in the binary
>> >> tarball, missing native libs). These are regressions from prior
>> releases.
>> >>
>> >> As an aside, "we release binaries as a convenience" doesn't relax the
>> >> quality bar. The binaries are linked on our website and distributed
>> through
>> >> official Apache channels. They have to adhere to Apache release
>> >> requirements. And, most users consume our work via Maven dependencies,
>> >> which are binary artifacts.
>> >>
>> >> http://www.apache.org/legal/release-policy.html goes into this in more
>> >> detail. A release must minimally include source packages, and can also
>> >> include binary artifacts.
>> >>
>> >> Best,
>> >> Andrew
>> >>
>> >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
>> >> shv.hadoop@gmail.com> wrote:
>> >>
>> >>> To avoid any confusion in this regard. I built RC0 manually in
>> compliance
>> >>> with Apache release policy
>> >>> http://www.apache.org/legal/release-policy.html
>> >>> I edited the HowToReleasePreDSBCR page to make sure people don't use
>> >>> Jenkins option for building.
>> >>>
>> >>> A side note. This particular build is broken anyways, so no worries
>> there.
>> >>> I think though it would be useful to have it working for testing and
>> as a
>> >>> packaging standard.
>> >>>
>> >>> Thanks,
>> >>> --Konstantin
>> >>>
>> >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
>> >>> aw@effectivemachines.com
>> >>> > wrote:
>> >>>
>> >>> >
>> >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
>> >>> shv.hadoop@gmail.com>
>> >>> > wrote:
>> >>> > >
>> >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
>> >>> >
>> >>> >         FYI:
>> >>> >
>> >>> >                 If you are using ASF Jenkins to create an ASF release
>> >>> > artifact, it's pretty much an automatic vote failure as any such
>> >>> release is
>> >>> > in violation of ASF policy.
>> >>> >
>> >>> >
>> >>>
>> >>
>> >>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>
>> --
> Zhe Zhang
> Apache Hadoop Committer
> http://zhe-thoughts.github.io/about/ | @oldcap

---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Chris Douglas <cd...@apache.org>.
On Wed, Aug 2, 2017 at 12:02 AM, Zhe Zhang <zh...@apache.org> wrote:
> Quick question for Chris: was your +1 for the RC, or to support
> Konstantin's statement regarding packaging?

For Konstantin's statement. I haven't had a chance to look through the
RC yet, but it's on my list. -C

> On Mon, Jul 31, 2017 at 3:56 PM Chris Douglas <cd...@apache.org> wrote:
>
>> On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
>> <sh...@gmail.com> wrote:
>> > For the packaging, here is the exact phrasing from the sited
>> release-policy
>> > document relevant to binaries:
>> > "As a convenience to users that might not have the appropriate tools to
>> > build a compiled version of the source, binary/bytecode packages MAY be
>> > distributed alongside official Apache releases. In all such cases, the
>> > binary/bytecode package MUST have the same version number as the source
>> > release and MUST only add binary/bytecode files that are the result of
>> > compiling that version of the source code release and its dependencies."
>> > I don't think my binary package violates any of these.
>>
>> +1 The PMC VOTE applies to source code, only. If someone wants to
>> rebuild the binary tarball with native libs and replace this one,
>> that's fine.
>>
>> My reading of the above is that source code must be distributed with
>> binaries, not that we omit the source code from binary releases... -C
>>
>> > But I'll upload an additional tar.gz with native bits and no src, as you
>> > guys requested.
>> > Will keep it as RC0 as there is no source code change and it comes from
>> the
>> > same build.
>> > Hope this is satisfactory.
>> >
>> > Thanks,
>> > --Konstantin
>> >
>> > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <an...@cloudera.com>
>> > wrote:
>> >
>> >> I agree with Brahma on the two issues flagged (having src in the binary
>> >> tarball, missing native libs). These are regressions from prior
>> releases.
>> >>
>> >> As an aside, "we release binaries as a convenience" doesn't relax the
>> >> quality bar. The binaries are linked on our website and distributed
>> through
>> >> official Apache channels. They have to adhere to Apache release
>> >> requirements. And, most users consume our work via Maven dependencies,
>> >> which are binary artifacts.
>> >>
>> >> http://www.apache.org/legal/release-policy.html goes into this in more
>> >> detail. A release must minimally include source packages, and can also
>> >> include binary artifacts.
>> >>
>> >> Best,
>> >> Andrew
>> >>
>> >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
>> >> shv.hadoop@gmail.com> wrote:
>> >>
>> >>> To avoid any confusion in this regard. I built RC0 manually in
>> compliance
>> >>> with Apache release policy
>> >>> http://www.apache.org/legal/release-policy.html
>> >>> I edited the HowToReleasePreDSBCR page to make sure people don't use
>> >>> Jenkins option for building.
>> >>>
>> >>> A side note. This particular build is broken anyways, so no worries
>> there.
>> >>> I think though it would be useful to have it working for testing and
>> as a
>> >>> packaging standard.
>> >>>
>> >>> Thanks,
>> >>> --Konstantin
>> >>>
>> >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
>> >>> aw@effectivemachines.com
>> >>> > wrote:
>> >>>
>> >>> >
>> >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
>> >>> shv.hadoop@gmail.com>
>> >>> > wrote:
>> >>> > >
>> >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
>> >>> >
>> >>> >         FYI:
>> >>> >
>> >>> >                 If you are using ASF Jenkins to create an ASF release
>> >>> > artifact, it's pretty much an automatic vote failure as any such
>> >>> release is
>> >>> > in violation of ASF policy.
>> >>> >
>> >>> >
>> >>>
>> >>
>> >>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>
>> --
> Zhe Zhang
> Apache Hadoop Committer
> http://zhe-thoughts.github.io/about/ | @oldcap

---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Zhe Zhang <zh...@apache.org>.
Quick question for Chris: was your +1 for the RC, or to support
Konstantin's statement regarding packaging?

Thanks,

On Mon, Jul 31, 2017 at 3:56 PM Chris Douglas <cd...@apache.org> wrote:

> On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
> <sh...@gmail.com> wrote:
> > For the packaging, here is the exact phrasing from the sited
> release-policy
> > document relevant to binaries:
> > "As a convenience to users that might not have the appropriate tools to
> > build a compiled version of the source, binary/bytecode packages MAY be
> > distributed alongside official Apache releases. In all such cases, the
> > binary/bytecode package MUST have the same version number as the source
> > release and MUST only add binary/bytecode files that are the result of
> > compiling that version of the source code release and its dependencies."
> > I don't think my binary package violates any of these.
>
> +1 The PMC VOTE applies to source code, only. If someone wants to
> rebuild the binary tarball with native libs and replace this one,
> that's fine.
>
> My reading of the above is that source code must be distributed with
> binaries, not that we omit the source code from binary releases... -C
>
> > But I'll upload an additional tar.gz with native bits and no src, as you
> > guys requested.
> > Will keep it as RC0 as there is no source code change and it comes from
> the
> > same build.
> > Hope this is satisfactory.
> >
> > Thanks,
> > --Konstantin
> >
> > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <an...@cloudera.com>
> > wrote:
> >
> >> I agree with Brahma on the two issues flagged (having src in the binary
> >> tarball, missing native libs). These are regressions from prior
> releases.
> >>
> >> As an aside, "we release binaries as a convenience" doesn't relax the
> >> quality bar. The binaries are linked on our website and distributed
> through
> >> official Apache channels. They have to adhere to Apache release
> >> requirements. And, most users consume our work via Maven dependencies,
> >> which are binary artifacts.
> >>
> >> http://www.apache.org/legal/release-policy.html goes into this in more
> >> detail. A release must minimally include source packages, and can also
> >> include binary artifacts.
> >>
> >> Best,
> >> Andrew
> >>
> >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
> >> shv.hadoop@gmail.com> wrote:
> >>
> >>> To avoid any confusion in this regard. I built RC0 manually in
> compliance
> >>> with Apache release policy
> >>> http://www.apache.org/legal/release-policy.html
> >>> I edited the HowToReleasePreDSBCR page to make sure people don't use
> >>> Jenkins option for building.
> >>>
> >>> A side note. This particular build is broken anyways, so no worries
> there.
> >>> I think though it would be useful to have it working for testing and
> as a
> >>> packaging standard.
> >>>
> >>> Thanks,
> >>> --Konstantin
> >>>
> >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
> >>> aw@effectivemachines.com
> >>> > wrote:
> >>>
> >>> >
> >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
> >>> shv.hadoop@gmail.com>
> >>> > wrote:
> >>> > >
> >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
> >>> >
> >>> >         FYI:
> >>> >
> >>> >                 If you are using ASF Jenkins to create an ASF release
> >>> > artifact, it's pretty much an automatic vote failure as any such
> >>> release is
> >>> > in violation of ASF policy.
> >>> >
> >>> >
> >>>
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
> --
Zhe Zhang
Apache Hadoop Committer
http://zhe-thoughts.github.io/about/ | @oldcap

RE: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Brahma Reddy Battula <br...@huawei.com>.
Hi Konstantin,

Thanks a lot again for your efforts.

+1  (non-binding)

-Built from the source on Suse-Linux with jdk_ 1.8.0_40
-Installed the HA cluster
-Verified basic shell commands
-Ran sample jobs
-Did the regression on IBR Feature, Balancer/mover,fsck

Downloaded the latest tarball, it contains the native and nodemanger can start (NM will not start without native). And install pseudo cluster and did basic verification.

IMHO, we should include natives in the tarball for user convenience (who doesn't have build tool can use for quick regression) 

As we are separately giving hadoop-2.7.4-RC0-src.tar.gz, still we need to include /src in tarball..?

As Andrew mentioned, these two are regression to prior release.


--Brahma Reddy Battula

-----Original Message-----
From: Konstantin Shvachko [mailto:shv.hadoop@gmail.com] 
Sent: 01 August 2017 09:57
To: Chris Douglas
Cc: Andrew Wang; Allen Wittenauer; common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org
Subject: Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Uploaded new binaries hadoop-2.7.4-RC0.tar.gz, which adds lib/native/.
Same place: http://home.apache.org/~shv/hadoop-2.7.4-RC0/

Thanks,
--Konstantin

On Mon, Jul 31, 2017 at 3:56 PM, Chris Douglas <cd...@apache.org> wrote:

> On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko 
> <sh...@gmail.com> wrote:
> > For the packaging, here is the exact phrasing from the sited
> release-policy
> > document relevant to binaries:
> > "As a convenience to users that might not have the appropriate tools 
> > to build a compiled version of the source, binary/bytecode packages 
> > MAY be distributed alongside official Apache releases. In all such 
> > cases, the binary/bytecode package MUST have the same version number 
> > as the source release and MUST only add binary/bytecode files that 
> > are the result of compiling that version of the source code release and its dependencies."
> > I don't think my binary package violates any of these.
>
> +1 The PMC VOTE applies to source code, only. If someone wants to
> rebuild the binary tarball with native libs and replace this one, 
> that's fine.
>
> My reading of the above is that source code must be distributed with 
> binaries, not that we omit the source code from binary releases... -C
>
> > But I'll upload an additional tar.gz with native bits and no src, as 
> > you guys requested.
> > Will keep it as RC0 as there is no source code change and it comes 
> > from
> the
> > same build.
> > Hope this is satisfactory.
> >
> > Thanks,
> > --Konstantin
> >
> > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang 
> > <an...@cloudera.com>
> > wrote:
> >
> >> I agree with Brahma on the two issues flagged (having src in the 
> >> binary tarball, missing native libs). These are regressions from 
> >> prior
> releases.
> >>
> >> As an aside, "we release binaries as a convenience" doesn't relax 
> >> the quality bar. The binaries are linked on our website and 
> >> distributed
> through
> >> official Apache channels. They have to adhere to Apache release 
> >> requirements. And, most users consume our work via Maven 
> >> dependencies, which are binary artifacts.
> >>
> >> http://www.apache.org/legal/release-policy.html goes into this in 
> >> more detail. A release must minimally include source packages, and 
> >> can also include binary artifacts.
> >>
> >> Best,
> >> Andrew
> >>
> >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko < 
> >> shv.hadoop@gmail.com> wrote:
> >>
> >>> To avoid any confusion in this regard. I built RC0 manually in
> compliance
> >>> with Apache release policy
> >>> http://www.apache.org/legal/release-policy.html
> >>> I edited the HowToReleasePreDSBCR page to make sure people don't 
> >>> use Jenkins option for building.
> >>>
> >>> A side note. This particular build is broken anyways, so no 
> >>> worries
> there.
> >>> I think though it would be useful to have it working for testing 
> >>> and
> as a
> >>> packaging standard.
> >>>
> >>> Thanks,
> >>> --Konstantin
> >>>
> >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer < 
> >>> aw@effectivemachines.com
> >>> > wrote:
> >>>
> >>> >
> >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
> >>> shv.hadoop@gmail.com>
> >>> > wrote:
> >>> > >
> >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
> >>> >
> >>> >         FYI:
> >>> >
> >>> >                 If you are using ASF Jenkins to create an ASF 
> >>> > release artifact, it's pretty much an automatic vote failure as 
> >>> > any such
> >>> release is
> >>> > in violation of ASF policy.
> >>> >
> >>> >
> >>>
> >>
> >>
>

RE: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Brahma Reddy Battula <br...@huawei.com>.
Hi Konstantin,

Thanks a lot again for your efforts.

+1  (non-binding)

-Built from the source on Suse-Linux with jdk_ 1.8.0_40
-Installed the HA cluster
-Verified basic shell commands
-Ran sample jobs
-Did the regression on IBR Feature, Balancer/mover,fsck

Downloaded the latest tarball, it contains the native and nodemanger can start (NM will not start without native). And install pseudo cluster and did basic verification.

IMHO, we should include natives in the tarball for user convenience (who doesn't have build tool can use for quick regression) 

As we are separately giving hadoop-2.7.4-RC0-src.tar.gz, still we need to include /src in tarball..?

As Andrew mentioned, these two are regression to prior release.


--Brahma Reddy Battula

-----Original Message-----
From: Konstantin Shvachko [mailto:shv.hadoop@gmail.com] 
Sent: 01 August 2017 09:57
To: Chris Douglas
Cc: Andrew Wang; Allen Wittenauer; common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org
Subject: Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Uploaded new binaries hadoop-2.7.4-RC0.tar.gz, which adds lib/native/.
Same place: http://home.apache.org/~shv/hadoop-2.7.4-RC0/

Thanks,
--Konstantin

On Mon, Jul 31, 2017 at 3:56 PM, Chris Douglas <cd...@apache.org> wrote:

> On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko 
> <sh...@gmail.com> wrote:
> > For the packaging, here is the exact phrasing from the sited
> release-policy
> > document relevant to binaries:
> > "As a convenience to users that might not have the appropriate tools 
> > to build a compiled version of the source, binary/bytecode packages 
> > MAY be distributed alongside official Apache releases. In all such 
> > cases, the binary/bytecode package MUST have the same version number 
> > as the source release and MUST only add binary/bytecode files that 
> > are the result of compiling that version of the source code release and its dependencies."
> > I don't think my binary package violates any of these.
>
> +1 The PMC VOTE applies to source code, only. If someone wants to
> rebuild the binary tarball with native libs and replace this one, 
> that's fine.
>
> My reading of the above is that source code must be distributed with 
> binaries, not that we omit the source code from binary releases... -C
>
> > But I'll upload an additional tar.gz with native bits and no src, as 
> > you guys requested.
> > Will keep it as RC0 as there is no source code change and it comes 
> > from
> the
> > same build.
> > Hope this is satisfactory.
> >
> > Thanks,
> > --Konstantin
> >
> > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang 
> > <an...@cloudera.com>
> > wrote:
> >
> >> I agree with Brahma on the two issues flagged (having src in the 
> >> binary tarball, missing native libs). These are regressions from 
> >> prior
> releases.
> >>
> >> As an aside, "we release binaries as a convenience" doesn't relax 
> >> the quality bar. The binaries are linked on our website and 
> >> distributed
> through
> >> official Apache channels. They have to adhere to Apache release 
> >> requirements. And, most users consume our work via Maven 
> >> dependencies, which are binary artifacts.
> >>
> >> http://www.apache.org/legal/release-policy.html goes into this in 
> >> more detail. A release must minimally include source packages, and 
> >> can also include binary artifacts.
> >>
> >> Best,
> >> Andrew
> >>
> >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko < 
> >> shv.hadoop@gmail.com> wrote:
> >>
> >>> To avoid any confusion in this regard. I built RC0 manually in
> compliance
> >>> with Apache release policy
> >>> http://www.apache.org/legal/release-policy.html
> >>> I edited the HowToReleasePreDSBCR page to make sure people don't 
> >>> use Jenkins option for building.
> >>>
> >>> A side note. This particular build is broken anyways, so no 
> >>> worries
> there.
> >>> I think though it would be useful to have it working for testing 
> >>> and
> as a
> >>> packaging standard.
> >>>
> >>> Thanks,
> >>> --Konstantin
> >>>
> >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer < 
> >>> aw@effectivemachines.com
> >>> > wrote:
> >>>
> >>> >
> >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
> >>> shv.hadoop@gmail.com>
> >>> > wrote:
> >>> > >
> >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
> >>> >
> >>> >         FYI:
> >>> >
> >>> >                 If you are using ASF Jenkins to create an ASF 
> >>> > release artifact, it's pretty much an automatic vote failure as 
> >>> > any such
> >>> release is
> >>> > in violation of ASF policy.
> >>> >
> >>> >
> >>>
> >>
> >>
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Zhe Zhang <zh...@apache.org>.
+1 (binding)

1. Downloaded src tar ball, verified m5dsum
2. Built from source on Linux RHEL6, Java 1_8_0_40
3. Tried some HDFS CLI methods with the above build, against two clusters,
one running 2.6.1 and another running 2.7.4 (server bin/conf built by an
internal Jenkins job, as Ye Zhou mentioned above). Both clusters are secure.
  - ls
  - mkdir
  - copyFromLocal
  - find (new feature in 2.7)
4. Tried some YARN CLI methods, on the above 2.7.4 cluster
  - yarn logs (verified a sample application's logs)
  - yarn cluster -lnl

Thanks for the great work Konstantin!

On Tue, Aug 1, 2017 at 5:00 PM Ye Zhou <zh...@gmail.com> wrote:

> Hi, Konstantin.
> Thanks for leading the release.
>
> +1 (non-binding)
>
> -Built from the source on mac with jdk_1.8.0_40
> -Built on internal Jenkins with jdk_1.8.0_40.
> -Deployed on a cluster with 121 nodes(Including RM, NM, NN, DN)
> -Basic shell commands
> -Distcp 3.7TB data to HDFS
> -Run GridMix test which submitted 15K MR jobs in 5 hours(trace generated
> from real production job trace)
>
> On Mon, Jul 31, 2017 at 6:57 PM, Konstantin Shvachko <shv.hadoop@gmail.com
> >
> wrote:
>
> > Uploaded new binaries hadoop-2.7.4-RC0.tar.gz, which adds lib/native/.
> > Same place: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
> >
> > Thanks,
> > --Konstantin
> >
> > On Mon, Jul 31, 2017 at 3:56 PM, Chris Douglas <cd...@apache.org>
> > wrote:
> >
> > > On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
> > > <sh...@gmail.com> wrote:
> > > > For the packaging, here is the exact phrasing from the sited
> > > release-policy
> > > > document relevant to binaries:
> > > > "As a convenience to users that might not have the appropriate tools
> to
> > > > build a compiled version of the source, binary/bytecode packages MAY
> be
> > > > distributed alongside official Apache releases. In all such cases,
> the
> > > > binary/bytecode package MUST have the same version number as the
> source
> > > > release and MUST only add binary/bytecode files that are the result
> of
> > > > compiling that version of the source code release and its
> > dependencies."
> > > > I don't think my binary package violates any of these.
> > >
> > > +1 The PMC VOTE applies to source code, only. If someone wants to
> > > rebuild the binary tarball with native libs and replace this one,
> > > that's fine.
> > >
> > > My reading of the above is that source code must be distributed with
> > > binaries, not that we omit the source code from binary releases... -C
> > >
> > > > But I'll upload an additional tar.gz with native bits and no src, as
> > you
> > > > guys requested.
> > > > Will keep it as RC0 as there is no source code change and it comes
> from
> > > the
> > > > same build.
> > > > Hope this is satisfactory.
> > > >
> > > > Thanks,
> > > > --Konstantin
> > > >
> > > > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <
> andrew.wang@cloudera.com
> > >
> > > > wrote:
> > > >
> > > >> I agree with Brahma on the two issues flagged (having src in the
> > binary
> > > >> tarball, missing native libs). These are regressions from prior
> > > releases.
> > > >>
> > > >> As an aside, "we release binaries as a convenience" doesn't relax
> the
> > > >> quality bar. The binaries are linked on our website and distributed
> > > through
> > > >> official Apache channels. They have to adhere to Apache release
> > > >> requirements. And, most users consume our work via Maven
> dependencies,
> > > >> which are binary artifacts.
> > > >>
> > > >> http://www.apache.org/legal/release-policy.html goes into this in
> > more
> > > >> detail. A release must minimally include source packages, and can
> also
> > > >> include binary artifacts.
> > > >>
> > > >> Best,
> > > >> Andrew
> > > >>
> > > >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
> > > >> shv.hadoop@gmail.com> wrote:
> > > >>
> > > >>> To avoid any confusion in this regard. I built RC0 manually in
> > > compliance
> > > >>> with Apache release policy
> > > >>> http://www.apache.org/legal/release-policy.html
> > > >>> I edited the HowToReleasePreDSBCR page to make sure people don't
> use
> > > >>> Jenkins option for building.
> > > >>>
> > > >>> A side note. This particular build is broken anyways, so no worries
> > > there.
> > > >>> I think though it would be useful to have it working for testing
> and
> > > as a
> > > >>> packaging standard.
> > > >>>
> > > >>> Thanks,
> > > >>> --Konstantin
> > > >>>
> > > >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
> > > >>> aw@effectivemachines.com
> > > >>> > wrote:
> > > >>>
> > > >>> >
> > > >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
> > > >>> shv.hadoop@gmail.com>
> > > >>> > wrote:
> > > >>> > >
> > > >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
> > > >>> >
> > > >>> >         FYI:
> > > >>> >
> > > >>> >                 If you are using ASF Jenkins to create an ASF
> > release
> > > >>> > artifact, it's pretty much an automatic vote failure as any such
> > > >>> release is
> > > >>> > in violation of ASF policy.
> > > >>> >
> > > >>> >
> > > >>>
> > > >>
> > > >>
> > >
> >
>
>
>
> --
>
> *Zhou, Ye  **周晔*
>
-- 
Zhe Zhang
Apache Hadoop Committer
http://zhe-thoughts.github.io/about/ | @oldcap

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Zhe Zhang <zh...@apache.org>.
+1 (binding)

1. Downloaded src tar ball, verified m5dsum
2. Built from source on Linux RHEL6, Java 1_8_0_40
3. Tried some HDFS CLI methods with the above build, against two clusters,
one running 2.6.1 and another running 2.7.4 (server bin/conf built by an
internal Jenkins job, as Ye Zhou mentioned above). Both clusters are secure.
  - ls
  - mkdir
  - copyFromLocal
  - find (new feature in 2.7)
4. Tried some YARN CLI methods, on the above 2.7.4 cluster
  - yarn logs (verified a sample application's logs)
  - yarn cluster -lnl

Thanks for the great work Konstantin!

On Tue, Aug 1, 2017 at 5:00 PM Ye Zhou <zh...@gmail.com> wrote:

> Hi, Konstantin.
> Thanks for leading the release.
>
> +1 (non-binding)
>
> -Built from the source on mac with jdk_1.8.0_40
> -Built on internal Jenkins with jdk_1.8.0_40.
> -Deployed on a cluster with 121 nodes(Including RM, NM, NN, DN)
> -Basic shell commands
> -Distcp 3.7TB data to HDFS
> -Run GridMix test which submitted 15K MR jobs in 5 hours(trace generated
> from real production job trace)
>
> On Mon, Jul 31, 2017 at 6:57 PM, Konstantin Shvachko <shv.hadoop@gmail.com
> >
> wrote:
>
> > Uploaded new binaries hadoop-2.7.4-RC0.tar.gz, which adds lib/native/.
> > Same place: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
> >
> > Thanks,
> > --Konstantin
> >
> > On Mon, Jul 31, 2017 at 3:56 PM, Chris Douglas <cd...@apache.org>
> > wrote:
> >
> > > On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
> > > <sh...@gmail.com> wrote:
> > > > For the packaging, here is the exact phrasing from the sited
> > > release-policy
> > > > document relevant to binaries:
> > > > "As a convenience to users that might not have the appropriate tools
> to
> > > > build a compiled version of the source, binary/bytecode packages MAY
> be
> > > > distributed alongside official Apache releases. In all such cases,
> the
> > > > binary/bytecode package MUST have the same version number as the
> source
> > > > release and MUST only add binary/bytecode files that are the result
> of
> > > > compiling that version of the source code release and its
> > dependencies."
> > > > I don't think my binary package violates any of these.
> > >
> > > +1 The PMC VOTE applies to source code, only. If someone wants to
> > > rebuild the binary tarball with native libs and replace this one,
> > > that's fine.
> > >
> > > My reading of the above is that source code must be distributed with
> > > binaries, not that we omit the source code from binary releases... -C
> > >
> > > > But I'll upload an additional tar.gz with native bits and no src, as
> > you
> > > > guys requested.
> > > > Will keep it as RC0 as there is no source code change and it comes
> from
> > > the
> > > > same build.
> > > > Hope this is satisfactory.
> > > >
> > > > Thanks,
> > > > --Konstantin
> > > >
> > > > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <
> andrew.wang@cloudera.com
> > >
> > > > wrote:
> > > >
> > > >> I agree with Brahma on the two issues flagged (having src in the
> > binary
> > > >> tarball, missing native libs). These are regressions from prior
> > > releases.
> > > >>
> > > >> As an aside, "we release binaries as a convenience" doesn't relax
> the
> > > >> quality bar. The binaries are linked on our website and distributed
> > > through
> > > >> official Apache channels. They have to adhere to Apache release
> > > >> requirements. And, most users consume our work via Maven
> dependencies,
> > > >> which are binary artifacts.
> > > >>
> > > >> http://www.apache.org/legal/release-policy.html goes into this in
> > more
> > > >> detail. A release must minimally include source packages, and can
> also
> > > >> include binary artifacts.
> > > >>
> > > >> Best,
> > > >> Andrew
> > > >>
> > > >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
> > > >> shv.hadoop@gmail.com> wrote:
> > > >>
> > > >>> To avoid any confusion in this regard. I built RC0 manually in
> > > compliance
> > > >>> with Apache release policy
> > > >>> http://www.apache.org/legal/release-policy.html
> > > >>> I edited the HowToReleasePreDSBCR page to make sure people don't
> use
> > > >>> Jenkins option for building.
> > > >>>
> > > >>> A side note. This particular build is broken anyways, so no worries
> > > there.
> > > >>> I think though it would be useful to have it working for testing
> and
> > > as a
> > > >>> packaging standard.
> > > >>>
> > > >>> Thanks,
> > > >>> --Konstantin
> > > >>>
> > > >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
> > > >>> aw@effectivemachines.com
> > > >>> > wrote:
> > > >>>
> > > >>> >
> > > >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
> > > >>> shv.hadoop@gmail.com>
> > > >>> > wrote:
> > > >>> > >
> > > >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
> > > >>> >
> > > >>> >         FYI:
> > > >>> >
> > > >>> >                 If you are using ASF Jenkins to create an ASF
> > release
> > > >>> > artifact, it's pretty much an automatic vote failure as any such
> > > >>> release is
> > > >>> > in violation of ASF policy.
> > > >>> >
> > > >>> >
> > > >>>
> > > >>
> > > >>
> > >
> >
>
>
>
> --
>
> *Zhou, Ye  **周晔*
>
-- 
Zhe Zhang
Apache Hadoop Committer
http://zhe-thoughts.github.io/about/ | @oldcap

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Zhe Zhang <zh...@apache.org>.
+1 (binding)

1. Downloaded src tar ball, verified m5dsum
2. Built from source on Linux RHEL6, Java 1_8_0_40
3. Tried some HDFS CLI methods with the above build, against two clusters,
one running 2.6.1 and another running 2.7.4 (server bin/conf built by an
internal Jenkins job, as Ye Zhou mentioned above). Both clusters are secure.
  - ls
  - mkdir
  - copyFromLocal
  - find (new feature in 2.7)
4. Tried some YARN CLI methods, on the above 2.7.4 cluster
  - yarn logs (verified a sample application's logs)
  - yarn cluster -lnl

Thanks for the great work Konstantin!

On Tue, Aug 1, 2017 at 5:00 PM Ye Zhou <zh...@gmail.com> wrote:

> Hi, Konstantin.
> Thanks for leading the release.
>
> +1 (non-binding)
>
> -Built from the source on mac with jdk_1.8.0_40
> -Built on internal Jenkins with jdk_1.8.0_40.
> -Deployed on a cluster with 121 nodes(Including RM, NM, NN, DN)
> -Basic shell commands
> -Distcp 3.7TB data to HDFS
> -Run GridMix test which submitted 15K MR jobs in 5 hours(trace generated
> from real production job trace)
>
> On Mon, Jul 31, 2017 at 6:57 PM, Konstantin Shvachko <shv.hadoop@gmail.com
> >
> wrote:
>
> > Uploaded new binaries hadoop-2.7.4-RC0.tar.gz, which adds lib/native/.
> > Same place: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
> >
> > Thanks,
> > --Konstantin
> >
> > On Mon, Jul 31, 2017 at 3:56 PM, Chris Douglas <cd...@apache.org>
> > wrote:
> >
> > > On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
> > > <sh...@gmail.com> wrote:
> > > > For the packaging, here is the exact phrasing from the sited
> > > release-policy
> > > > document relevant to binaries:
> > > > "As a convenience to users that might not have the appropriate tools
> to
> > > > build a compiled version of the source, binary/bytecode packages MAY
> be
> > > > distributed alongside official Apache releases. In all such cases,
> the
> > > > binary/bytecode package MUST have the same version number as the
> source
> > > > release and MUST only add binary/bytecode files that are the result
> of
> > > > compiling that version of the source code release and its
> > dependencies."
> > > > I don't think my binary package violates any of these.
> > >
> > > +1 The PMC VOTE applies to source code, only. If someone wants to
> > > rebuild the binary tarball with native libs and replace this one,
> > > that's fine.
> > >
> > > My reading of the above is that source code must be distributed with
> > > binaries, not that we omit the source code from binary releases... -C
> > >
> > > > But I'll upload an additional tar.gz with native bits and no src, as
> > you
> > > > guys requested.
> > > > Will keep it as RC0 as there is no source code change and it comes
> from
> > > the
> > > > same build.
> > > > Hope this is satisfactory.
> > > >
> > > > Thanks,
> > > > --Konstantin
> > > >
> > > > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <
> andrew.wang@cloudera.com
> > >
> > > > wrote:
> > > >
> > > >> I agree with Brahma on the two issues flagged (having src in the
> > binary
> > > >> tarball, missing native libs). These are regressions from prior
> > > releases.
> > > >>
> > > >> As an aside, "we release binaries as a convenience" doesn't relax
> the
> > > >> quality bar. The binaries are linked on our website and distributed
> > > through
> > > >> official Apache channels. They have to adhere to Apache release
> > > >> requirements. And, most users consume our work via Maven
> dependencies,
> > > >> which are binary artifacts.
> > > >>
> > > >> http://www.apache.org/legal/release-policy.html goes into this in
> > more
> > > >> detail. A release must minimally include source packages, and can
> also
> > > >> include binary artifacts.
> > > >>
> > > >> Best,
> > > >> Andrew
> > > >>
> > > >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
> > > >> shv.hadoop@gmail.com> wrote:
> > > >>
> > > >>> To avoid any confusion in this regard. I built RC0 manually in
> > > compliance
> > > >>> with Apache release policy
> > > >>> http://www.apache.org/legal/release-policy.html
> > > >>> I edited the HowToReleasePreDSBCR page to make sure people don't
> use
> > > >>> Jenkins option for building.
> > > >>>
> > > >>> A side note. This particular build is broken anyways, so no worries
> > > there.
> > > >>> I think though it would be useful to have it working for testing
> and
> > > as a
> > > >>> packaging standard.
> > > >>>
> > > >>> Thanks,
> > > >>> --Konstantin
> > > >>>
> > > >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
> > > >>> aw@effectivemachines.com
> > > >>> > wrote:
> > > >>>
> > > >>> >
> > > >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
> > > >>> shv.hadoop@gmail.com>
> > > >>> > wrote:
> > > >>> > >
> > > >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
> > > >>> >
> > > >>> >         FYI:
> > > >>> >
> > > >>> >                 If you are using ASF Jenkins to create an ASF
> > release
> > > >>> > artifact, it's pretty much an automatic vote failure as any such
> > > >>> release is
> > > >>> > in violation of ASF policy.
> > > >>> >
> > > >>> >
> > > >>>
> > > >>
> > > >>
> > >
> >
>
>
>
> --
>
> *Zhou, Ye  **周晔*
>
-- 
Zhe Zhang
Apache Hadoop Committer
http://zhe-thoughts.github.io/about/ | @oldcap

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Zhe Zhang <zh...@apache.org>.
+1 (binding)

1. Downloaded src tar ball, verified m5dsum
2. Built from source on Linux RHEL6, Java 1_8_0_40
3. Tried some HDFS CLI methods with the above build, against two clusters,
one running 2.6.1 and another running 2.7.4 (server bin/conf built by an
internal Jenkins job, as Ye Zhou mentioned above). Both clusters are secure.
  - ls
  - mkdir
  - copyFromLocal
  - find (new feature in 2.7)
4. Tried some YARN CLI methods, on the above 2.7.4 cluster
  - yarn logs (verified a sample application's logs)
  - yarn cluster -lnl

Thanks for the great work Konstantin!

On Tue, Aug 1, 2017 at 5:00 PM Ye Zhou <zh...@gmail.com> wrote:

> Hi, Konstantin.
> Thanks for leading the release.
>
> +1 (non-binding)
>
> -Built from the source on mac with jdk_1.8.0_40
> -Built on internal Jenkins with jdk_1.8.0_40.
> -Deployed on a cluster with 121 nodes(Including RM, NM, NN, DN)
> -Basic shell commands
> -Distcp 3.7TB data to HDFS
> -Run GridMix test which submitted 15K MR jobs in 5 hours(trace generated
> from real production job trace)
>
> On Mon, Jul 31, 2017 at 6:57 PM, Konstantin Shvachko <shv.hadoop@gmail.com
> >
> wrote:
>
> > Uploaded new binaries hadoop-2.7.4-RC0.tar.gz, which adds lib/native/.
> > Same place: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
> >
> > Thanks,
> > --Konstantin
> >
> > On Mon, Jul 31, 2017 at 3:56 PM, Chris Douglas <cd...@apache.org>
> > wrote:
> >
> > > On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
> > > <sh...@gmail.com> wrote:
> > > > For the packaging, here is the exact phrasing from the sited
> > > release-policy
> > > > document relevant to binaries:
> > > > "As a convenience to users that might not have the appropriate tools
> to
> > > > build a compiled version of the source, binary/bytecode packages MAY
> be
> > > > distributed alongside official Apache releases. In all such cases,
> the
> > > > binary/bytecode package MUST have the same version number as the
> source
> > > > release and MUST only add binary/bytecode files that are the result
> of
> > > > compiling that version of the source code release and its
> > dependencies."
> > > > I don't think my binary package violates any of these.
> > >
> > > +1 The PMC VOTE applies to source code, only. If someone wants to
> > > rebuild the binary tarball with native libs and replace this one,
> > > that's fine.
> > >
> > > My reading of the above is that source code must be distributed with
> > > binaries, not that we omit the source code from binary releases... -C
> > >
> > > > But I'll upload an additional tar.gz with native bits and no src, as
> > you
> > > > guys requested.
> > > > Will keep it as RC0 as there is no source code change and it comes
> from
> > > the
> > > > same build.
> > > > Hope this is satisfactory.
> > > >
> > > > Thanks,
> > > > --Konstantin
> > > >
> > > > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <
> andrew.wang@cloudera.com
> > >
> > > > wrote:
> > > >
> > > >> I agree with Brahma on the two issues flagged (having src in the
> > binary
> > > >> tarball, missing native libs). These are regressions from prior
> > > releases.
> > > >>
> > > >> As an aside, "we release binaries as a convenience" doesn't relax
> the
> > > >> quality bar. The binaries are linked on our website and distributed
> > > through
> > > >> official Apache channels. They have to adhere to Apache release
> > > >> requirements. And, most users consume our work via Maven
> dependencies,
> > > >> which are binary artifacts.
> > > >>
> > > >> http://www.apache.org/legal/release-policy.html goes into this in
> > more
> > > >> detail. A release must minimally include source packages, and can
> also
> > > >> include binary artifacts.
> > > >>
> > > >> Best,
> > > >> Andrew
> > > >>
> > > >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
> > > >> shv.hadoop@gmail.com> wrote:
> > > >>
> > > >>> To avoid any confusion in this regard. I built RC0 manually in
> > > compliance
> > > >>> with Apache release policy
> > > >>> http://www.apache.org/legal/release-policy.html
> > > >>> I edited the HowToReleasePreDSBCR page to make sure people don't
> use
> > > >>> Jenkins option for building.
> > > >>>
> > > >>> A side note. This particular build is broken anyways, so no worries
> > > there.
> > > >>> I think though it would be useful to have it working for testing
> and
> > > as a
> > > >>> packaging standard.
> > > >>>
> > > >>> Thanks,
> > > >>> --Konstantin
> > > >>>
> > > >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
> > > >>> aw@effectivemachines.com
> > > >>> > wrote:
> > > >>>
> > > >>> >
> > > >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
> > > >>> shv.hadoop@gmail.com>
> > > >>> > wrote:
> > > >>> > >
> > > >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
> > > >>> >
> > > >>> >         FYI:
> > > >>> >
> > > >>> >                 If you are using ASF Jenkins to create an ASF
> > release
> > > >>> > artifact, it's pretty much an automatic vote failure as any such
> > > >>> release is
> > > >>> > in violation of ASF policy.
> > > >>> >
> > > >>> >
> > > >>>
> > > >>
> > > >>
> > >
> >
>
>
>
> --
>
> *Zhou, Ye  **周晔*
>
-- 
Zhe Zhang
Apache Hadoop Committer
http://zhe-thoughts.github.io/about/ | @oldcap

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Ye Zhou <zh...@gmail.com>.
Hi, Konstantin.
Thanks for leading the release.

+1 (non-binding)

-Built from the source on mac with jdk_1.8.0_40
-Built on internal Jenkins with jdk_1.8.0_40.
-Deployed on a cluster with 121 nodes(Including RM, NM, NN, DN)
-Basic shell commands
-Distcp 3.7TB data to HDFS
-Run GridMix test which submitted 15K MR jobs in 5 hours(trace generated
from real production job trace)

On Mon, Jul 31, 2017 at 6:57 PM, Konstantin Shvachko <sh...@gmail.com>
wrote:

> Uploaded new binaries hadoop-2.7.4-RC0.tar.gz, which adds lib/native/.
> Same place: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>
> Thanks,
> --Konstantin
>
> On Mon, Jul 31, 2017 at 3:56 PM, Chris Douglas <cd...@apache.org>
> wrote:
>
> > On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
> > <sh...@gmail.com> wrote:
> > > For the packaging, here is the exact phrasing from the sited
> > release-policy
> > > document relevant to binaries:
> > > "As a convenience to users that might not have the appropriate tools to
> > > build a compiled version of the source, binary/bytecode packages MAY be
> > > distributed alongside official Apache releases. In all such cases, the
> > > binary/bytecode package MUST have the same version number as the source
> > > release and MUST only add binary/bytecode files that are the result of
> > > compiling that version of the source code release and its
> dependencies."
> > > I don't think my binary package violates any of these.
> >
> > +1 The PMC VOTE applies to source code, only. If someone wants to
> > rebuild the binary tarball with native libs and replace this one,
> > that's fine.
> >
> > My reading of the above is that source code must be distributed with
> > binaries, not that we omit the source code from binary releases... -C
> >
> > > But I'll upload an additional tar.gz with native bits and no src, as
> you
> > > guys requested.
> > > Will keep it as RC0 as there is no source code change and it comes from
> > the
> > > same build.
> > > Hope this is satisfactory.
> > >
> > > Thanks,
> > > --Konstantin
> > >
> > > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <andrew.wang@cloudera.com
> >
> > > wrote:
> > >
> > >> I agree with Brahma on the two issues flagged (having src in the
> binary
> > >> tarball, missing native libs). These are regressions from prior
> > releases.
> > >>
> > >> As an aside, "we release binaries as a convenience" doesn't relax the
> > >> quality bar. The binaries are linked on our website and distributed
> > through
> > >> official Apache channels. They have to adhere to Apache release
> > >> requirements. And, most users consume our work via Maven dependencies,
> > >> which are binary artifacts.
> > >>
> > >> http://www.apache.org/legal/release-policy.html goes into this in
> more
> > >> detail. A release must minimally include source packages, and can also
> > >> include binary artifacts.
> > >>
> > >> Best,
> > >> Andrew
> > >>
> > >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
> > >> shv.hadoop@gmail.com> wrote:
> > >>
> > >>> To avoid any confusion in this regard. I built RC0 manually in
> > compliance
> > >>> with Apache release policy
> > >>> http://www.apache.org/legal/release-policy.html
> > >>> I edited the HowToReleasePreDSBCR page to make sure people don't use
> > >>> Jenkins option for building.
> > >>>
> > >>> A side note. This particular build is broken anyways, so no worries
> > there.
> > >>> I think though it would be useful to have it working for testing and
> > as a
> > >>> packaging standard.
> > >>>
> > >>> Thanks,
> > >>> --Konstantin
> > >>>
> > >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
> > >>> aw@effectivemachines.com
> > >>> > wrote:
> > >>>
> > >>> >
> > >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
> > >>> shv.hadoop@gmail.com>
> > >>> > wrote:
> > >>> > >
> > >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
> > >>> >
> > >>> >         FYI:
> > >>> >
> > >>> >                 If you are using ASF Jenkins to create an ASF
> release
> > >>> > artifact, it's pretty much an automatic vote failure as any such
> > >>> release is
> > >>> > in violation of ASF policy.
> > >>> >
> > >>> >
> > >>>
> > >>
> > >>
> >
>



-- 

*Zhou, Ye  **周晔*

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Ye Zhou <zh...@gmail.com>.
Hi, Konstantin.
Thanks for leading the release.

+1 (non-binding)

-Built from the source on mac with jdk_1.8.0_40
-Built on internal Jenkins with jdk_1.8.0_40.
-Deployed on a cluster with 121 nodes(Including RM, NM, NN, DN)
-Basic shell commands
-Distcp 3.7TB data to HDFS
-Run GridMix test which submitted 15K MR jobs in 5 hours(trace generated
from real production job trace)

On Mon, Jul 31, 2017 at 6:57 PM, Konstantin Shvachko <sh...@gmail.com>
wrote:

> Uploaded new binaries hadoop-2.7.4-RC0.tar.gz, which adds lib/native/.
> Same place: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>
> Thanks,
> --Konstantin
>
> On Mon, Jul 31, 2017 at 3:56 PM, Chris Douglas <cd...@apache.org>
> wrote:
>
> > On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
> > <sh...@gmail.com> wrote:
> > > For the packaging, here is the exact phrasing from the sited
> > release-policy
> > > document relevant to binaries:
> > > "As a convenience to users that might not have the appropriate tools to
> > > build a compiled version of the source, binary/bytecode packages MAY be
> > > distributed alongside official Apache releases. In all such cases, the
> > > binary/bytecode package MUST have the same version number as the source
> > > release and MUST only add binary/bytecode files that are the result of
> > > compiling that version of the source code release and its
> dependencies."
> > > I don't think my binary package violates any of these.
> >
> > +1 The PMC VOTE applies to source code, only. If someone wants to
> > rebuild the binary tarball with native libs and replace this one,
> > that's fine.
> >
> > My reading of the above is that source code must be distributed with
> > binaries, not that we omit the source code from binary releases... -C
> >
> > > But I'll upload an additional tar.gz with native bits and no src, as
> you
> > > guys requested.
> > > Will keep it as RC0 as there is no source code change and it comes from
> > the
> > > same build.
> > > Hope this is satisfactory.
> > >
> > > Thanks,
> > > --Konstantin
> > >
> > > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <andrew.wang@cloudera.com
> >
> > > wrote:
> > >
> > >> I agree with Brahma on the two issues flagged (having src in the
> binary
> > >> tarball, missing native libs). These are regressions from prior
> > releases.
> > >>
> > >> As an aside, "we release binaries as a convenience" doesn't relax the
> > >> quality bar. The binaries are linked on our website and distributed
> > through
> > >> official Apache channels. They have to adhere to Apache release
> > >> requirements. And, most users consume our work via Maven dependencies,
> > >> which are binary artifacts.
> > >>
> > >> http://www.apache.org/legal/release-policy.html goes into this in
> more
> > >> detail. A release must minimally include source packages, and can also
> > >> include binary artifacts.
> > >>
> > >> Best,
> > >> Andrew
> > >>
> > >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
> > >> shv.hadoop@gmail.com> wrote:
> > >>
> > >>> To avoid any confusion in this regard. I built RC0 manually in
> > compliance
> > >>> with Apache release policy
> > >>> http://www.apache.org/legal/release-policy.html
> > >>> I edited the HowToReleasePreDSBCR page to make sure people don't use
> > >>> Jenkins option for building.
> > >>>
> > >>> A side note. This particular build is broken anyways, so no worries
> > there.
> > >>> I think though it would be useful to have it working for testing and
> > as a
> > >>> packaging standard.
> > >>>
> > >>> Thanks,
> > >>> --Konstantin
> > >>>
> > >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
> > >>> aw@effectivemachines.com
> > >>> > wrote:
> > >>>
> > >>> >
> > >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
> > >>> shv.hadoop@gmail.com>
> > >>> > wrote:
> > >>> > >
> > >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
> > >>> >
> > >>> >         FYI:
> > >>> >
> > >>> >                 If you are using ASF Jenkins to create an ASF
> release
> > >>> > artifact, it's pretty much an automatic vote failure as any such
> > >>> release is
> > >>> > in violation of ASF policy.
> > >>> >
> > >>> >
> > >>>
> > >>
> > >>
> >
>



-- 

*Zhou, Ye  **周晔*

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Eric Payne <er...@yahoo.com.INVALID>.
+1 (binding)
Tested the following:




- Application History Server

-- Apps can be observed from UI
-- App and container metadata can be retrieved via REST APIs



- RM UI

-- Can kill an app from the RM UI


- Apps run in different frameworks. Frameworks tested: MR and yarn shell

-- In yarn shell framework, containers are preserved across AM restart.


- Cross-queue preemption (Inter-queue):

-- Inter-queue preemption will preempt the correct number of containers from a p
reemptable queue.

-- Inter-queue preemption will not preempt from queues with preemption disabled.


- Labeled queues work as expected where apps assigned to a queue that has a spec
ific label will run only on labeled nodes.




________________________________
From: Konstantin Shvachko <sh...@gmail.com>
To: Chris Douglas <cd...@apache.org> 
Cc: Andrew Wang <an...@cloudera.com>; Allen Wittenauer <aw...@effectivemachines.com>; "common-dev@hadoop.apache.org" <co...@hadoop.apache.org>; "hdfs-dev@hadoop.apache.org" <hd...@hadoop.apache.org>; "mapreduce-dev@hadoop.apache.org" <ma...@hadoop.apache.org>; "yarn-dev@hadoop.apache.org" <ya...@hadoop.apache.org>
Sent: Monday, July 31, 2017 8:57 PM
Subject: Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)



Uploaded new binaries hadoop-2.7.4-RC0.tar.gz, which adds lib/native/.
Same place: http://home.apache.org/~shv/hadoop-2.7.4-RC0/

Thanks,
--Konstantin


On Mon, Jul 31, 2017 at 3:56 PM, Chris Douglas <cd...@apache.org> wrote:

> On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
> <sh...@gmail.com> wrote:
> > For the packaging, here is the exact phrasing from the sited
> release-policy
> > document relevant to binaries:
> > "As a convenience to users that might not have the appropriate tools to
> > build a compiled version of the source, binary/bytecode packages MAY be
> > distributed alongside official Apache releases. In all such cases, the
> > binary/bytecode package MUST have the same version number as the source
> > release and MUST only add binary/bytecode files that are the result of
> > compiling that version of the source code release and its dependencies."
> > I don't think my binary package violates any of these.
>
> +1 The PMC VOTE applies to source code, only. If someone wants to
> rebuild the binary tarball with native libs and replace this one,
> that's fine.
>
> My reading of the above is that source code must be distributed with
> binaries, not that we omit the source code from binary releases... -C
>
> > But I'll upload an additional tar.gz with native bits and no src, as you
> > guys requested.
> > Will keep it as RC0 as there is no source code change and it comes from
> the
> > same build.
> > Hope this is satisfactory.
> >
> > Thanks,
> > --Konstantin
> >
> > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <an...@cloudera.com>
> > wrote:
> >
> >> I agree with Brahma on the two issues flagged (having src in the binary
> >> tarball, missing native libs). These are regressions from prior
> releases.
> >>
> >> As an aside, "we release binaries as a convenience" doesn't relax the
> >> quality bar. The binaries are linked on our website and distributed
> through
> >> official Apache channels. They have to adhere to Apache release
> >> requirements. And, most users consume our work via Maven dependencies,
> >> which are binary artifacts.
> >>
> >> http://www.apache.org/legal/release-policy.html goes into this in more
> >> detail. A release must minimally include source packages, and can also
> >> include binary artifacts.
> >>
> >> Best,
> >> Andrew
> >>
> >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
> >> shv.hadoop@gmail.com> wrote:
> >>
> >>> To avoid any confusion in this regard. I built RC0 manually in
> compliance
> >>> with Apache release policy
> >>> http://www.apache.org/legal/release-policy.html
> >>> I edited the HowToReleasePreDSBCR page to make sure people don't use
> >>> Jenkins option for building.
> >>>
> >>> A side note. This particular build is broken anyways, so no worries
> there.
> >>> I think though it would be useful to have it working for testing and
> as a
> >>> packaging standard.
> >>>
> >>> Thanks,
> >>> --Konstantin
> >>>
> >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
> >>> aw@effectivemachines.com
> >>> > wrote:
> >>>
> >>> >
> >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
> >>> shv.hadoop@gmail.com>
> >>> > wrote:
> >>> > >
> >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
> >>> >
> >>> >         FYI:
> >>> >
> >>> >                 If you are using ASF Jenkins to create an ASF release
> >>> > artifact, it's pretty much an automatic vote failure as any such
> >>> release is
> >>> > in violation of 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.7.4 (RC0)

Posted by Edwina Lu <ed...@linkedin.com>.
+1 (non-binding). 

Thanks,

Edwina

On 7/31/17, 6:57 PM, "Konstantin Shvachko" <sh...@gmail.com> wrote:

    Uploaded new binaries hadoop-2.7.4-RC0.tar.gz, which adds lib/native/.
    Same place: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
    
    Thanks,
    --Konstantin
    
    On Mon, Jul 31, 2017 at 3:56 PM, Chris Douglas <cd...@apache.org> wrote:
    
    > On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
    > <sh...@gmail.com> wrote:
    > > For the packaging, here is the exact phrasing from the sited
    > release-policy
    > > document relevant to binaries:
    > > "As a convenience to users that might not have the appropriate tools to
    > > build a compiled version of the source, binary/bytecode packages MAY be
    > > distributed alongside official Apache releases. In all such cases, the
    > > binary/bytecode package MUST have the same version number as the source
    > > release and MUST only add binary/bytecode files that are the result of
    > > compiling that version of the source code release and its dependencies."
    > > I don't think my binary package violates any of these.
    >
    > +1 The PMC VOTE applies to source code, only. If someone wants to
    > rebuild the binary tarball with native libs and replace this one,
    > that's fine.
    >
    > My reading of the above is that source code must be distributed with
    > binaries, not that we omit the source code from binary releases... -C
    >
    > > But I'll upload an additional tar.gz with native bits and no src, as you
    > > guys requested.
    > > Will keep it as RC0 as there is no source code change and it comes from
    > the
    > > same build.
    > > Hope this is satisfactory.
    > >
    > > Thanks,
    > > --Konstantin
    > >
    > > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <an...@cloudera.com>
    > > wrote:
    > >
    > >> I agree with Brahma on the two issues flagged (having src in the binary
    > >> tarball, missing native libs). These are regressions from prior
    > releases.
    > >>
    > >> As an aside, "we release binaries as a convenience" doesn't relax the
    > >> quality bar. The binaries are linked on our website and distributed
    > through
    > >> official Apache channels. They have to adhere to Apache release
    > >> requirements. And, most users consume our work via Maven dependencies,
    > >> which are binary artifacts.
    > >>
    > >> http://www.apache.org/legal/release-policy.html goes into this in more
    > >> detail. A release must minimally include source packages, and can also
    > >> include binary artifacts.
    > >>
    > >> Best,
    > >> Andrew
    > >>
    > >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
    > >> shv.hadoop@gmail.com> wrote:
    > >>
    > >>> To avoid any confusion in this regard. I built RC0 manually in
    > compliance
    > >>> with Apache release policy
    > >>> http://www.apache.org/legal/release-policy.html
    > >>> I edited the HowToReleasePreDSBCR page to make sure people don't use
    > >>> Jenkins option for building.
    > >>>
    > >>> A side note. This particular build is broken anyways, so no worries
    > there.
    > >>> I think though it would be useful to have it working for testing and
    > as a
    > >>> packaging standard.
    > >>>
    > >>> Thanks,
    > >>> --Konstantin
    > >>>
    > >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
    > >>> aw@effectivemachines.com
    > >>> > wrote:
    > >>>
    > >>> >
    > >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
    > >>> shv.hadoop@gmail.com>
    > >>> > wrote:
    > >>> > >
    > >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
    > >>> >
    > >>> >         FYI:
    > >>> >
    > >>> >                 If you are using ASF Jenkins to create an ASF release
    > >>> > artifact, it's pretty much an automatic vote failure as any such
    > >>> release is
    > >>> > in violation of ASF policy.
    > >>> >
    > >>> >
    > >>>
    > >>
    > >>
    >
    


Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Ye Zhou <zh...@gmail.com>.
Hi, Konstantin.
Thanks for leading the release.

+1 (non-binding)

-Built from the source on mac with jdk_1.8.0_40
-Built on internal Jenkins with jdk_1.8.0_40.
-Deployed on a cluster with 121 nodes(Including RM, NM, NN, DN)
-Basic shell commands
-Distcp 3.7TB data to HDFS
-Run GridMix test which submitted 15K MR jobs in 5 hours(trace generated
from real production job trace)

On Mon, Jul 31, 2017 at 6:57 PM, Konstantin Shvachko <sh...@gmail.com>
wrote:

> Uploaded new binaries hadoop-2.7.4-RC0.tar.gz, which adds lib/native/.
> Same place: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>
> Thanks,
> --Konstantin
>
> On Mon, Jul 31, 2017 at 3:56 PM, Chris Douglas <cd...@apache.org>
> wrote:
>
> > On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
> > <sh...@gmail.com> wrote:
> > > For the packaging, here is the exact phrasing from the sited
> > release-policy
> > > document relevant to binaries:
> > > "As a convenience to users that might not have the appropriate tools to
> > > build a compiled version of the source, binary/bytecode packages MAY be
> > > distributed alongside official Apache releases. In all such cases, the
> > > binary/bytecode package MUST have the same version number as the source
> > > release and MUST only add binary/bytecode files that are the result of
> > > compiling that version of the source code release and its
> dependencies."
> > > I don't think my binary package violates any of these.
> >
> > +1 The PMC VOTE applies to source code, only. If someone wants to
> > rebuild the binary tarball with native libs and replace this one,
> > that's fine.
> >
> > My reading of the above is that source code must be distributed with
> > binaries, not that we omit the source code from binary releases... -C
> >
> > > But I'll upload an additional tar.gz with native bits and no src, as
> you
> > > guys requested.
> > > Will keep it as RC0 as there is no source code change and it comes from
> > the
> > > same build.
> > > Hope this is satisfactory.
> > >
> > > Thanks,
> > > --Konstantin
> > >
> > > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <andrew.wang@cloudera.com
> >
> > > wrote:
> > >
> > >> I agree with Brahma on the two issues flagged (having src in the
> binary
> > >> tarball, missing native libs). These are regressions from prior
> > releases.
> > >>
> > >> As an aside, "we release binaries as a convenience" doesn't relax the
> > >> quality bar. The binaries are linked on our website and distributed
> > through
> > >> official Apache channels. They have to adhere to Apache release
> > >> requirements. And, most users consume our work via Maven dependencies,
> > >> which are binary artifacts.
> > >>
> > >> http://www.apache.org/legal/release-policy.html goes into this in
> more
> > >> detail. A release must minimally include source packages, and can also
> > >> include binary artifacts.
> > >>
> > >> Best,
> > >> Andrew
> > >>
> > >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
> > >> shv.hadoop@gmail.com> wrote:
> > >>
> > >>> To avoid any confusion in this regard. I built RC0 manually in
> > compliance
> > >>> with Apache release policy
> > >>> http://www.apache.org/legal/release-policy.html
> > >>> I edited the HowToReleasePreDSBCR page to make sure people don't use
> > >>> Jenkins option for building.
> > >>>
> > >>> A side note. This particular build is broken anyways, so no worries
> > there.
> > >>> I think though it would be useful to have it working for testing and
> > as a
> > >>> packaging standard.
> > >>>
> > >>> Thanks,
> > >>> --Konstantin
> > >>>
> > >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
> > >>> aw@effectivemachines.com
> > >>> > wrote:
> > >>>
> > >>> >
> > >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
> > >>> shv.hadoop@gmail.com>
> > >>> > wrote:
> > >>> > >
> > >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
> > >>> >
> > >>> >         FYI:
> > >>> >
> > >>> >                 If you are using ASF Jenkins to create an ASF
> release
> > >>> > artifact, it's pretty much an automatic vote failure as any such
> > >>> release is
> > >>> > in violation of ASF policy.
> > >>> >
> > >>> >
> > >>>
> > >>
> > >>
> >
>



-- 

*Zhou, Ye  **周晔*

RE: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Brahma Reddy Battula <br...@huawei.com>.
Hi Konstantin,

Thanks a lot again for your efforts.

+1  (non-binding)

-Built from the source on Suse-Linux with jdk_ 1.8.0_40
-Installed the HA cluster
-Verified basic shell commands
-Ran sample jobs
-Did the regression on IBR Feature, Balancer/mover,fsck

Downloaded the latest tarball, it contains the native and nodemanger can start (NM will not start without native). And install pseudo cluster and did basic verification.

IMHO, we should include natives in the tarball for user convenience (who doesn't have build tool can use for quick regression) 

As we are separately giving hadoop-2.7.4-RC0-src.tar.gz, still we need to include /src in tarball..?

As Andrew mentioned, these two are regression to prior release.


--Brahma Reddy Battula

-----Original Message-----
From: Konstantin Shvachko [mailto:shv.hadoop@gmail.com] 
Sent: 01 August 2017 09:57
To: Chris Douglas
Cc: Andrew Wang; Allen Wittenauer; common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org
Subject: Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Uploaded new binaries hadoop-2.7.4-RC0.tar.gz, which adds lib/native/.
Same place: http://home.apache.org/~shv/hadoop-2.7.4-RC0/

Thanks,
--Konstantin

On Mon, Jul 31, 2017 at 3:56 PM, Chris Douglas <cd...@apache.org> wrote:

> On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko 
> <sh...@gmail.com> wrote:
> > For the packaging, here is the exact phrasing from the sited
> release-policy
> > document relevant to binaries:
> > "As a convenience to users that might not have the appropriate tools 
> > to build a compiled version of the source, binary/bytecode packages 
> > MAY be distributed alongside official Apache releases. In all such 
> > cases, the binary/bytecode package MUST have the same version number 
> > as the source release and MUST only add binary/bytecode files that 
> > are the result of compiling that version of the source code release and its dependencies."
> > I don't think my binary package violates any of these.
>
> +1 The PMC VOTE applies to source code, only. If someone wants to
> rebuild the binary tarball with native libs and replace this one, 
> that's fine.
>
> My reading of the above is that source code must be distributed with 
> binaries, not that we omit the source code from binary releases... -C
>
> > But I'll upload an additional tar.gz with native bits and no src, as 
> > you guys requested.
> > Will keep it as RC0 as there is no source code change and it comes 
> > from
> the
> > same build.
> > Hope this is satisfactory.
> >
> > Thanks,
> > --Konstantin
> >
> > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang 
> > <an...@cloudera.com>
> > wrote:
> >
> >> I agree with Brahma on the two issues flagged (having src in the 
> >> binary tarball, missing native libs). These are regressions from 
> >> prior
> releases.
> >>
> >> As an aside, "we release binaries as a convenience" doesn't relax 
> >> the quality bar. The binaries are linked on our website and 
> >> distributed
> through
> >> official Apache channels. They have to adhere to Apache release 
> >> requirements. And, most users consume our work via Maven 
> >> dependencies, which are binary artifacts.
> >>
> >> http://www.apache.org/legal/release-policy.html goes into this in 
> >> more detail. A release must minimally include source packages, and 
> >> can also include binary artifacts.
> >>
> >> Best,
> >> Andrew
> >>
> >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko < 
> >> shv.hadoop@gmail.com> wrote:
> >>
> >>> To avoid any confusion in this regard. I built RC0 manually in
> compliance
> >>> with Apache release policy
> >>> http://www.apache.org/legal/release-policy.html
> >>> I edited the HowToReleasePreDSBCR page to make sure people don't 
> >>> use Jenkins option for building.
> >>>
> >>> A side note. This particular build is broken anyways, so no 
> >>> worries
> there.
> >>> I think though it would be useful to have it working for testing 
> >>> and
> as a
> >>> packaging standard.
> >>>
> >>> Thanks,
> >>> --Konstantin
> >>>
> >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer < 
> >>> aw@effectivemachines.com
> >>> > wrote:
> >>>
> >>> >
> >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
> >>> shv.hadoop@gmail.com>
> >>> > wrote:
> >>> > >
> >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
> >>> >
> >>> >         FYI:
> >>> >
> >>> >                 If you are using ASF Jenkins to create an ASF 
> >>> > release artifact, it's pretty much an automatic vote failure as 
> >>> > any such
> >>> release is
> >>> > in violation of ASF policy.
> >>> >
> >>> >
> >>>
> >>
> >>
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Eric Payne <er...@yahoo.com.INVALID>.
+1 (binding)
Tested the following:




- Application History Server

-- Apps can be observed from UI
-- App and container metadata can be retrieved via REST APIs



- RM UI

-- Can kill an app from the RM UI


- Apps run in different frameworks. Frameworks tested: MR and yarn shell

-- In yarn shell framework, containers are preserved across AM restart.


- Cross-queue preemption (Inter-queue):

-- Inter-queue preemption will preempt the correct number of containers from a p
reemptable queue.

-- Inter-queue preemption will not preempt from queues with preemption disabled.


- Labeled queues work as expected where apps assigned to a queue that has a spec
ific label will run only on labeled nodes.




________________________________
From: Konstantin Shvachko <sh...@gmail.com>
To: Chris Douglas <cd...@apache.org> 
Cc: Andrew Wang <an...@cloudera.com>; Allen Wittenauer <aw...@effectivemachines.com>; "common-dev@hadoop.apache.org" <co...@hadoop.apache.org>; "hdfs-dev@hadoop.apache.org" <hd...@hadoop.apache.org>; "mapreduce-dev@hadoop.apache.org" <ma...@hadoop.apache.org>; "yarn-dev@hadoop.apache.org" <ya...@hadoop.apache.org>
Sent: Monday, July 31, 2017 8:57 PM
Subject: Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)



Uploaded new binaries hadoop-2.7.4-RC0.tar.gz, which adds lib/native/.
Same place: http://home.apache.org/~shv/hadoop-2.7.4-RC0/

Thanks,
--Konstantin


On Mon, Jul 31, 2017 at 3:56 PM, Chris Douglas <cd...@apache.org> wrote:

> On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
> <sh...@gmail.com> wrote:
> > For the packaging, here is the exact phrasing from the sited
> release-policy
> > document relevant to binaries:
> > "As a convenience to users that might not have the appropriate tools to
> > build a compiled version of the source, binary/bytecode packages MAY be
> > distributed alongside official Apache releases. In all such cases, the
> > binary/bytecode package MUST have the same version number as the source
> > release and MUST only add binary/bytecode files that are the result of
> > compiling that version of the source code release and its dependencies."
> > I don't think my binary package violates any of these.
>
> +1 The PMC VOTE applies to source code, only. If someone wants to
> rebuild the binary tarball with native libs and replace this one,
> that's fine.
>
> My reading of the above is that source code must be distributed with
> binaries, not that we omit the source code from binary releases... -C
>
> > But I'll upload an additional tar.gz with native bits and no src, as you
> > guys requested.
> > Will keep it as RC0 as there is no source code change and it comes from
> the
> > same build.
> > Hope this is satisfactory.
> >
> > Thanks,
> > --Konstantin
> >
> > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <an...@cloudera.com>
> > wrote:
> >
> >> I agree with Brahma on the two issues flagged (having src in the binary
> >> tarball, missing native libs). These are regressions from prior
> releases.
> >>
> >> As an aside, "we release binaries as a convenience" doesn't relax the
> >> quality bar. The binaries are linked on our website and distributed
> through
> >> official Apache channels. They have to adhere to Apache release
> >> requirements. And, most users consume our work via Maven dependencies,
> >> which are binary artifacts.
> >>
> >> http://www.apache.org/legal/release-policy.html goes into this in more
> >> detail. A release must minimally include source packages, and can also
> >> include binary artifacts.
> >>
> >> Best,
> >> Andrew
> >>
> >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
> >> shv.hadoop@gmail.com> wrote:
> >>
> >>> To avoid any confusion in this regard. I built RC0 manually in
> compliance
> >>> with Apache release policy
> >>> http://www.apache.org/legal/release-policy.html
> >>> I edited the HowToReleasePreDSBCR page to make sure people don't use
> >>> Jenkins option for building.
> >>>
> >>> A side note. This particular build is broken anyways, so no worries
> there.
> >>> I think though it would be useful to have it working for testing and
> as a
> >>> packaging standard.
> >>>
> >>> Thanks,
> >>> --Konstantin
> >>>
> >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
> >>> aw@effectivemachines.com
> >>> > wrote:
> >>>
> >>> >
> >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
> >>> shv.hadoop@gmail.com>
> >>> > wrote:
> >>> > >
> >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
> >>> >
> >>> >         FYI:
> >>> >
> >>> >                 If you are using ASF Jenkins to create an ASF release
> >>> > artifact, it's pretty much an automatic vote failure as any such
> >>> release is
> >>> > in violation of 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.7.4 (RC0)

Posted by Ye Zhou <zh...@gmail.com>.
Hi, Konstantin.
Thanks for leading the release.

+1 (non-binding)

-Built from the source on mac with jdk_1.8.0_40
-Built on internal Jenkins with jdk_1.8.0_40.
-Deployed on a cluster with 121 nodes(Including RM, NM, NN, DN)
-Basic shell commands
-Distcp 3.7TB data to HDFS
-Run GridMix test which submitted 15K MR jobs in 5 hours(trace generated
from real production job trace)

On Mon, Jul 31, 2017 at 6:57 PM, Konstantin Shvachko <sh...@gmail.com>
wrote:

> Uploaded new binaries hadoop-2.7.4-RC0.tar.gz, which adds lib/native/.
> Same place: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>
> Thanks,
> --Konstantin
>
> On Mon, Jul 31, 2017 at 3:56 PM, Chris Douglas <cd...@apache.org>
> wrote:
>
> > On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
> > <sh...@gmail.com> wrote:
> > > For the packaging, here is the exact phrasing from the sited
> > release-policy
> > > document relevant to binaries:
> > > "As a convenience to users that might not have the appropriate tools to
> > > build a compiled version of the source, binary/bytecode packages MAY be
> > > distributed alongside official Apache releases. In all such cases, the
> > > binary/bytecode package MUST have the same version number as the source
> > > release and MUST only add binary/bytecode files that are the result of
> > > compiling that version of the source code release and its
> dependencies."
> > > I don't think my binary package violates any of these.
> >
> > +1 The PMC VOTE applies to source code, only. If someone wants to
> > rebuild the binary tarball with native libs and replace this one,
> > that's fine.
> >
> > My reading of the above is that source code must be distributed with
> > binaries, not that we omit the source code from binary releases... -C
> >
> > > But I'll upload an additional tar.gz with native bits and no src, as
> you
> > > guys requested.
> > > Will keep it as RC0 as there is no source code change and it comes from
> > the
> > > same build.
> > > Hope this is satisfactory.
> > >
> > > Thanks,
> > > --Konstantin
> > >
> > > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <andrew.wang@cloudera.com
> >
> > > wrote:
> > >
> > >> I agree with Brahma on the two issues flagged (having src in the
> binary
> > >> tarball, missing native libs). These are regressions from prior
> > releases.
> > >>
> > >> As an aside, "we release binaries as a convenience" doesn't relax the
> > >> quality bar. The binaries are linked on our website and distributed
> > through
> > >> official Apache channels. They have to adhere to Apache release
> > >> requirements. And, most users consume our work via Maven dependencies,
> > >> which are binary artifacts.
> > >>
> > >> http://www.apache.org/legal/release-policy.html goes into this in
> more
> > >> detail. A release must minimally include source packages, and can also
> > >> include binary artifacts.
> > >>
> > >> Best,
> > >> Andrew
> > >>
> > >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
> > >> shv.hadoop@gmail.com> wrote:
> > >>
> > >>> To avoid any confusion in this regard. I built RC0 manually in
> > compliance
> > >>> with Apache release policy
> > >>> http://www.apache.org/legal/release-policy.html
> > >>> I edited the HowToReleasePreDSBCR page to make sure people don't use
> > >>> Jenkins option for building.
> > >>>
> > >>> A side note. This particular build is broken anyways, so no worries
> > there.
> > >>> I think though it would be useful to have it working for testing and
> > as a
> > >>> packaging standard.
> > >>>
> > >>> Thanks,
> > >>> --Konstantin
> > >>>
> > >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
> > >>> aw@effectivemachines.com
> > >>> > wrote:
> > >>>
> > >>> >
> > >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
> > >>> shv.hadoop@gmail.com>
> > >>> > wrote:
> > >>> > >
> > >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
> > >>> >
> > >>> >         FYI:
> > >>> >
> > >>> >                 If you are using ASF Jenkins to create an ASF
> release
> > >>> > artifact, it's pretty much an automatic vote failure as any such
> > >>> release is
> > >>> > in violation of ASF policy.
> > >>> >
> > >>> >
> > >>>
> > >>
> > >>
> >
>



-- 

*Zhou, Ye  **周晔*

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Fnu Ajay Kumar <aj...@hortonworks.com>.
+1 (non-binding)

Thanks for preparing the 2.7.4-RC0 release.

- Built from source on Mac OS X 10.12.6 with Java 1.8.0_111
- Deployed to a pseudo cluster
- Passed the following sanity checks
    - Basic dfs operations
    - Wordcount
    - DFSIO- read/write

Thanks,
Ajay


On 7/31/17, 6:57 PM, "Konstantin Shvachko" <sh...@gmail.com> wrote:

    Uploaded new binaries hadoop-2.7.4-RC0.tar.gz, which adds lib/native/.
    Same place: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
    
    Thanks,
    --Konstantin
    
    On Mon, Jul 31, 2017 at 3:56 PM, Chris Douglas <cd...@apache.org> wrote:
    
    > On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
    > <sh...@gmail.com> wrote:
    > > For the packaging, here is the exact phrasing from the sited
    > release-policy
    > > document relevant to binaries:
    > > "As a convenience to users that might not have the appropriate tools to
    > > build a compiled version of the source, binary/bytecode packages MAY be
    > > distributed alongside official Apache releases. In all such cases, the
    > > binary/bytecode package MUST have the same version number as the source
    > > release and MUST only add binary/bytecode files that are the result of
    > > compiling that version of the source code release and its dependencies."
    > > I don't think my binary package violates any of these.
    >
    > +1 The PMC VOTE applies to source code, only. If someone wants to
    > rebuild the binary tarball with native libs and replace this one,
    > that's fine.
    >
    > My reading of the above is that source code must be distributed with
    > binaries, not that we omit the source code from binary releases... -C
    >
    > > But I'll upload an additional tar.gz with native bits and no src, as you
    > > guys requested.
    > > Will keep it as RC0 as there is no source code change and it comes from
    > the
    > > same build.
    > > Hope this is satisfactory.
    > >
    > > Thanks,
    > > --Konstantin
    > >
    > > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <an...@cloudera.com>
    > > wrote:
    > >
    > >> I agree with Brahma on the two issues flagged (having src in the binary
    > >> tarball, missing native libs). These are regressions from prior
    > releases.
    > >>
    > >> As an aside, "we release binaries as a convenience" doesn't relax the
    > >> quality bar. The binaries are linked on our website and distributed
    > through
    > >> official Apache channels. They have to adhere to Apache release
    > >> requirements. And, most users consume our work via Maven dependencies,
    > >> which are binary artifacts.
    > >>
    > >> http://www.apache.org/legal/release-policy.html goes into this in more
    > >> detail. A release must minimally include source packages, and can also
    > >> include binary artifacts.
    > >>
    > >> Best,
    > >> Andrew
    > >>
    > >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
    > >> shv.hadoop@gmail.com> wrote:
    > >>
    > >>> To avoid any confusion in this regard. I built RC0 manually in
    > compliance
    > >>> with Apache release policy
    > >>> http://www.apache.org/legal/release-policy.html
    > >>> I edited the HowToReleasePreDSBCR page to make sure people don't use
    > >>> Jenkins option for building.
    > >>>
    > >>> A side note. This particular build is broken anyways, so no worries
    > there.
    > >>> I think though it would be useful to have it working for testing and
    > as a
    > >>> packaging standard.
    > >>>
    > >>> Thanks,
    > >>> --Konstantin
    > >>>
    > >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
    > >>> aw@effectivemachines.com
    > >>> > wrote:
    > >>>
    > >>> >
    > >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
    > >>> shv.hadoop@gmail.com>
    > >>> > wrote:
    > >>> > >
    > >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
    > >>> >
    > >>> >         FYI:
    > >>> >
    > >>> >                 If you are using ASF Jenkins to create an ASF release
    > >>> > artifact, it's pretty much an automatic vote failure as any such
    > >>> release is
    > >>> > in violation of ASF policy.
    > >>> >
    > >>> >
    > >>>
    > >>
    > >>
    >
    


Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Eric Payne <er...@yahoo.com.INVALID>.
+1 (binding)
Tested the following:




- Application History Server

-- Apps can be observed from UI
-- App and container metadata can be retrieved via REST APIs



- RM UI

-- Can kill an app from the RM UI


- Apps run in different frameworks. Frameworks tested: MR and yarn shell

-- In yarn shell framework, containers are preserved across AM restart.


- Cross-queue preemption (Inter-queue):

-- Inter-queue preemption will preempt the correct number of containers from a p
reemptable queue.

-- Inter-queue preemption will not preempt from queues with preemption disabled.


- Labeled queues work as expected where apps assigned to a queue that has a spec
ific label will run only on labeled nodes.




________________________________
From: Konstantin Shvachko <sh...@gmail.com>
To: Chris Douglas <cd...@apache.org> 
Cc: Andrew Wang <an...@cloudera.com>; Allen Wittenauer <aw...@effectivemachines.com>; "common-dev@hadoop.apache.org" <co...@hadoop.apache.org>; "hdfs-dev@hadoop.apache.org" <hd...@hadoop.apache.org>; "mapreduce-dev@hadoop.apache.org" <ma...@hadoop.apache.org>; "yarn-dev@hadoop.apache.org" <ya...@hadoop.apache.org>
Sent: Monday, July 31, 2017 8:57 PM
Subject: Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)



Uploaded new binaries hadoop-2.7.4-RC0.tar.gz, which adds lib/native/.
Same place: http://home.apache.org/~shv/hadoop-2.7.4-RC0/

Thanks,
--Konstantin


On Mon, Jul 31, 2017 at 3:56 PM, Chris Douglas <cd...@apache.org> wrote:

> On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
> <sh...@gmail.com> wrote:
> > For the packaging, here is the exact phrasing from the sited
> release-policy
> > document relevant to binaries:
> > "As a convenience to users that might not have the appropriate tools to
> > build a compiled version of the source, binary/bytecode packages MAY be
> > distributed alongside official Apache releases. In all such cases, the
> > binary/bytecode package MUST have the same version number as the source
> > release and MUST only add binary/bytecode files that are the result of
> > compiling that version of the source code release and its dependencies."
> > I don't think my binary package violates any of these.
>
> +1 The PMC VOTE applies to source code, only. If someone wants to
> rebuild the binary tarball with native libs and replace this one,
> that's fine.
>
> My reading of the above is that source code must be distributed with
> binaries, not that we omit the source code from binary releases... -C
>
> > But I'll upload an additional tar.gz with native bits and no src, as you
> > guys requested.
> > Will keep it as RC0 as there is no source code change and it comes from
> the
> > same build.
> > Hope this is satisfactory.
> >
> > Thanks,
> > --Konstantin
> >
> > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <an...@cloudera.com>
> > wrote:
> >
> >> I agree with Brahma on the two issues flagged (having src in the binary
> >> tarball, missing native libs). These are regressions from prior
> releases.
> >>
> >> As an aside, "we release binaries as a convenience" doesn't relax the
> >> quality bar. The binaries are linked on our website and distributed
> through
> >> official Apache channels. They have to adhere to Apache release
> >> requirements. And, most users consume our work via Maven dependencies,
> >> which are binary artifacts.
> >>
> >> http://www.apache.org/legal/release-policy.html goes into this in more
> >> detail. A release must minimally include source packages, and can also
> >> include binary artifacts.
> >>
> >> Best,
> >> Andrew
> >>
> >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
> >> shv.hadoop@gmail.com> wrote:
> >>
> >>> To avoid any confusion in this regard. I built RC0 manually in
> compliance
> >>> with Apache release policy
> >>> http://www.apache.org/legal/release-policy.html
> >>> I edited the HowToReleasePreDSBCR page to make sure people don't use
> >>> Jenkins option for building.
> >>>
> >>> A side note. This particular build is broken anyways, so no worries
> there.
> >>> I think though it would be useful to have it working for testing and
> as a
> >>> packaging standard.
> >>>
> >>> Thanks,
> >>> --Konstantin
> >>>
> >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
> >>> aw@effectivemachines.com
> >>> > wrote:
> >>>
> >>> >
> >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
> >>> shv.hadoop@gmail.com>
> >>> > wrote:
> >>> > >
> >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
> >>> >
> >>> >         FYI:
> >>> >
> >>> >                 If you are using ASF Jenkins to create an ASF release
> >>> > artifact, it's pretty much an automatic vote failure as any such
> >>> release is
> >>> > in violation of 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.7.4 (RC0)

Posted by Brahma Reddy Battula <br...@huawei.com>.
Hi Konstantin,

Thanks a lot again for your efforts.

+1  (non-binding)

-Built from the source on Suse-Linux with jdk_ 1.8.0_40
-Installed the HA cluster
-Verified basic shell commands
-Ran sample jobs
-Did the regression on IBR Feature, Balancer/mover,fsck

Downloaded the latest tarball, it contains the native and nodemanger can start (NM will not start without native). And install pseudo cluster and did basic verification.

IMHO, we should include natives in the tarball for user convenience (who doesn't have build tool can use for quick regression) 

As we are separately giving hadoop-2.7.4-RC0-src.tar.gz, still we need to include /src in tarball..?

As Andrew mentioned, these two are regression to prior release.


--Brahma Reddy Battula

-----Original Message-----
From: Konstantin Shvachko [mailto:shv.hadoop@gmail.com] 
Sent: 01 August 2017 09:57
To: Chris Douglas
Cc: Andrew Wang; Allen Wittenauer; common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org
Subject: Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Uploaded new binaries hadoop-2.7.4-RC0.tar.gz, which adds lib/native/.
Same place: http://home.apache.org/~shv/hadoop-2.7.4-RC0/

Thanks,
--Konstantin

On Mon, Jul 31, 2017 at 3:56 PM, Chris Douglas <cd...@apache.org> wrote:

> On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko 
> <sh...@gmail.com> wrote:
> > For the packaging, here is the exact phrasing from the sited
> release-policy
> > document relevant to binaries:
> > "As a convenience to users that might not have the appropriate tools 
> > to build a compiled version of the source, binary/bytecode packages 
> > MAY be distributed alongside official Apache releases. In all such 
> > cases, the binary/bytecode package MUST have the same version number 
> > as the source release and MUST only add binary/bytecode files that 
> > are the result of compiling that version of the source code release and its dependencies."
> > I don't think my binary package violates any of these.
>
> +1 The PMC VOTE applies to source code, only. If someone wants to
> rebuild the binary tarball with native libs and replace this one, 
> that's fine.
>
> My reading of the above is that source code must be distributed with 
> binaries, not that we omit the source code from binary releases... -C
>
> > But I'll upload an additional tar.gz with native bits and no src, as 
> > you guys requested.
> > Will keep it as RC0 as there is no source code change and it comes 
> > from
> the
> > same build.
> > Hope this is satisfactory.
> >
> > Thanks,
> > --Konstantin
> >
> > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang 
> > <an...@cloudera.com>
> > wrote:
> >
> >> I agree with Brahma on the two issues flagged (having src in the 
> >> binary tarball, missing native libs). These are regressions from 
> >> prior
> releases.
> >>
> >> As an aside, "we release binaries as a convenience" doesn't relax 
> >> the quality bar. The binaries are linked on our website and 
> >> distributed
> through
> >> official Apache channels. They have to adhere to Apache release 
> >> requirements. And, most users consume our work via Maven 
> >> dependencies, which are binary artifacts.
> >>
> >> http://www.apache.org/legal/release-policy.html goes into this in 
> >> more detail. A release must minimally include source packages, and 
> >> can also include binary artifacts.
> >>
> >> Best,
> >> Andrew
> >>
> >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko < 
> >> shv.hadoop@gmail.com> wrote:
> >>
> >>> To avoid any confusion in this regard. I built RC0 manually in
> compliance
> >>> with Apache release policy
> >>> http://www.apache.org/legal/release-policy.html
> >>> I edited the HowToReleasePreDSBCR page to make sure people don't 
> >>> use Jenkins option for building.
> >>>
> >>> A side note. This particular build is broken anyways, so no 
> >>> worries
> there.
> >>> I think though it would be useful to have it working for testing 
> >>> and
> as a
> >>> packaging standard.
> >>>
> >>> Thanks,
> >>> --Konstantin
> >>>
> >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer < 
> >>> aw@effectivemachines.com
> >>> > wrote:
> >>>
> >>> >
> >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
> >>> shv.hadoop@gmail.com>
> >>> > wrote:
> >>> > >
> >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
> >>> >
> >>> >         FYI:
> >>> >
> >>> >                 If you are using ASF Jenkins to create an ASF 
> >>> > release artifact, it's pretty much an automatic vote failure as 
> >>> > any such
> >>> release is
> >>> > in violation of ASF policy.
> >>> >
> >>> >
> >>>
> >>
> >>
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Fnu Ajay Kumar <aj...@hortonworks.com>.
+1 (non-binding)

Thanks for preparing the 2.7.4-RC0 release.

- Built from source on Mac OS X 10.12.6 with Java 1.8.0_111
- Deployed to a pseudo cluster
- Passed the following sanity checks
    - Basic dfs operations
    - Wordcount
    - DFSIO- read/write

Thanks,
Ajay


On 7/31/17, 6:57 PM, "Konstantin Shvachko" <sh...@gmail.com> wrote:

    Uploaded new binaries hadoop-2.7.4-RC0.tar.gz, which adds lib/native/.
    Same place: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
    
    Thanks,
    --Konstantin
    
    On Mon, Jul 31, 2017 at 3:56 PM, Chris Douglas <cd...@apache.org> wrote:
    
    > On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
    > <sh...@gmail.com> wrote:
    > > For the packaging, here is the exact phrasing from the sited
    > release-policy
    > > document relevant to binaries:
    > > "As a convenience to users that might not have the appropriate tools to
    > > build a compiled version of the source, binary/bytecode packages MAY be
    > > distributed alongside official Apache releases. In all such cases, the
    > > binary/bytecode package MUST have the same version number as the source
    > > release and MUST only add binary/bytecode files that are the result of
    > > compiling that version of the source code release and its dependencies."
    > > I don't think my binary package violates any of these.
    >
    > +1 The PMC VOTE applies to source code, only. If someone wants to
    > rebuild the binary tarball with native libs and replace this one,
    > that's fine.
    >
    > My reading of the above is that source code must be distributed with
    > binaries, not that we omit the source code from binary releases... -C
    >
    > > But I'll upload an additional tar.gz with native bits and no src, as you
    > > guys requested.
    > > Will keep it as RC0 as there is no source code change and it comes from
    > the
    > > same build.
    > > Hope this is satisfactory.
    > >
    > > Thanks,
    > > --Konstantin
    > >
    > > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <an...@cloudera.com>
    > > wrote:
    > >
    > >> I agree with Brahma on the two issues flagged (having src in the binary
    > >> tarball, missing native libs). These are regressions from prior
    > releases.
    > >>
    > >> As an aside, "we release binaries as a convenience" doesn't relax the
    > >> quality bar. The binaries are linked on our website and distributed
    > through
    > >> official Apache channels. They have to adhere to Apache release
    > >> requirements. And, most users consume our work via Maven dependencies,
    > >> which are binary artifacts.
    > >>
    > >> http://www.apache.org/legal/release-policy.html goes into this in more
    > >> detail. A release must minimally include source packages, and can also
    > >> include binary artifacts.
    > >>
    > >> Best,
    > >> Andrew
    > >>
    > >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
    > >> shv.hadoop@gmail.com> wrote:
    > >>
    > >>> To avoid any confusion in this regard. I built RC0 manually in
    > compliance
    > >>> with Apache release policy
    > >>> http://www.apache.org/legal/release-policy.html
    > >>> I edited the HowToReleasePreDSBCR page to make sure people don't use
    > >>> Jenkins option for building.
    > >>>
    > >>> A side note. This particular build is broken anyways, so no worries
    > there.
    > >>> I think though it would be useful to have it working for testing and
    > as a
    > >>> packaging standard.
    > >>>
    > >>> Thanks,
    > >>> --Konstantin
    > >>>
    > >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
    > >>> aw@effectivemachines.com
    > >>> > wrote:
    > >>>
    > >>> >
    > >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
    > >>> shv.hadoop@gmail.com>
    > >>> > wrote:
    > >>> > >
    > >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
    > >>> >
    > >>> >         FYI:
    > >>> >
    > >>> >                 If you are using ASF Jenkins to create an ASF release
    > >>> > artifact, it's pretty much an automatic vote failure as any such
    > >>> release is
    > >>> > in violation of ASF policy.
    > >>> >
    > >>> >
    > >>>
    > >>
    > >>
    >
    


Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Eric Payne <er...@yahoo.com.INVALID>.
+1 (binding)
Tested the following:




- Application History Server

-- Apps can be observed from UI
-- App and container metadata can be retrieved via REST APIs



- RM UI

-- Can kill an app from the RM UI


- Apps run in different frameworks. Frameworks tested: MR and yarn shell

-- In yarn shell framework, containers are preserved across AM restart.


- Cross-queue preemption (Inter-queue):

-- Inter-queue preemption will preempt the correct number of containers from a p
reemptable queue.

-- Inter-queue preemption will not preempt from queues with preemption disabled.


- Labeled queues work as expected where apps assigned to a queue that has a spec
ific label will run only on labeled nodes.




________________________________
From: Konstantin Shvachko <sh...@gmail.com>
To: Chris Douglas <cd...@apache.org> 
Cc: Andrew Wang <an...@cloudera.com>; Allen Wittenauer <aw...@effectivemachines.com>; "common-dev@hadoop.apache.org" <co...@hadoop.apache.org>; "hdfs-dev@hadoop.apache.org" <hd...@hadoop.apache.org>; "mapreduce-dev@hadoop.apache.org" <ma...@hadoop.apache.org>; "yarn-dev@hadoop.apache.org" <ya...@hadoop.apache.org>
Sent: Monday, July 31, 2017 8:57 PM
Subject: Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)



Uploaded new binaries hadoop-2.7.4-RC0.tar.gz, which adds lib/native/.
Same place: http://home.apache.org/~shv/hadoop-2.7.4-RC0/

Thanks,
--Konstantin


On Mon, Jul 31, 2017 at 3:56 PM, Chris Douglas <cd...@apache.org> wrote:

> On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
> <sh...@gmail.com> wrote:
> > For the packaging, here is the exact phrasing from the sited
> release-policy
> > document relevant to binaries:
> > "As a convenience to users that might not have the appropriate tools to
> > build a compiled version of the source, binary/bytecode packages MAY be
> > distributed alongside official Apache releases. In all such cases, the
> > binary/bytecode package MUST have the same version number as the source
> > release and MUST only add binary/bytecode files that are the result of
> > compiling that version of the source code release and its dependencies."
> > I don't think my binary package violates any of these.
>
> +1 The PMC VOTE applies to source code, only. If someone wants to
> rebuild the binary tarball with native libs and replace this one,
> that's fine.
>
> My reading of the above is that source code must be distributed with
> binaries, not that we omit the source code from binary releases... -C
>
> > But I'll upload an additional tar.gz with native bits and no src, as you
> > guys requested.
> > Will keep it as RC0 as there is no source code change and it comes from
> the
> > same build.
> > Hope this is satisfactory.
> >
> > Thanks,
> > --Konstantin
> >
> > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <an...@cloudera.com>
> > wrote:
> >
> >> I agree with Brahma on the two issues flagged (having src in the binary
> >> tarball, missing native libs). These are regressions from prior
> releases.
> >>
> >> As an aside, "we release binaries as a convenience" doesn't relax the
> >> quality bar. The binaries are linked on our website and distributed
> through
> >> official Apache channels. They have to adhere to Apache release
> >> requirements. And, most users consume our work via Maven dependencies,
> >> which are binary artifacts.
> >>
> >> http://www.apache.org/legal/release-policy.html goes into this in more
> >> detail. A release must minimally include source packages, and can also
> >> include binary artifacts.
> >>
> >> Best,
> >> Andrew
> >>
> >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
> >> shv.hadoop@gmail.com> wrote:
> >>
> >>> To avoid any confusion in this regard. I built RC0 manually in
> compliance
> >>> with Apache release policy
> >>> http://www.apache.org/legal/release-policy.html
> >>> I edited the HowToReleasePreDSBCR page to make sure people don't use
> >>> Jenkins option for building.
> >>>
> >>> A side note. This particular build is broken anyways, so no worries
> there.
> >>> I think though it would be useful to have it working for testing and
> as a
> >>> packaging standard.
> >>>
> >>> Thanks,
> >>> --Konstantin
> >>>
> >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
> >>> aw@effectivemachines.com
> >>> > wrote:
> >>>
> >>> >
> >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
> >>> shv.hadoop@gmail.com>
> >>> > wrote:
> >>> > >
> >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
> >>> >
> >>> >         FYI:
> >>> >
> >>> >                 If you are using ASF Jenkins to create an ASF release
> >>> > artifact, it's pretty much an automatic vote failure as any such
> >>> release is
> >>> > in violation of 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.7.4 (RC0)

Posted by Konstantin Shvachko <sh...@gmail.com>.
Uploaded new binaries hadoop-2.7.4-RC0.tar.gz, which adds lib/native/.
Same place: http://home.apache.org/~shv/hadoop-2.7.4-RC0/

Thanks,
--Konstantin

On Mon, Jul 31, 2017 at 3:56 PM, Chris Douglas <cd...@apache.org> wrote:

> On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
> <sh...@gmail.com> wrote:
> > For the packaging, here is the exact phrasing from the sited
> release-policy
> > document relevant to binaries:
> > "As a convenience to users that might not have the appropriate tools to
> > build a compiled version of the source, binary/bytecode packages MAY be
> > distributed alongside official Apache releases. In all such cases, the
> > binary/bytecode package MUST have the same version number as the source
> > release and MUST only add binary/bytecode files that are the result of
> > compiling that version of the source code release and its dependencies."
> > I don't think my binary package violates any of these.
>
> +1 The PMC VOTE applies to source code, only. If someone wants to
> rebuild the binary tarball with native libs and replace this one,
> that's fine.
>
> My reading of the above is that source code must be distributed with
> binaries, not that we omit the source code from binary releases... -C
>
> > But I'll upload an additional tar.gz with native bits and no src, as you
> > guys requested.
> > Will keep it as RC0 as there is no source code change and it comes from
> the
> > same build.
> > Hope this is satisfactory.
> >
> > Thanks,
> > --Konstantin
> >
> > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <an...@cloudera.com>
> > wrote:
> >
> >> I agree with Brahma on the two issues flagged (having src in the binary
> >> tarball, missing native libs). These are regressions from prior
> releases.
> >>
> >> As an aside, "we release binaries as a convenience" doesn't relax the
> >> quality bar. The binaries are linked on our website and distributed
> through
> >> official Apache channels. They have to adhere to Apache release
> >> requirements. And, most users consume our work via Maven dependencies,
> >> which are binary artifacts.
> >>
> >> http://www.apache.org/legal/release-policy.html goes into this in more
> >> detail. A release must minimally include source packages, and can also
> >> include binary artifacts.
> >>
> >> Best,
> >> Andrew
> >>
> >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
> >> shv.hadoop@gmail.com> wrote:
> >>
> >>> To avoid any confusion in this regard. I built RC0 manually in
> compliance
> >>> with Apache release policy
> >>> http://www.apache.org/legal/release-policy.html
> >>> I edited the HowToReleasePreDSBCR page to make sure people don't use
> >>> Jenkins option for building.
> >>>
> >>> A side note. This particular build is broken anyways, so no worries
> there.
> >>> I think though it would be useful to have it working for testing and
> as a
> >>> packaging standard.
> >>>
> >>> Thanks,
> >>> --Konstantin
> >>>
> >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
> >>> aw@effectivemachines.com
> >>> > wrote:
> >>>
> >>> >
> >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
> >>> shv.hadoop@gmail.com>
> >>> > wrote:
> >>> > >
> >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
> >>> >
> >>> >         FYI:
> >>> >
> >>> >                 If you are using ASF Jenkins to create an ASF release
> >>> > artifact, it's pretty much an automatic vote failure as any such
> >>> release is
> >>> > in violation of ASF policy.
> >>> >
> >>> >
> >>>
> >>
> >>
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Konstantin Shvachko <sh...@gmail.com>.
Uploaded new binaries hadoop-2.7.4-RC0.tar.gz, which adds lib/native/.
Same place: http://home.apache.org/~shv/hadoop-2.7.4-RC0/

Thanks,
--Konstantin

On Mon, Jul 31, 2017 at 3:56 PM, Chris Douglas <cd...@apache.org> wrote:

> On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
> <sh...@gmail.com> wrote:
> > For the packaging, here is the exact phrasing from the sited
> release-policy
> > document relevant to binaries:
> > "As a convenience to users that might not have the appropriate tools to
> > build a compiled version of the source, binary/bytecode packages MAY be
> > distributed alongside official Apache releases. In all such cases, the
> > binary/bytecode package MUST have the same version number as the source
> > release and MUST only add binary/bytecode files that are the result of
> > compiling that version of the source code release and its dependencies."
> > I don't think my binary package violates any of these.
>
> +1 The PMC VOTE applies to source code, only. If someone wants to
> rebuild the binary tarball with native libs and replace this one,
> that's fine.
>
> My reading of the above is that source code must be distributed with
> binaries, not that we omit the source code from binary releases... -C
>
> > But I'll upload an additional tar.gz with native bits and no src, as you
> > guys requested.
> > Will keep it as RC0 as there is no source code change and it comes from
> the
> > same build.
> > Hope this is satisfactory.
> >
> > Thanks,
> > --Konstantin
> >
> > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <an...@cloudera.com>
> > wrote:
> >
> >> I agree with Brahma on the two issues flagged (having src in the binary
> >> tarball, missing native libs). These are regressions from prior
> releases.
> >>
> >> As an aside, "we release binaries as a convenience" doesn't relax the
> >> quality bar. The binaries are linked on our website and distributed
> through
> >> official Apache channels. They have to adhere to Apache release
> >> requirements. And, most users consume our work via Maven dependencies,
> >> which are binary artifacts.
> >>
> >> http://www.apache.org/legal/release-policy.html goes into this in more
> >> detail. A release must minimally include source packages, and can also
> >> include binary artifacts.
> >>
> >> Best,
> >> Andrew
> >>
> >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
> >> shv.hadoop@gmail.com> wrote:
> >>
> >>> To avoid any confusion in this regard. I built RC0 manually in
> compliance
> >>> with Apache release policy
> >>> http://www.apache.org/legal/release-policy.html
> >>> I edited the HowToReleasePreDSBCR page to make sure people don't use
> >>> Jenkins option for building.
> >>>
> >>> A side note. This particular build is broken anyways, so no worries
> there.
> >>> I think though it would be useful to have it working for testing and
> as a
> >>> packaging standard.
> >>>
> >>> Thanks,
> >>> --Konstantin
> >>>
> >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
> >>> aw@effectivemachines.com
> >>> > wrote:
> >>>
> >>> >
> >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
> >>> shv.hadoop@gmail.com>
> >>> > wrote:
> >>> > >
> >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
> >>> >
> >>> >         FYI:
> >>> >
> >>> >                 If you are using ASF Jenkins to create an ASF release
> >>> > artifact, it's pretty much an automatic vote failure as any such
> >>> release is
> >>> > in violation of ASF policy.
> >>> >
> >>> >
> >>>
> >>
> >>
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Konstantin Shvachko <sh...@gmail.com>.
Uploaded new binaries hadoop-2.7.4-RC0.tar.gz, which adds lib/native/.
Same place: http://home.apache.org/~shv/hadoop-2.7.4-RC0/

Thanks,
--Konstantin

On Mon, Jul 31, 2017 at 3:56 PM, Chris Douglas <cd...@apache.org> wrote:

> On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
> <sh...@gmail.com> wrote:
> > For the packaging, here is the exact phrasing from the sited
> release-policy
> > document relevant to binaries:
> > "As a convenience to users that might not have the appropriate tools to
> > build a compiled version of the source, binary/bytecode packages MAY be
> > distributed alongside official Apache releases. In all such cases, the
> > binary/bytecode package MUST have the same version number as the source
> > release and MUST only add binary/bytecode files that are the result of
> > compiling that version of the source code release and its dependencies."
> > I don't think my binary package violates any of these.
>
> +1 The PMC VOTE applies to source code, only. If someone wants to
> rebuild the binary tarball with native libs and replace this one,
> that's fine.
>
> My reading of the above is that source code must be distributed with
> binaries, not that we omit the source code from binary releases... -C
>
> > But I'll upload an additional tar.gz with native bits and no src, as you
> > guys requested.
> > Will keep it as RC0 as there is no source code change and it comes from
> the
> > same build.
> > Hope this is satisfactory.
> >
> > Thanks,
> > --Konstantin
> >
> > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <an...@cloudera.com>
> > wrote:
> >
> >> I agree with Brahma on the two issues flagged (having src in the binary
> >> tarball, missing native libs). These are regressions from prior
> releases.
> >>
> >> As an aside, "we release binaries as a convenience" doesn't relax the
> >> quality bar. The binaries are linked on our website and distributed
> through
> >> official Apache channels. They have to adhere to Apache release
> >> requirements. And, most users consume our work via Maven dependencies,
> >> which are binary artifacts.
> >>
> >> http://www.apache.org/legal/release-policy.html goes into this in more
> >> detail. A release must minimally include source packages, and can also
> >> include binary artifacts.
> >>
> >> Best,
> >> Andrew
> >>
> >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
> >> shv.hadoop@gmail.com> wrote:
> >>
> >>> To avoid any confusion in this regard. I built RC0 manually in
> compliance
> >>> with Apache release policy
> >>> http://www.apache.org/legal/release-policy.html
> >>> I edited the HowToReleasePreDSBCR page to make sure people don't use
> >>> Jenkins option for building.
> >>>
> >>> A side note. This particular build is broken anyways, so no worries
> there.
> >>> I think though it would be useful to have it working for testing and
> as a
> >>> packaging standard.
> >>>
> >>> Thanks,
> >>> --Konstantin
> >>>
> >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
> >>> aw@effectivemachines.com
> >>> > wrote:
> >>>
> >>> >
> >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
> >>> shv.hadoop@gmail.com>
> >>> > wrote:
> >>> > >
> >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
> >>> >
> >>> >         FYI:
> >>> >
> >>> >                 If you are using ASF Jenkins to create an ASF release
> >>> > artifact, it's pretty much an automatic vote failure as any such
> >>> release is
> >>> > in violation of ASF policy.
> >>> >
> >>> >
> >>>
> >>
> >>
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Zhe Zhang <zh...@apache.org>.
Quick question for Chris: was your +1 for the RC, or to support
Konstantin's statement regarding packaging?

Thanks,

On Mon, Jul 31, 2017 at 3:56 PM Chris Douglas <cd...@apache.org> wrote:

> On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
> <sh...@gmail.com> wrote:
> > For the packaging, here is the exact phrasing from the sited
> release-policy
> > document relevant to binaries:
> > "As a convenience to users that might not have the appropriate tools to
> > build a compiled version of the source, binary/bytecode packages MAY be
> > distributed alongside official Apache releases. In all such cases, the
> > binary/bytecode package MUST have the same version number as the source
> > release and MUST only add binary/bytecode files that are the result of
> > compiling that version of the source code release and its dependencies."
> > I don't think my binary package violates any of these.
>
> +1 The PMC VOTE applies to source code, only. If someone wants to
> rebuild the binary tarball with native libs and replace this one,
> that's fine.
>
> My reading of the above is that source code must be distributed with
> binaries, not that we omit the source code from binary releases... -C
>
> > But I'll upload an additional tar.gz with native bits and no src, as you
> > guys requested.
> > Will keep it as RC0 as there is no source code change and it comes from
> the
> > same build.
> > Hope this is satisfactory.
> >
> > Thanks,
> > --Konstantin
> >
> > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <an...@cloudera.com>
> > wrote:
> >
> >> I agree with Brahma on the two issues flagged (having src in the binary
> >> tarball, missing native libs). These are regressions from prior
> releases.
> >>
> >> As an aside, "we release binaries as a convenience" doesn't relax the
> >> quality bar. The binaries are linked on our website and distributed
> through
> >> official Apache channels. They have to adhere to Apache release
> >> requirements. And, most users consume our work via Maven dependencies,
> >> which are binary artifacts.
> >>
> >> http://www.apache.org/legal/release-policy.html goes into this in more
> >> detail. A release must minimally include source packages, and can also
> >> include binary artifacts.
> >>
> >> Best,
> >> Andrew
> >>
> >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
> >> shv.hadoop@gmail.com> wrote:
> >>
> >>> To avoid any confusion in this regard. I built RC0 manually in
> compliance
> >>> with Apache release policy
> >>> http://www.apache.org/legal/release-policy.html
> >>> I edited the HowToReleasePreDSBCR page to make sure people don't use
> >>> Jenkins option for building.
> >>>
> >>> A side note. This particular build is broken anyways, so no worries
> there.
> >>> I think though it would be useful to have it working for testing and
> as a
> >>> packaging standard.
> >>>
> >>> Thanks,
> >>> --Konstantin
> >>>
> >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
> >>> aw@effectivemachines.com
> >>> > wrote:
> >>>
> >>> >
> >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
> >>> shv.hadoop@gmail.com>
> >>> > wrote:
> >>> > >
> >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
> >>> >
> >>> >         FYI:
> >>> >
> >>> >                 If you are using ASF Jenkins to create an ASF release
> >>> > artifact, it's pretty much an automatic vote failure as any such
> >>> release is
> >>> > in violation of ASF policy.
> >>> >
> >>> >
> >>>
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
> --
Zhe Zhang
Apache Hadoop Committer
http://zhe-thoughts.github.io/about/ | @oldcap

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Konstantin Shvachko <sh...@gmail.com>.
Uploaded new binaries hadoop-2.7.4-RC0.tar.gz, which adds lib/native/.
Same place: http://home.apache.org/~shv/hadoop-2.7.4-RC0/

Thanks,
--Konstantin

On Mon, Jul 31, 2017 at 3:56 PM, Chris Douglas <cd...@apache.org> wrote:

> On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
> <sh...@gmail.com> wrote:
> > For the packaging, here is the exact phrasing from the sited
> release-policy
> > document relevant to binaries:
> > "As a convenience to users that might not have the appropriate tools to
> > build a compiled version of the source, binary/bytecode packages MAY be
> > distributed alongside official Apache releases. In all such cases, the
> > binary/bytecode package MUST have the same version number as the source
> > release and MUST only add binary/bytecode files that are the result of
> > compiling that version of the source code release and its dependencies."
> > I don't think my binary package violates any of these.
>
> +1 The PMC VOTE applies to source code, only. If someone wants to
> rebuild the binary tarball with native libs and replace this one,
> that's fine.
>
> My reading of the above is that source code must be distributed with
> binaries, not that we omit the source code from binary releases... -C
>
> > But I'll upload an additional tar.gz with native bits and no src, as you
> > guys requested.
> > Will keep it as RC0 as there is no source code change and it comes from
> the
> > same build.
> > Hope this is satisfactory.
> >
> > Thanks,
> > --Konstantin
> >
> > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <an...@cloudera.com>
> > wrote:
> >
> >> I agree with Brahma on the two issues flagged (having src in the binary
> >> tarball, missing native libs). These are regressions from prior
> releases.
> >>
> >> As an aside, "we release binaries as a convenience" doesn't relax the
> >> quality bar. The binaries are linked on our website and distributed
> through
> >> official Apache channels. They have to adhere to Apache release
> >> requirements. And, most users consume our work via Maven dependencies,
> >> which are binary artifacts.
> >>
> >> http://www.apache.org/legal/release-policy.html goes into this in more
> >> detail. A release must minimally include source packages, and can also
> >> include binary artifacts.
> >>
> >> Best,
> >> Andrew
> >>
> >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
> >> shv.hadoop@gmail.com> wrote:
> >>
> >>> To avoid any confusion in this regard. I built RC0 manually in
> compliance
> >>> with Apache release policy
> >>> http://www.apache.org/legal/release-policy.html
> >>> I edited the HowToReleasePreDSBCR page to make sure people don't use
> >>> Jenkins option for building.
> >>>
> >>> A side note. This particular build is broken anyways, so no worries
> there.
> >>> I think though it would be useful to have it working for testing and
> as a
> >>> packaging standard.
> >>>
> >>> Thanks,
> >>> --Konstantin
> >>>
> >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
> >>> aw@effectivemachines.com
> >>> > wrote:
> >>>
> >>> >
> >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
> >>> shv.hadoop@gmail.com>
> >>> > wrote:
> >>> > >
> >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
> >>> >
> >>> >         FYI:
> >>> >
> >>> >                 If you are using ASF Jenkins to create an ASF release
> >>> > artifact, it's pretty much an automatic vote failure as any such
> >>> release is
> >>> > in violation of ASF policy.
> >>> >
> >>> >
> >>>
> >>
> >>
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Zhe Zhang <zh...@apache.org>.
Quick question for Chris: was your +1 for the RC, or to support
Konstantin's statement regarding packaging?

Thanks,

On Mon, Jul 31, 2017 at 3:56 PM Chris Douglas <cd...@apache.org> wrote:

> On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
> <sh...@gmail.com> wrote:
> > For the packaging, here is the exact phrasing from the sited
> release-policy
> > document relevant to binaries:
> > "As a convenience to users that might not have the appropriate tools to
> > build a compiled version of the source, binary/bytecode packages MAY be
> > distributed alongside official Apache releases. In all such cases, the
> > binary/bytecode package MUST have the same version number as the source
> > release and MUST only add binary/bytecode files that are the result of
> > compiling that version of the source code release and its dependencies."
> > I don't think my binary package violates any of these.
>
> +1 The PMC VOTE applies to source code, only. If someone wants to
> rebuild the binary tarball with native libs and replace this one,
> that's fine.
>
> My reading of the above is that source code must be distributed with
> binaries, not that we omit the source code from binary releases... -C
>
> > But I'll upload an additional tar.gz with native bits and no src, as you
> > guys requested.
> > Will keep it as RC0 as there is no source code change and it comes from
> the
> > same build.
> > Hope this is satisfactory.
> >
> > Thanks,
> > --Konstantin
> >
> > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <an...@cloudera.com>
> > wrote:
> >
> >> I agree with Brahma on the two issues flagged (having src in the binary
> >> tarball, missing native libs). These are regressions from prior
> releases.
> >>
> >> As an aside, "we release binaries as a convenience" doesn't relax the
> >> quality bar. The binaries are linked on our website and distributed
> through
> >> official Apache channels. They have to adhere to Apache release
> >> requirements. And, most users consume our work via Maven dependencies,
> >> which are binary artifacts.
> >>
> >> http://www.apache.org/legal/release-policy.html goes into this in more
> >> detail. A release must minimally include source packages, and can also
> >> include binary artifacts.
> >>
> >> Best,
> >> Andrew
> >>
> >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
> >> shv.hadoop@gmail.com> wrote:
> >>
> >>> To avoid any confusion in this regard. I built RC0 manually in
> compliance
> >>> with Apache release policy
> >>> http://www.apache.org/legal/release-policy.html
> >>> I edited the HowToReleasePreDSBCR page to make sure people don't use
> >>> Jenkins option for building.
> >>>
> >>> A side note. This particular build is broken anyways, so no worries
> there.
> >>> I think though it would be useful to have it working for testing and
> as a
> >>> packaging standard.
> >>>
> >>> Thanks,
> >>> --Konstantin
> >>>
> >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
> >>> aw@effectivemachines.com
> >>> > wrote:
> >>>
> >>> >
> >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
> >>> shv.hadoop@gmail.com>
> >>> > wrote:
> >>> > >
> >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
> >>> >
> >>> >         FYI:
> >>> >
> >>> >                 If you are using ASF Jenkins to create an ASF release
> >>> > artifact, it's pretty much an automatic vote failure as any such
> >>> release is
> >>> > in violation of ASF policy.
> >>> >
> >>> >
> >>>
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
> --
Zhe Zhang
Apache Hadoop Committer
http://zhe-thoughts.github.io/about/ | @oldcap

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Zhe Zhang <zh...@apache.org>.
Quick question for Chris: was your +1 for the RC, or to support
Konstantin's statement regarding packaging?

Thanks,

On Mon, Jul 31, 2017 at 3:56 PM Chris Douglas <cd...@apache.org> wrote:

> On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
> <sh...@gmail.com> wrote:
> > For the packaging, here is the exact phrasing from the sited
> release-policy
> > document relevant to binaries:
> > "As a convenience to users that might not have the appropriate tools to
> > build a compiled version of the source, binary/bytecode packages MAY be
> > distributed alongside official Apache releases. In all such cases, the
> > binary/bytecode package MUST have the same version number as the source
> > release and MUST only add binary/bytecode files that are the result of
> > compiling that version of the source code release and its dependencies."
> > I don't think my binary package violates any of these.
>
> +1 The PMC VOTE applies to source code, only. If someone wants to
> rebuild the binary tarball with native libs and replace this one,
> that's fine.
>
> My reading of the above is that source code must be distributed with
> binaries, not that we omit the source code from binary releases... -C
>
> > But I'll upload an additional tar.gz with native bits and no src, as you
> > guys requested.
> > Will keep it as RC0 as there is no source code change and it comes from
> the
> > same build.
> > Hope this is satisfactory.
> >
> > Thanks,
> > --Konstantin
> >
> > On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <an...@cloudera.com>
> > wrote:
> >
> >> I agree with Brahma on the two issues flagged (having src in the binary
> >> tarball, missing native libs). These are regressions from prior
> releases.
> >>
> >> As an aside, "we release binaries as a convenience" doesn't relax the
> >> quality bar. The binaries are linked on our website and distributed
> through
> >> official Apache channels. They have to adhere to Apache release
> >> requirements. And, most users consume our work via Maven dependencies,
> >> which are binary artifacts.
> >>
> >> http://www.apache.org/legal/release-policy.html goes into this in more
> >> detail. A release must minimally include source packages, and can also
> >> include binary artifacts.
> >>
> >> Best,
> >> Andrew
> >>
> >> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
> >> shv.hadoop@gmail.com> wrote:
> >>
> >>> To avoid any confusion in this regard. I built RC0 manually in
> compliance
> >>> with Apache release policy
> >>> http://www.apache.org/legal/release-policy.html
> >>> I edited the HowToReleasePreDSBCR page to make sure people don't use
> >>> Jenkins option for building.
> >>>
> >>> A side note. This particular build is broken anyways, so no worries
> there.
> >>> I think though it would be useful to have it working for testing and
> as a
> >>> packaging standard.
> >>>
> >>> Thanks,
> >>> --Konstantin
> >>>
> >>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
> >>> aw@effectivemachines.com
> >>> > wrote:
> >>>
> >>> >
> >>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
> >>> shv.hadoop@gmail.com>
> >>> > wrote:
> >>> > >
> >>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
> >>> >
> >>> >         FYI:
> >>> >
> >>> >                 If you are using ASF Jenkins to create an ASF release
> >>> > artifact, it's pretty much an automatic vote failure as any such
> >>> release is
> >>> > in violation of ASF policy.
> >>> >
> >>> >
> >>>
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
> --
Zhe Zhang
Apache Hadoop Committer
http://zhe-thoughts.github.io/about/ | @oldcap

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Chris Douglas <cd...@apache.org>.
On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
<sh...@gmail.com> wrote:
> For the packaging, here is the exact phrasing from the sited release-policy
> document relevant to binaries:
> "As a convenience to users that might not have the appropriate tools to
> build a compiled version of the source, binary/bytecode packages MAY be
> distributed alongside official Apache releases. In all such cases, the
> binary/bytecode package MUST have the same version number as the source
> release and MUST only add binary/bytecode files that are the result of
> compiling that version of the source code release and its dependencies."
> I don't think my binary package violates any of these.

+1 The PMC VOTE applies to source code, only. If someone wants to
rebuild the binary tarball with native libs and replace this one,
that's fine.

My reading of the above is that source code must be distributed with
binaries, not that we omit the source code from binary releases... -C

> But I'll upload an additional tar.gz with native bits and no src, as you
> guys requested.
> Will keep it as RC0 as there is no source code change and it comes from the
> same build.
> Hope this is satisfactory.
>
> Thanks,
> --Konstantin
>
> On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <an...@cloudera.com>
> wrote:
>
>> I agree with Brahma on the two issues flagged (having src in the binary
>> tarball, missing native libs). These are regressions from prior releases.
>>
>> As an aside, "we release binaries as a convenience" doesn't relax the
>> quality bar. The binaries are linked on our website and distributed through
>> official Apache channels. They have to adhere to Apache release
>> requirements. And, most users consume our work via Maven dependencies,
>> which are binary artifacts.
>>
>> http://www.apache.org/legal/release-policy.html goes into this in more
>> detail. A release must minimally include source packages, and can also
>> include binary artifacts.
>>
>> Best,
>> Andrew
>>
>> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
>> shv.hadoop@gmail.com> wrote:
>>
>>> To avoid any confusion in this regard. I built RC0 manually in compliance
>>> with Apache release policy
>>> http://www.apache.org/legal/release-policy.html
>>> I edited the HowToReleasePreDSBCR page to make sure people don't use
>>> Jenkins option for building.
>>>
>>> A side note. This particular build is broken anyways, so no worries there.
>>> I think though it would be useful to have it working for testing and as a
>>> packaging standard.
>>>
>>> Thanks,
>>> --Konstantin
>>>
>>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
>>> aw@effectivemachines.com
>>> > wrote:
>>>
>>> >
>>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
>>> shv.hadoop@gmail.com>
>>> > wrote:
>>> > >
>>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
>>> >
>>> >         FYI:
>>> >
>>> >                 If you are using ASF Jenkins to create an ASF release
>>> > artifact, it's pretty much an automatic vote failure as any such
>>> release is
>>> > in violation of 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.7.4 (RC0)

Posted by Chris Douglas <cd...@apache.org>.
On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
<sh...@gmail.com> wrote:
> For the packaging, here is the exact phrasing from the sited release-policy
> document relevant to binaries:
> "As a convenience to users that might not have the appropriate tools to
> build a compiled version of the source, binary/bytecode packages MAY be
> distributed alongside official Apache releases. In all such cases, the
> binary/bytecode package MUST have the same version number as the source
> release and MUST only add binary/bytecode files that are the result of
> compiling that version of the source code release and its dependencies."
> I don't think my binary package violates any of these.

+1 The PMC VOTE applies to source code, only. If someone wants to
rebuild the binary tarball with native libs and replace this one,
that's fine.

My reading of the above is that source code must be distributed with
binaries, not that we omit the source code from binary releases... -C

> But I'll upload an additional tar.gz with native bits and no src, as you
> guys requested.
> Will keep it as RC0 as there is no source code change and it comes from the
> same build.
> Hope this is satisfactory.
>
> Thanks,
> --Konstantin
>
> On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <an...@cloudera.com>
> wrote:
>
>> I agree with Brahma on the two issues flagged (having src in the binary
>> tarball, missing native libs). These are regressions from prior releases.
>>
>> As an aside, "we release binaries as a convenience" doesn't relax the
>> quality bar. The binaries are linked on our website and distributed through
>> official Apache channels. They have to adhere to Apache release
>> requirements. And, most users consume our work via Maven dependencies,
>> which are binary artifacts.
>>
>> http://www.apache.org/legal/release-policy.html goes into this in more
>> detail. A release must minimally include source packages, and can also
>> include binary artifacts.
>>
>> Best,
>> Andrew
>>
>> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
>> shv.hadoop@gmail.com> wrote:
>>
>>> To avoid any confusion in this regard. I built RC0 manually in compliance
>>> with Apache release policy
>>> http://www.apache.org/legal/release-policy.html
>>> I edited the HowToReleasePreDSBCR page to make sure people don't use
>>> Jenkins option for building.
>>>
>>> A side note. This particular build is broken anyways, so no worries there.
>>> I think though it would be useful to have it working for testing and as a
>>> packaging standard.
>>>
>>> Thanks,
>>> --Konstantin
>>>
>>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
>>> aw@effectivemachines.com
>>> > wrote:
>>>
>>> >
>>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
>>> shv.hadoop@gmail.com>
>>> > wrote:
>>> > >
>>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
>>> >
>>> >         FYI:
>>> >
>>> >                 If you are using ASF Jenkins to create an ASF release
>>> > artifact, it's pretty much an automatic vote failure as any such
>>> release is
>>> > in violation of 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.7.4 (RC0)

Posted by Chris Douglas <cd...@apache.org>.
On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
<sh...@gmail.com> wrote:
> For the packaging, here is the exact phrasing from the sited release-policy
> document relevant to binaries:
> "As a convenience to users that might not have the appropriate tools to
> build a compiled version of the source, binary/bytecode packages MAY be
> distributed alongside official Apache releases. In all such cases, the
> binary/bytecode package MUST have the same version number as the source
> release and MUST only add binary/bytecode files that are the result of
> compiling that version of the source code release and its dependencies."
> I don't think my binary package violates any of these.

+1 The PMC VOTE applies to source code, only. If someone wants to
rebuild the binary tarball with native libs and replace this one,
that's fine.

My reading of the above is that source code must be distributed with
binaries, not that we omit the source code from binary releases... -C

> But I'll upload an additional tar.gz with native bits and no src, as you
> guys requested.
> Will keep it as RC0 as there is no source code change and it comes from the
> same build.
> Hope this is satisfactory.
>
> Thanks,
> --Konstantin
>
> On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <an...@cloudera.com>
> wrote:
>
>> I agree with Brahma on the two issues flagged (having src in the binary
>> tarball, missing native libs). These are regressions from prior releases.
>>
>> As an aside, "we release binaries as a convenience" doesn't relax the
>> quality bar. The binaries are linked on our website and distributed through
>> official Apache channels. They have to adhere to Apache release
>> requirements. And, most users consume our work via Maven dependencies,
>> which are binary artifacts.
>>
>> http://www.apache.org/legal/release-policy.html goes into this in more
>> detail. A release must minimally include source packages, and can also
>> include binary artifacts.
>>
>> Best,
>> Andrew
>>
>> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
>> shv.hadoop@gmail.com> wrote:
>>
>>> To avoid any confusion in this regard. I built RC0 manually in compliance
>>> with Apache release policy
>>> http://www.apache.org/legal/release-policy.html
>>> I edited the HowToReleasePreDSBCR page to make sure people don't use
>>> Jenkins option for building.
>>>
>>> A side note. This particular build is broken anyways, so no worries there.
>>> I think though it would be useful to have it working for testing and as a
>>> packaging standard.
>>>
>>> Thanks,
>>> --Konstantin
>>>
>>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
>>> aw@effectivemachines.com
>>> > wrote:
>>>
>>> >
>>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
>>> shv.hadoop@gmail.com>
>>> > wrote:
>>> > >
>>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
>>> >
>>> >         FYI:
>>> >
>>> >                 If you are using ASF Jenkins to create an ASF release
>>> > artifact, it's pretty much an automatic vote failure as any such
>>> release is
>>> > in violation of 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.7.4 (RC0)

Posted by Chris Douglas <cd...@apache.org>.
On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko
<sh...@gmail.com> wrote:
> For the packaging, here is the exact phrasing from the sited release-policy
> document relevant to binaries:
> "As a convenience to users that might not have the appropriate tools to
> build a compiled version of the source, binary/bytecode packages MAY be
> distributed alongside official Apache releases. In all such cases, the
> binary/bytecode package MUST have the same version number as the source
> release and MUST only add binary/bytecode files that are the result of
> compiling that version of the source code release and its dependencies."
> I don't think my binary package violates any of these.

+1 The PMC VOTE applies to source code, only. If someone wants to
rebuild the binary tarball with native libs and replace this one,
that's fine.

My reading of the above is that source code must be distributed with
binaries, not that we omit the source code from binary releases... -C

> But I'll upload an additional tar.gz with native bits and no src, as you
> guys requested.
> Will keep it as RC0 as there is no source code change and it comes from the
> same build.
> Hope this is satisfactory.
>
> Thanks,
> --Konstantin
>
> On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <an...@cloudera.com>
> wrote:
>
>> I agree with Brahma on the two issues flagged (having src in the binary
>> tarball, missing native libs). These are regressions from prior releases.
>>
>> As an aside, "we release binaries as a convenience" doesn't relax the
>> quality bar. The binaries are linked on our website and distributed through
>> official Apache channels. They have to adhere to Apache release
>> requirements. And, most users consume our work via Maven dependencies,
>> which are binary artifacts.
>>
>> http://www.apache.org/legal/release-policy.html goes into this in more
>> detail. A release must minimally include source packages, and can also
>> include binary artifacts.
>>
>> Best,
>> Andrew
>>
>> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
>> shv.hadoop@gmail.com> wrote:
>>
>>> To avoid any confusion in this regard. I built RC0 manually in compliance
>>> with Apache release policy
>>> http://www.apache.org/legal/release-policy.html
>>> I edited the HowToReleasePreDSBCR page to make sure people don't use
>>> Jenkins option for building.
>>>
>>> A side note. This particular build is broken anyways, so no worries there.
>>> I think though it would be useful to have it working for testing and as a
>>> packaging standard.
>>>
>>> Thanks,
>>> --Konstantin
>>>
>>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
>>> aw@effectivemachines.com
>>> > wrote:
>>>
>>> >
>>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
>>> shv.hadoop@gmail.com>
>>> > wrote:
>>> > >
>>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
>>> >
>>> >         FYI:
>>> >
>>> >                 If you are using ASF Jenkins to create an ASF release
>>> > artifact, it's pretty much an automatic vote failure as any such
>>> release is
>>> > in violation of 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.7.4 (RC0)

Posted by Konstantin Shvachko <sh...@gmail.com>.
Maven dependencies should be fine.

For the packaging, here is the exact phrasing from the sited release-policy
document relevant to binaries:
"As a convenience to users that might not have the appropriate tools to
build a compiled version of the source, binary/bytecode packages MAY be
distributed alongside official Apache releases. In all such cases, the
binary/bytecode package MUST have the same version number as the source
release and MUST only add binary/bytecode files that are the result of
compiling that version of the source code release and its dependencies."
I don't think my binary package violates any of these.

But I'll upload an additional tar.gz with native bits and no src, as you
guys requested.
Will keep it as RC0 as there is no source code change and it comes from the
same build.
Hope this is satisfactory.

Thanks,
--Konstantin

On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <an...@cloudera.com>
wrote:

> I agree with Brahma on the two issues flagged (having src in the binary
> tarball, missing native libs). These are regressions from prior releases.
>
> As an aside, "we release binaries as a convenience" doesn't relax the
> quality bar. The binaries are linked on our website and distributed through
> official Apache channels. They have to adhere to Apache release
> requirements. And, most users consume our work via Maven dependencies,
> which are binary artifacts.
>
> http://www.apache.org/legal/release-policy.html goes into this in more
> detail. A release must minimally include source packages, and can also
> include binary artifacts.
>
> Best,
> Andrew
>
> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
> shv.hadoop@gmail.com> wrote:
>
>> To avoid any confusion in this regard. I built RC0 manually in compliance
>> with Apache release policy
>> http://www.apache.org/legal/release-policy.html
>> I edited the HowToReleasePreDSBCR page to make sure people don't use
>> Jenkins option for building.
>>
>> A side note. This particular build is broken anyways, so no worries there.
>> I think though it would be useful to have it working for testing and as a
>> packaging standard.
>>
>> Thanks,
>> --Konstantin
>>
>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
>> aw@effectivemachines.com
>> > wrote:
>>
>> >
>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
>> shv.hadoop@gmail.com>
>> > wrote:
>> > >
>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
>> >
>> >         FYI:
>> >
>> >                 If you are using ASF Jenkins to create an ASF release
>> > artifact, it's pretty much an automatic vote failure as any such
>> release is
>> > in violation of ASF policy.
>> >
>> >
>>
>
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Konstantin Shvachko <sh...@gmail.com>.
Maven dependencies should be fine.

For the packaging, here is the exact phrasing from the sited release-policy
document relevant to binaries:
"As a convenience to users that might not have the appropriate tools to
build a compiled version of the source, binary/bytecode packages MAY be
distributed alongside official Apache releases. In all such cases, the
binary/bytecode package MUST have the same version number as the source
release and MUST only add binary/bytecode files that are the result of
compiling that version of the source code release and its dependencies."
I don't think my binary package violates any of these.

But I'll upload an additional tar.gz with native bits and no src, as you
guys requested.
Will keep it as RC0 as there is no source code change and it comes from the
same build.
Hope this is satisfactory.

Thanks,
--Konstantin

On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <an...@cloudera.com>
wrote:

> I agree with Brahma on the two issues flagged (having src in the binary
> tarball, missing native libs). These are regressions from prior releases.
>
> As an aside, "we release binaries as a convenience" doesn't relax the
> quality bar. The binaries are linked on our website and distributed through
> official Apache channels. They have to adhere to Apache release
> requirements. And, most users consume our work via Maven dependencies,
> which are binary artifacts.
>
> http://www.apache.org/legal/release-policy.html goes into this in more
> detail. A release must minimally include source packages, and can also
> include binary artifacts.
>
> Best,
> Andrew
>
> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
> shv.hadoop@gmail.com> wrote:
>
>> To avoid any confusion in this regard. I built RC0 manually in compliance
>> with Apache release policy
>> http://www.apache.org/legal/release-policy.html
>> I edited the HowToReleasePreDSBCR page to make sure people don't use
>> Jenkins option for building.
>>
>> A side note. This particular build is broken anyways, so no worries there.
>> I think though it would be useful to have it working for testing and as a
>> packaging standard.
>>
>> Thanks,
>> --Konstantin
>>
>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
>> aw@effectivemachines.com
>> > wrote:
>>
>> >
>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
>> shv.hadoop@gmail.com>
>> > wrote:
>> > >
>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
>> >
>> >         FYI:
>> >
>> >                 If you are using ASF Jenkins to create an ASF release
>> > artifact, it's pretty much an automatic vote failure as any such
>> release is
>> > in violation of ASF policy.
>> >
>> >
>>
>
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Konstantin Shvachko <sh...@gmail.com>.
Maven dependencies should be fine.

For the packaging, here is the exact phrasing from the sited release-policy
document relevant to binaries:
"As a convenience to users that might not have the appropriate tools to
build a compiled version of the source, binary/bytecode packages MAY be
distributed alongside official Apache releases. In all such cases, the
binary/bytecode package MUST have the same version number as the source
release and MUST only add binary/bytecode files that are the result of
compiling that version of the source code release and its dependencies."
I don't think my binary package violates any of these.

But I'll upload an additional tar.gz with native bits and no src, as you
guys requested.
Will keep it as RC0 as there is no source code change and it comes from the
same build.
Hope this is satisfactory.

Thanks,
--Konstantin

On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <an...@cloudera.com>
wrote:

> I agree with Brahma on the two issues flagged (having src in the binary
> tarball, missing native libs). These are regressions from prior releases.
>
> As an aside, "we release binaries as a convenience" doesn't relax the
> quality bar. The binaries are linked on our website and distributed through
> official Apache channels. They have to adhere to Apache release
> requirements. And, most users consume our work via Maven dependencies,
> which are binary artifacts.
>
> http://www.apache.org/legal/release-policy.html goes into this in more
> detail. A release must minimally include source packages, and can also
> include binary artifacts.
>
> Best,
> Andrew
>
> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
> shv.hadoop@gmail.com> wrote:
>
>> To avoid any confusion in this regard. I built RC0 manually in compliance
>> with Apache release policy
>> http://www.apache.org/legal/release-policy.html
>> I edited the HowToReleasePreDSBCR page to make sure people don't use
>> Jenkins option for building.
>>
>> A side note. This particular build is broken anyways, so no worries there.
>> I think though it would be useful to have it working for testing and as a
>> packaging standard.
>>
>> Thanks,
>> --Konstantin
>>
>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
>> aw@effectivemachines.com
>> > wrote:
>>
>> >
>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
>> shv.hadoop@gmail.com>
>> > wrote:
>> > >
>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
>> >
>> >         FYI:
>> >
>> >                 If you are using ASF Jenkins to create an ASF release
>> > artifact, it's pretty much an automatic vote failure as any such
>> release is
>> > in violation of ASF policy.
>> >
>> >
>>
>
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Konstantin Shvachko <sh...@gmail.com>.
Maven dependencies should be fine.

For the packaging, here is the exact phrasing from the sited release-policy
document relevant to binaries:
"As a convenience to users that might not have the appropriate tools to
build a compiled version of the source, binary/bytecode packages MAY be
distributed alongside official Apache releases. In all such cases, the
binary/bytecode package MUST have the same version number as the source
release and MUST only add binary/bytecode files that are the result of
compiling that version of the source code release and its dependencies."
I don't think my binary package violates any of these.

But I'll upload an additional tar.gz with native bits and no src, as you
guys requested.
Will keep it as RC0 as there is no source code change and it comes from the
same build.
Hope this is satisfactory.

Thanks,
--Konstantin

On Mon, Jul 31, 2017 at 1:53 PM, Andrew Wang <an...@cloudera.com>
wrote:

> I agree with Brahma on the two issues flagged (having src in the binary
> tarball, missing native libs). These are regressions from prior releases.
>
> As an aside, "we release binaries as a convenience" doesn't relax the
> quality bar. The binaries are linked on our website and distributed through
> official Apache channels. They have to adhere to Apache release
> requirements. And, most users consume our work via Maven dependencies,
> which are binary artifacts.
>
> http://www.apache.org/legal/release-policy.html goes into this in more
> detail. A release must minimally include source packages, and can also
> include binary artifacts.
>
> Best,
> Andrew
>
> On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <
> shv.hadoop@gmail.com> wrote:
>
>> To avoid any confusion in this regard. I built RC0 manually in compliance
>> with Apache release policy
>> http://www.apache.org/legal/release-policy.html
>> I edited the HowToReleasePreDSBCR page to make sure people don't use
>> Jenkins option for building.
>>
>> A side note. This particular build is broken anyways, so no worries there.
>> I think though it would be useful to have it working for testing and as a
>> packaging standard.
>>
>> Thanks,
>> --Konstantin
>>
>> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
>> aw@effectivemachines.com
>> > wrote:
>>
>> >
>> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
>> shv.hadoop@gmail.com>
>> > wrote:
>> > >
>> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
>> >
>> >         FYI:
>> >
>> >                 If you are using ASF Jenkins to create an ASF release
>> > artifact, it's pretty much an automatic vote failure as any such
>> release is
>> > in violation of ASF policy.
>> >
>> >
>>
>
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Andrew Wang <an...@cloudera.com>.
I agree with Brahma on the two issues flagged (having src in the binary
tarball, missing native libs). These are regressions from prior releases.

As an aside, "we release binaries as a convenience" doesn't relax the
quality bar. The binaries are linked on our website and distributed through
official Apache channels. They have to adhere to Apache release
requirements. And, most users consume our work via Maven dependencies,
which are binary artifacts.

http://www.apache.org/legal/release-policy.html goes into this in more
detail. A release must minimally include source packages, and can also
include binary artifacts.

Best,
Andrew

On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <sh...@gmail.com>
wrote:

> To avoid any confusion in this regard. I built RC0 manually in compliance
> with Apache release policy
> http://www.apache.org/legal/release-policy.html
> I edited the HowToReleasePreDSBCR page to make sure people don't use
> Jenkins option for building.
>
> A side note. This particular build is broken anyways, so no worries there.
> I think though it would be useful to have it working for testing and as a
> packaging standard.
>
> Thanks,
> --Konstantin
>
> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
> aw@effectivemachines.com
> > wrote:
>
> >
> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
> shv.hadoop@gmail.com>
> > wrote:
> > >
> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
> >
> >         FYI:
> >
> >                 If you are using ASF Jenkins to create an ASF release
> > artifact, it's pretty much an automatic vote failure as any such release
> is
> > in violation of ASF policy.
> >
> >
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Andrew Wang <an...@cloudera.com>.
I agree with Brahma on the two issues flagged (having src in the binary
tarball, missing native libs). These are regressions from prior releases.

As an aside, "we release binaries as a convenience" doesn't relax the
quality bar. The binaries are linked on our website and distributed through
official Apache channels. They have to adhere to Apache release
requirements. And, most users consume our work via Maven dependencies,
which are binary artifacts.

http://www.apache.org/legal/release-policy.html goes into this in more
detail. A release must minimally include source packages, and can also
include binary artifacts.

Best,
Andrew

On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <sh...@gmail.com>
wrote:

> To avoid any confusion in this regard. I built RC0 manually in compliance
> with Apache release policy
> http://www.apache.org/legal/release-policy.html
> I edited the HowToReleasePreDSBCR page to make sure people don't use
> Jenkins option for building.
>
> A side note. This particular build is broken anyways, so no worries there.
> I think though it would be useful to have it working for testing and as a
> packaging standard.
>
> Thanks,
> --Konstantin
>
> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
> aw@effectivemachines.com
> > wrote:
>
> >
> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
> shv.hadoop@gmail.com>
> > wrote:
> > >
> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
> >
> >         FYI:
> >
> >                 If you are using ASF Jenkins to create an ASF release
> > artifact, it's pretty much an automatic vote failure as any such release
> is
> > in violation of ASF policy.
> >
> >
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Andrew Wang <an...@cloudera.com>.
I agree with Brahma on the two issues flagged (having src in the binary
tarball, missing native libs). These are regressions from prior releases.

As an aside, "we release binaries as a convenience" doesn't relax the
quality bar. The binaries are linked on our website and distributed through
official Apache channels. They have to adhere to Apache release
requirements. And, most users consume our work via Maven dependencies,
which are binary artifacts.

http://www.apache.org/legal/release-policy.html goes into this in more
detail. A release must minimally include source packages, and can also
include binary artifacts.

Best,
Andrew

On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <sh...@gmail.com>
wrote:

> To avoid any confusion in this regard. I built RC0 manually in compliance
> with Apache release policy
> http://www.apache.org/legal/release-policy.html
> I edited the HowToReleasePreDSBCR page to make sure people don't use
> Jenkins option for building.
>
> A side note. This particular build is broken anyways, so no worries there.
> I think though it would be useful to have it working for testing and as a
> packaging standard.
>
> Thanks,
> --Konstantin
>
> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
> aw@effectivemachines.com
> > wrote:
>
> >
> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
> shv.hadoop@gmail.com>
> > wrote:
> > >
> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
> >
> >         FYI:
> >
> >                 If you are using ASF Jenkins to create an ASF release
> > artifact, it's pretty much an automatic vote failure as any such release
> is
> > in violation of ASF policy.
> >
> >
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Andrew Wang <an...@cloudera.com>.
I agree with Brahma on the two issues flagged (having src in the binary
tarball, missing native libs). These are regressions from prior releases.

As an aside, "we release binaries as a convenience" doesn't relax the
quality bar. The binaries are linked on our website and distributed through
official Apache channels. They have to adhere to Apache release
requirements. And, most users consume our work via Maven dependencies,
which are binary artifacts.

http://www.apache.org/legal/release-policy.html goes into this in more
detail. A release must minimally include source packages, and can also
include binary artifacts.

Best,
Andrew

On Mon, Jul 31, 2017 at 12:30 PM, Konstantin Shvachko <sh...@gmail.com>
wrote:

> To avoid any confusion in this regard. I built RC0 manually in compliance
> with Apache release policy
> http://www.apache.org/legal/release-policy.html
> I edited the HowToReleasePreDSBCR page to make sure people don't use
> Jenkins option for building.
>
> A side note. This particular build is broken anyways, so no worries there.
> I think though it would be useful to have it working for testing and as a
> packaging standard.
>
> Thanks,
> --Konstantin
>
> On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <
> aw@effectivemachines.com
> > wrote:
>
> >
> > > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <
> shv.hadoop@gmail.com>
> > wrote:
> > >
> > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
> >
> >         FYI:
> >
> >                 If you are using ASF Jenkins to create an ASF release
> > artifact, it's pretty much an automatic vote failure as any such release
> is
> > in violation of ASF policy.
> >
> >
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Konstantin Shvachko <sh...@gmail.com>.
To avoid any confusion in this regard. I built RC0 manually in compliance
with Apache release policy
http://www.apache.org/legal/release-policy.html
I edited the HowToReleasePreDSBCR page to make sure people don't use
Jenkins option for building.

A side note. This particular build is broken anyways, so no worries there.
I think though it would be useful to have it working for testing and as a
packaging standard.

Thanks,
--Konstantin

On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <aw@effectivemachines.com
> wrote:

>
> > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <sh...@gmail.com>
> wrote:
> >
> > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
>
>         FYI:
>
>                 If you are using ASF Jenkins to create an ASF release
> artifact, it's pretty much an automatic vote failure as any such release is
> in violation of ASF policy.
>
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Konstantin Shvachko <sh...@gmail.com>.
To avoid any confusion in this regard. I built RC0 manually in compliance
with Apache release policy
http://www.apache.org/legal/release-policy.html
I edited the HowToReleasePreDSBCR page to make sure people don't use
Jenkins option for building.

A side note. This particular build is broken anyways, so no worries there.
I think though it would be useful to have it working for testing and as a
packaging standard.

Thanks,
--Konstantin

On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <aw@effectivemachines.com
> wrote:

>
> > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <sh...@gmail.com>
> wrote:
> >
> > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
>
>         FYI:
>
>                 If you are using ASF Jenkins to create an ASF release
> artifact, it's pretty much an automatic vote failure as any such release is
> in violation of ASF policy.
>
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Konstantin Shvachko <sh...@gmail.com>.
To avoid any confusion in this regard. I built RC0 manually in compliance
with Apache release policy
http://www.apache.org/legal/release-policy.html
I edited the HowToReleasePreDSBCR page to make sure people don't use
Jenkins option for building.

A side note. This particular build is broken anyways, so no worries there.
I think though it would be useful to have it working for testing and as a
packaging standard.

Thanks,
--Konstantin

On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <aw@effectivemachines.com
> wrote:

>
> > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <sh...@gmail.com>
> wrote:
> >
> > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
>
>         FYI:
>
>                 If you are using ASF Jenkins to create an ASF release
> artifact, it's pretty much an automatic vote failure as any such release is
> in violation of ASF policy.
>
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Konstantin Shvachko <sh...@gmail.com>.
To avoid any confusion in this regard. I built RC0 manually in compliance
with Apache release policy
http://www.apache.org/legal/release-policy.html
I edited the HowToReleasePreDSBCR page to make sure people don't use
Jenkins option for building.

A side note. This particular build is broken anyways, so no worries there.
I think though it would be useful to have it working for testing and as a
packaging standard.

Thanks,
--Konstantin

On Mon, Jul 31, 2017 at 11:40 AM, Allen Wittenauer <aw@effectivemachines.com
> wrote:

>
> > On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <sh...@gmail.com>
> wrote:
> >
> > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
>
>         FYI:
>
>                 If you are using ASF Jenkins to create an ASF release
> artifact, it's pretty much an automatic vote failure as any such release is
> in violation of ASF policy.
>
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Allen Wittenauer <aw...@effectivemachines.com>.
> On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <sh...@gmail.com> wrote:
> 
> https://wiki.apache.org/hadoop/HowToReleasePreDSBCR

	FYI:

		If you are using ASF Jenkins to create an ASF release artifact, it's pretty much an automatic vote failure as any such release is in violation of 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.7.4 (RC0)

Posted by Allen Wittenauer <aw...@effectivemachines.com>.
> On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <sh...@gmail.com> wrote:
> 
> https://wiki.apache.org/hadoop/HowToReleasePreDSBCR

	FYI:

		If you are using ASF Jenkins to create an ASF release artifact, it's pretty much an automatic vote failure as any such release is in violation of 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.7.4 (RC0)

Posted by Allen Wittenauer <aw...@effectivemachines.com>.
> On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <sh...@gmail.com> wrote:
> 
> https://wiki.apache.org/hadoop/HowToReleasePreDSBCR

	FYI:

		If you are using ASF Jenkins to create an ASF release artifact, it's pretty much an automatic vote failure as any such release is in violation of 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.7.4 (RC0)

Posted by Allen Wittenauer <aw...@effectivemachines.com>.
> On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko <sh...@gmail.com> wrote:
> 
> https://wiki.apache.org/hadoop/HowToReleasePreDSBCR

	FYI:

		If you are using ASF Jenkins to create an ASF release artifact, it's pretty much an automatic vote failure as any such release is in violation of 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.7.4 (RC0)

Posted by Konstantin Shvachko <sh...@gmail.com>.
Hi Brahma Reddy Battula,

Formally Apache releases sources. We provide binaries as a reference for
convenience.
The release instructions for Hadoop 2.7 line at
https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
don't give much guidance on how to actually build and package the binary
tarball.
I intentionally included sources as the main content of the release.
And did not include native binaries, which very much depend on the
environment.
LMK if binary packaging is a blocker for you.

Thanks,
--Konstantin

On Sun, Jul 30, 2017 at 7:45 PM, Brahma Reddy Battula <
brahmareddy.battula@huawei.com> wrote:

> Thanks konstantin.
>
> Native files (lib/native) is missed
> And src folder exists in tar ball.
>
> Please check the same.
>
> Host1:/home/Brahma/Release/hadoop-2.7.4 # ll
> total 144
> -rw-r--r--  1 20415 messagebus 86424 Jul 30 02:54 LICENSE.txt
> -rw-r--r--  1 20415 messagebus 14978 Jul 30 02:54 NOTICE.txt
> -rw-r--r--  1 20415 messagebus  1366 Jul 30 02:54 README.txt
> drwxr-xr-x  2 20415 messagebus  4096 Jul 30 02:54 bin
> drwxr-xr-x  3 20415 messagebus  4096 Jul 30 02:54 etc
> -rw-r--r--  1 20415 messagebus  1683 Jul 30 03:15 hadoop-client.list
> drwxr-xr-x  2 20415 messagebus  4096 Jul 30 02:54 include
> drwxr-xr-x  2 20415 messagebus  4096 Jul 30 02:54 libexec
> drwxr-xr-x  2 20415 messagebus  4096 Jul 30 02:54 sbin
> drwxr-xr-x  4 20415 messagebus  4096 Jul 30 02:54 share
> drwxr-xr-x 19 20415 messagebus  4096 Jul 30 03:01 src
>
>
>
> --Brahma Reddy Battula
>
> -----Original Message-----
> From: Konstantin Shvachko [mailto:shv.hadoop@gmail.com]
> Sent: 30 July 2017 07:29
> To: common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
> mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org
> Subject: [VOTE] Release Apache Hadoop 2.7.4 (RC0)
>
> Hi everybody,
>
> Here is the next release of Apache Hadoop 2.7 line. The previous stable
> release 2.7.3 was available since 25 August, 2016.
> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
> critical bug fixes and major optimizations. See more details in Release
> Note:
> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>
> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>
> Please give it a try and vote on this thread. The vote will run for 5 days
> ending 08/04/2017.
>
> Please note that my up to date public key are available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> Please don't forget to refresh the page if you've been there recently.
> There are other place on Apache sites, which may contain my outdated key.
>
> Thanks,
> --Konstantin
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Konstantin Shvachko <sh...@gmail.com>.
Hi Brahma Reddy Battula,

Formally Apache releases sources. We provide binaries as a reference for
convenience.
The release instructions for Hadoop 2.7 line at
https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
don't give much guidance on how to actually build and package the binary
tarball.
I intentionally included sources as the main content of the release.
And did not include native binaries, which very much depend on the
environment.
LMK if binary packaging is a blocker for you.

Thanks,
--Konstantin

On Sun, Jul 30, 2017 at 7:45 PM, Brahma Reddy Battula <
brahmareddy.battula@huawei.com> wrote:

> Thanks konstantin.
>
> Native files (lib/native) is missed
> And src folder exists in tar ball.
>
> Please check the same.
>
> Host1:/home/Brahma/Release/hadoop-2.7.4 # ll
> total 144
> -rw-r--r--  1 20415 messagebus 86424 Jul 30 02:54 LICENSE.txt
> -rw-r--r--  1 20415 messagebus 14978 Jul 30 02:54 NOTICE.txt
> -rw-r--r--  1 20415 messagebus  1366 Jul 30 02:54 README.txt
> drwxr-xr-x  2 20415 messagebus  4096 Jul 30 02:54 bin
> drwxr-xr-x  3 20415 messagebus  4096 Jul 30 02:54 etc
> -rw-r--r--  1 20415 messagebus  1683 Jul 30 03:15 hadoop-client.list
> drwxr-xr-x  2 20415 messagebus  4096 Jul 30 02:54 include
> drwxr-xr-x  2 20415 messagebus  4096 Jul 30 02:54 libexec
> drwxr-xr-x  2 20415 messagebus  4096 Jul 30 02:54 sbin
> drwxr-xr-x  4 20415 messagebus  4096 Jul 30 02:54 share
> drwxr-xr-x 19 20415 messagebus  4096 Jul 30 03:01 src
>
>
>
> --Brahma Reddy Battula
>
> -----Original Message-----
> From: Konstantin Shvachko [mailto:shv.hadoop@gmail.com]
> Sent: 30 July 2017 07:29
> To: common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
> mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org
> Subject: [VOTE] Release Apache Hadoop 2.7.4 (RC0)
>
> Hi everybody,
>
> Here is the next release of Apache Hadoop 2.7 line. The previous stable
> release 2.7.3 was available since 25 August, 2016.
> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
> critical bug fixes and major optimizations. See more details in Release
> Note:
> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>
> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>
> Please give it a try and vote on this thread. The vote will run for 5 days
> ending 08/04/2017.
>
> Please note that my up to date public key are available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> Please don't forget to refresh the page if you've been there recently.
> There are other place on Apache sites, which may contain my outdated key.
>
> Thanks,
> --Konstantin
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Konstantin Shvachko <sh...@gmail.com>.
Hi Brahma Reddy Battula,

Formally Apache releases sources. We provide binaries as a reference for
convenience.
The release instructions for Hadoop 2.7 line at
https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
don't give much guidance on how to actually build and package the binary
tarball.
I intentionally included sources as the main content of the release.
And did not include native binaries, which very much depend on the
environment.
LMK if binary packaging is a blocker for you.

Thanks,
--Konstantin

On Sun, Jul 30, 2017 at 7:45 PM, Brahma Reddy Battula <
brahmareddy.battula@huawei.com> wrote:

> Thanks konstantin.
>
> Native files (lib/native) is missed
> And src folder exists in tar ball.
>
> Please check the same.
>
> Host1:/home/Brahma/Release/hadoop-2.7.4 # ll
> total 144
> -rw-r--r--  1 20415 messagebus 86424 Jul 30 02:54 LICENSE.txt
> -rw-r--r--  1 20415 messagebus 14978 Jul 30 02:54 NOTICE.txt
> -rw-r--r--  1 20415 messagebus  1366 Jul 30 02:54 README.txt
> drwxr-xr-x  2 20415 messagebus  4096 Jul 30 02:54 bin
> drwxr-xr-x  3 20415 messagebus  4096 Jul 30 02:54 etc
> -rw-r--r--  1 20415 messagebus  1683 Jul 30 03:15 hadoop-client.list
> drwxr-xr-x  2 20415 messagebus  4096 Jul 30 02:54 include
> drwxr-xr-x  2 20415 messagebus  4096 Jul 30 02:54 libexec
> drwxr-xr-x  2 20415 messagebus  4096 Jul 30 02:54 sbin
> drwxr-xr-x  4 20415 messagebus  4096 Jul 30 02:54 share
> drwxr-xr-x 19 20415 messagebus  4096 Jul 30 03:01 src
>
>
>
> --Brahma Reddy Battula
>
> -----Original Message-----
> From: Konstantin Shvachko [mailto:shv.hadoop@gmail.com]
> Sent: 30 July 2017 07:29
> To: common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
> mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org
> Subject: [VOTE] Release Apache Hadoop 2.7.4 (RC0)
>
> Hi everybody,
>
> Here is the next release of Apache Hadoop 2.7 line. The previous stable
> release 2.7.3 was available since 25 August, 2016.
> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
> critical bug fixes and major optimizations. See more details in Release
> Note:
> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>
> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>
> Please give it a try and vote on this thread. The vote will run for 5 days
> ending 08/04/2017.
>
> Please note that my up to date public key are available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> Please don't forget to refresh the page if you've been there recently.
> There are other place on Apache sites, which may contain my outdated key.
>
> Thanks,
> --Konstantin
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Konstantin Shvachko <sh...@gmail.com>.
Hi Brahma Reddy Battula,

Formally Apache releases sources. We provide binaries as a reference for
convenience.
The release instructions for Hadoop 2.7 line at
https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
don't give much guidance on how to actually build and package the binary
tarball.
I intentionally included sources as the main content of the release.
And did not include native binaries, which very much depend on the
environment.
LMK if binary packaging is a blocker for you.

Thanks,
--Konstantin

On Sun, Jul 30, 2017 at 7:45 PM, Brahma Reddy Battula <
brahmareddy.battula@huawei.com> wrote:

> Thanks konstantin.
>
> Native files (lib/native) is missed
> And src folder exists in tar ball.
>
> Please check the same.
>
> Host1:/home/Brahma/Release/hadoop-2.7.4 # ll
> total 144
> -rw-r--r--  1 20415 messagebus 86424 Jul 30 02:54 LICENSE.txt
> -rw-r--r--  1 20415 messagebus 14978 Jul 30 02:54 NOTICE.txt
> -rw-r--r--  1 20415 messagebus  1366 Jul 30 02:54 README.txt
> drwxr-xr-x  2 20415 messagebus  4096 Jul 30 02:54 bin
> drwxr-xr-x  3 20415 messagebus  4096 Jul 30 02:54 etc
> -rw-r--r--  1 20415 messagebus  1683 Jul 30 03:15 hadoop-client.list
> drwxr-xr-x  2 20415 messagebus  4096 Jul 30 02:54 include
> drwxr-xr-x  2 20415 messagebus  4096 Jul 30 02:54 libexec
> drwxr-xr-x  2 20415 messagebus  4096 Jul 30 02:54 sbin
> drwxr-xr-x  4 20415 messagebus  4096 Jul 30 02:54 share
> drwxr-xr-x 19 20415 messagebus  4096 Jul 30 03:01 src
>
>
>
> --Brahma Reddy Battula
>
> -----Original Message-----
> From: Konstantin Shvachko [mailto:shv.hadoop@gmail.com]
> Sent: 30 July 2017 07:29
> To: common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
> mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org
> Subject: [VOTE] Release Apache Hadoop 2.7.4 (RC0)
>
> Hi everybody,
>
> Here is the next release of Apache Hadoop 2.7 line. The previous stable
> release 2.7.3 was available since 25 August, 2016.
> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
> critical bug fixes and major optimizations. See more details in Release
> Note:
> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>
> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>
> Please give it a try and vote on this thread. The vote will run for 5 days
> ending 08/04/2017.
>
> Please note that my up to date public key are available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> Please don't forget to refresh the page if you've been there recently.
> There are other place on Apache sites, which may contain my outdated key.
>
> Thanks,
> --Konstantin
>

RE: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Brahma Reddy Battula <br...@huawei.com>.
Thanks konstantin.

Native files (lib/native) is missed
And src folder exists in tar ball.

Please check the same.

Host1:/home/Brahma/Release/hadoop-2.7.4 # ll
total 144
-rw-r--r--  1 20415 messagebus 86424 Jul 30 02:54 LICENSE.txt
-rw-r--r--  1 20415 messagebus 14978 Jul 30 02:54 NOTICE.txt
-rw-r--r--  1 20415 messagebus  1366 Jul 30 02:54 README.txt
drwxr-xr-x  2 20415 messagebus  4096 Jul 30 02:54 bin
drwxr-xr-x  3 20415 messagebus  4096 Jul 30 02:54 etc
-rw-r--r--  1 20415 messagebus  1683 Jul 30 03:15 hadoop-client.list
drwxr-xr-x  2 20415 messagebus  4096 Jul 30 02:54 include
drwxr-xr-x  2 20415 messagebus  4096 Jul 30 02:54 libexec
drwxr-xr-x  2 20415 messagebus  4096 Jul 30 02:54 sbin
drwxr-xr-x  4 20415 messagebus  4096 Jul 30 02:54 share
drwxr-xr-x 19 20415 messagebus  4096 Jul 30 03:01 src



--Brahma Reddy Battula

-----Original Message-----
From: Konstantin Shvachko [mailto:shv.hadoop@gmail.com] 
Sent: 30 July 2017 07:29
To: common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org
Subject: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Hi everybody,

Here is the next release of Apache Hadoop 2.7 line. The previous stable release 2.7.3 was available since 25 August, 2016.
Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are critical bug fixes and major optimizations. See more details in Release
Note:
http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html

The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/

Please give it a try and vote on this thread. The vote will run for 5 days ending 08/04/2017.

Please note that my up to date public key are available from:
https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
Please don't forget to refresh the page if you've been there recently.
There are other place on Apache sites, which may contain my outdated key.

Thanks,
--Konstantin

---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Brahma Reddy Battula <br...@huawei.com>.
Thanks konstantin.

Native files (lib/native) is missed
And src folder exists in tar ball.

Please check the same.

Host1:/home/Brahma/Release/hadoop-2.7.4 # ll
total 144
-rw-r--r--  1 20415 messagebus 86424 Jul 30 02:54 LICENSE.txt
-rw-r--r--  1 20415 messagebus 14978 Jul 30 02:54 NOTICE.txt
-rw-r--r--  1 20415 messagebus  1366 Jul 30 02:54 README.txt
drwxr-xr-x  2 20415 messagebus  4096 Jul 30 02:54 bin
drwxr-xr-x  3 20415 messagebus  4096 Jul 30 02:54 etc
-rw-r--r--  1 20415 messagebus  1683 Jul 30 03:15 hadoop-client.list
drwxr-xr-x  2 20415 messagebus  4096 Jul 30 02:54 include
drwxr-xr-x  2 20415 messagebus  4096 Jul 30 02:54 libexec
drwxr-xr-x  2 20415 messagebus  4096 Jul 30 02:54 sbin
drwxr-xr-x  4 20415 messagebus  4096 Jul 30 02:54 share
drwxr-xr-x 19 20415 messagebus  4096 Jul 30 03:01 src



--Brahma Reddy Battula

-----Original Message-----
From: Konstantin Shvachko [mailto:shv.hadoop@gmail.com] 
Sent: 30 July 2017 07:29
To: common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org
Subject: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Hi everybody,

Here is the next release of Apache Hadoop 2.7 line. The previous stable release 2.7.3 was available since 25 August, 2016.
Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are critical bug fixes and major optimizations. See more details in Release
Note:
http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html

The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/

Please give it a try and vote on this thread. The vote will run for 5 days ending 08/04/2017.

Please note that my up to date public key are available from:
https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
Please don't forget to refresh the page if you've been there recently.
There are other place on Apache sites, which may contain my outdated key.

Thanks,
--Konstantin

---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Akira Ajisaka <aa...@apache.org>.
Thanks! I'll check whether Apache Hive and Tez can be built with the artiacts.

-Akira

On 2017/08/03 16:34, Konstantin Shvachko wrote:
> Hi Akira,
>
> The artifacts are on Nexus in Staging Repositories:
> https://repository.apache.org/#stagingRepositories
> or
> https://repository.apache.org/content/repositories/orgapachehadoop-1061/
>
> They are not released yet, which happens once the release is approved.
> See in Publishing section #5
> https://wiki.apache.org/hadoop/HowToReleasePreDSBCR#Publishing
>
> Thanks,
> --Konst
>
> On Wed, Aug 2, 2017 at 11:36 PM, Akira Ajisaka <aajisaka@apache.org <ma...@apache.org>> wrote:
>
>     Thanks Konstantin for the work!
>     I have a question: Where are the maven artifacts deployed?
>
>     -Akira
>
>     On 2017/07/30 8:29, Konstantin Shvachko wrote:
>
>         Hi everybody,
>
>         Here is the next release of Apache Hadoop 2.7 line. The previous stable
>         release 2.7.3 was available since 25 August, 2016.
>         Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
>         critical bug fixes and major optimizations. See more details in Release
>         Note:
>         http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html <http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html>
>
>         The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/ <http://home.apache.org/~shv/hadoop-2.7.4-RC0/>
>
>         Please give it a try and vote on this thread. The vote will run for 5 days
>         ending 08/04/2017.
>
>         Please note that my up to date public key are available from:
>         https://dist.apache.org/repos/dist/release/hadoop/common/KEYS <https://dist.apache.org/repos/dist/release/hadoop/common/KEYS>
>         Please don't forget to refresh the page if you've been there recently.
>         There are other place on Apache sites, which may contain my outdated key.
>
>         Thanks,
>         --Konstantin
>
>

---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Akira Ajisaka <aa...@apache.org>.
Thanks! I'll check whether Apache Hive and Tez can be built with the artiacts.

-Akira

On 2017/08/03 16:34, Konstantin Shvachko wrote:
> Hi Akira,
>
> The artifacts are on Nexus in Staging Repositories:
> https://repository.apache.org/#stagingRepositories
> or
> https://repository.apache.org/content/repositories/orgapachehadoop-1061/
>
> They are not released yet, which happens once the release is approved.
> See in Publishing section #5
> https://wiki.apache.org/hadoop/HowToReleasePreDSBCR#Publishing
>
> Thanks,
> --Konst
>
> On Wed, Aug 2, 2017 at 11:36 PM, Akira Ajisaka <aajisaka@apache.org <ma...@apache.org>> wrote:
>
>     Thanks Konstantin for the work!
>     I have a question: Where are the maven artifacts deployed?
>
>     -Akira
>
>     On 2017/07/30 8:29, Konstantin Shvachko wrote:
>
>         Hi everybody,
>
>         Here is the next release of Apache Hadoop 2.7 line. The previous stable
>         release 2.7.3 was available since 25 August, 2016.
>         Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
>         critical bug fixes and major optimizations. See more details in Release
>         Note:
>         http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html <http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html>
>
>         The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/ <http://home.apache.org/~shv/hadoop-2.7.4-RC0/>
>
>         Please give it a try and vote on this thread. The vote will run for 5 days
>         ending 08/04/2017.
>
>         Please note that my up to date public key are available from:
>         https://dist.apache.org/repos/dist/release/hadoop/common/KEYS <https://dist.apache.org/repos/dist/release/hadoop/common/KEYS>
>         Please don't forget to refresh the page if you've been there recently.
>         There are other place on Apache sites, which may contain my outdated key.
>
>         Thanks,
>         --Konstantin
>
>

---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Akira Ajisaka <aa...@apache.org>.
Thanks! I'll check whether Apache Hive and Tez can be built with the artiacts.

-Akira

On 2017/08/03 16:34, Konstantin Shvachko wrote:
> Hi Akira,
>
> The artifacts are on Nexus in Staging Repositories:
> https://repository.apache.org/#stagingRepositories
> or
> https://repository.apache.org/content/repositories/orgapachehadoop-1061/
>
> They are not released yet, which happens once the release is approved.
> See in Publishing section #5
> https://wiki.apache.org/hadoop/HowToReleasePreDSBCR#Publishing
>
> Thanks,
> --Konst
>
> On Wed, Aug 2, 2017 at 11:36 PM, Akira Ajisaka <aajisaka@apache.org <ma...@apache.org>> wrote:
>
>     Thanks Konstantin for the work!
>     I have a question: Where are the maven artifacts deployed?
>
>     -Akira
>
>     On 2017/07/30 8:29, Konstantin Shvachko wrote:
>
>         Hi everybody,
>
>         Here is the next release of Apache Hadoop 2.7 line. The previous stable
>         release 2.7.3 was available since 25 August, 2016.
>         Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
>         critical bug fixes and major optimizations. See more details in Release
>         Note:
>         http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html <http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html>
>
>         The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/ <http://home.apache.org/~shv/hadoop-2.7.4-RC0/>
>
>         Please give it a try and vote on this thread. The vote will run for 5 days
>         ending 08/04/2017.
>
>         Please note that my up to date public key are available from:
>         https://dist.apache.org/repos/dist/release/hadoop/common/KEYS <https://dist.apache.org/repos/dist/release/hadoop/common/KEYS>
>         Please don't forget to refresh the page if you've been there recently.
>         There are other place on Apache sites, which may contain my outdated key.
>
>         Thanks,
>         --Konstantin
>
>

---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Akira Ajisaka <aa...@apache.org>.
Thanks! I'll check whether Apache Hive and Tez can be built with the artiacts.

-Akira

On 2017/08/03 16:34, Konstantin Shvachko wrote:
> Hi Akira,
>
> The artifacts are on Nexus in Staging Repositories:
> https://repository.apache.org/#stagingRepositories
> or
> https://repository.apache.org/content/repositories/orgapachehadoop-1061/
>
> They are not released yet, which happens once the release is approved.
> See in Publishing section #5
> https://wiki.apache.org/hadoop/HowToReleasePreDSBCR#Publishing
>
> Thanks,
> --Konst
>
> On Wed, Aug 2, 2017 at 11:36 PM, Akira Ajisaka <aajisaka@apache.org <ma...@apache.org>> wrote:
>
>     Thanks Konstantin for the work!
>     I have a question: Where are the maven artifacts deployed?
>
>     -Akira
>
>     On 2017/07/30 8:29, Konstantin Shvachko wrote:
>
>         Hi everybody,
>
>         Here is the next release of Apache Hadoop 2.7 line. The previous stable
>         release 2.7.3 was available since 25 August, 2016.
>         Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
>         critical bug fixes and major optimizations. See more details in Release
>         Note:
>         http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html <http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html>
>
>         The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/ <http://home.apache.org/~shv/hadoop-2.7.4-RC0/>
>
>         Please give it a try and vote on this thread. The vote will run for 5 days
>         ending 08/04/2017.
>
>         Please note that my up to date public key are available from:
>         https://dist.apache.org/repos/dist/release/hadoop/common/KEYS <https://dist.apache.org/repos/dist/release/hadoop/common/KEYS>
>         Please don't forget to refresh the page if you've been there recently.
>         There are other place on Apache sites, which may contain my outdated key.
>
>         Thanks,
>         --Konstantin
>
>

---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Konstantin Shvachko <sh...@gmail.com>.
Hi Akira,

The artifacts are on Nexus in Staging Repositories:
https://repository.apache.org/#stagingRepositories
or
https://repository.apache.org/content/repositories/orgapachehadoop-1061/

They are not released yet, which happens once the release is approved.
See in Publishing section #5
https://wiki.apache.org/hadoop/HowToReleasePreDSBCR#Publishing

Thanks,
--Konst

On Wed, Aug 2, 2017 at 11:36 PM, Akira Ajisaka <aa...@apache.org> wrote:

> Thanks Konstantin for the work!
> I have a question: Where are the maven artifacts deployed?
>
> -Akira
>
> On 2017/07/30 8:29, Konstantin Shvachko wrote:
>
>> Hi everybody,
>>
>> Here is the next release of Apache Hadoop 2.7 line. The previous stable
>> release 2.7.3 was available since 25 August, 2016.
>> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
>> critical bug fixes and major optimizations. See more details in Release
>> Note:
>> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>>
>> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>>
>> Please give it a try and vote on this thread. The vote will run for 5 days
>> ending 08/04/2017.
>>
>> Please note that my up to date public key are available from:
>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
>> Please don't forget to refresh the page if you've been there recently.
>> There are other place on Apache sites, which may contain my outdated key.
>>
>> Thanks,
>> --Konstantin
>>
>>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Konstantin Shvachko <sh...@gmail.com>.
Hi Akira,

The artifacts are on Nexus in Staging Repositories:
https://repository.apache.org/#stagingRepositories
or
https://repository.apache.org/content/repositories/orgapachehadoop-1061/

They are not released yet, which happens once the release is approved.
See in Publishing section #5
https://wiki.apache.org/hadoop/HowToReleasePreDSBCR#Publishing

Thanks,
--Konst

On Wed, Aug 2, 2017 at 11:36 PM, Akira Ajisaka <aa...@apache.org> wrote:

> Thanks Konstantin for the work!
> I have a question: Where are the maven artifacts deployed?
>
> -Akira
>
> On 2017/07/30 8:29, Konstantin Shvachko wrote:
>
>> Hi everybody,
>>
>> Here is the next release of Apache Hadoop 2.7 line. The previous stable
>> release 2.7.3 was available since 25 August, 2016.
>> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
>> critical bug fixes and major optimizations. See more details in Release
>> Note:
>> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>>
>> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>>
>> Please give it a try and vote on this thread. The vote will run for 5 days
>> ending 08/04/2017.
>>
>> Please note that my up to date public key are available from:
>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
>> Please don't forget to refresh the page if you've been there recently.
>> There are other place on Apache sites, which may contain my outdated key.
>>
>> Thanks,
>> --Konstantin
>>
>>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Konstantin Shvachko <sh...@gmail.com>.
Hi Akira,

The artifacts are on Nexus in Staging Repositories:
https://repository.apache.org/#stagingRepositories
or
https://repository.apache.org/content/repositories/orgapachehadoop-1061/

They are not released yet, which happens once the release is approved.
See in Publishing section #5
https://wiki.apache.org/hadoop/HowToReleasePreDSBCR#Publishing

Thanks,
--Konst

On Wed, Aug 2, 2017 at 11:36 PM, Akira Ajisaka <aa...@apache.org> wrote:

> Thanks Konstantin for the work!
> I have a question: Where are the maven artifacts deployed?
>
> -Akira
>
> On 2017/07/30 8:29, Konstantin Shvachko wrote:
>
>> Hi everybody,
>>
>> Here is the next release of Apache Hadoop 2.7 line. The previous stable
>> release 2.7.3 was available since 25 August, 2016.
>> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
>> critical bug fixes and major optimizations. See more details in Release
>> Note:
>> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>>
>> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>>
>> Please give it a try and vote on this thread. The vote will run for 5 days
>> ending 08/04/2017.
>>
>> Please note that my up to date public key are available from:
>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
>> Please don't forget to refresh the page if you've been there recently.
>> There are other place on Apache sites, which may contain my outdated key.
>>
>> Thanks,
>> --Konstantin
>>
>>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Konstantin Shvachko <sh...@gmail.com>.
Hi Akira,

The artifacts are on Nexus in Staging Repositories:
https://repository.apache.org/#stagingRepositories
or
https://repository.apache.org/content/repositories/orgapachehadoop-1061/

They are not released yet, which happens once the release is approved.
See in Publishing section #5
https://wiki.apache.org/hadoop/HowToReleasePreDSBCR#Publishing

Thanks,
--Konst

On Wed, Aug 2, 2017 at 11:36 PM, Akira Ajisaka <aa...@apache.org> wrote:

> Thanks Konstantin for the work!
> I have a question: Where are the maven artifacts deployed?
>
> -Akira
>
> On 2017/07/30 8:29, Konstantin Shvachko wrote:
>
>> Hi everybody,
>>
>> Here is the next release of Apache Hadoop 2.7 line. The previous stable
>> release 2.7.3 was available since 25 August, 2016.
>> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
>> critical bug fixes and major optimizations. See more details in Release
>> Note:
>> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>>
>> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>>
>> Please give it a try and vote on this thread. The vote will run for 5 days
>> ending 08/04/2017.
>>
>> Please note that my up to date public key are available from:
>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
>> Please don't forget to refresh the page if you've been there recently.
>> There are other place on Apache sites, which may contain my outdated key.
>>
>> Thanks,
>> --Konstantin
>>
>>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Akira Ajisaka <aa...@apache.org>.
Thanks Konstantin for the work!
I have a question: Where are the maven artifacts deployed?

-Akira

On 2017/07/30 8:29, Konstantin Shvachko wrote:
> Hi everybody,
>
> Here is the next release of Apache Hadoop 2.7 line. The previous stable
> release 2.7.3 was available since 25 August, 2016.
> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
> critical bug fixes and major optimizations. See more details in Release
> Note:
> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>
> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>
> Please give it a try and vote on this thread. The vote will run for 5 days
> ending 08/04/2017.
>
> Please note that my up to date public key are available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> Please don't forget to refresh the page if you've been there recently.
> There are other place on Apache sites, which may contain my outdated key.
>
> Thanks,
> --Konstantin
>

---------------------------------------------------------------------
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.7.4 (RC0)

Posted by surendra lilhore <su...@huawei.com>.
+1 (non-binding)

   -Installed HA cluster.
   -Verified HDFS basic.
	-Read/Write/Append.
	-Snapshot
	-ACL
	-xAttr
	-Truncate
	-Quota
	-Admin operations


-Surendra Singh Lilhore


-----Original Message-----
From: Konstantin Shvachko [mailto:shv.hadoop@gmail.com] 
Sent: 30 July 2017 04:59
To: common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org
Subject: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Hi everybody,

Here is the next release of Apache Hadoop 2.7 line. The previous stable release 2.7.3 was available since 25 August, 2016.
Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are critical bug fixes and major optimizations. See more details in Release
Note:
http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html

The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/

Please give it a try and vote on this thread. The vote will run for 5 days ending 08/04/2017.

Please note that my up to date public key are available from:
https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
Please don't forget to refresh the page if you've been there recently.
There are other place on Apache sites, which may contain my outdated key.

Thanks,
--Konstantin

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Chris Douglas <ch...@gmail.com>.
+1 (binding)

Looked through the src tarball. Checksum and signature match, skimmed
NOTICE/LICENSE, ran some unit tests. -C

On Sat, Jul 29, 2017 at 4:29 PM, Konstantin Shvachko
<sh...@gmail.com> wrote:
> Hi everybody,
>
> Here is the next release of Apache Hadoop 2.7 line. The previous stable
> release 2.7.3 was available since 25 August, 2016.
> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
> critical bug fixes and major optimizations. See more details in Release
> Note:
> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>
> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>
> Please give it a try and vote on this thread. The vote will run for 5 days
> ending 08/04/2017.
>
> Please note that my up to date public key are available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> Please don't forget to refresh the page if you've been there recently.
> There are other place on Apache sites, which may contain my outdated key.
>
> Thanks,
> --Konstantin

---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Mingliang Liu <li...@gmail.com>.
Thanks Konstantin!

+1 (non-binding)

I have tried several steps including:
- Download source package and check the checksums
- Build from source using Java 8
- Deploy a test cluster using docker containers w/ 5 DNs and 1 NN
- Run basic HDFS client/admin operations (e.g. read/write files, dfsadmin)
- Run NNThroughputBenchmark (using the new -fs option)
- Run DistCp and example apps (wordcount, sort)

All looked good to me.

> On Jul 29, 2017, at 4:29 PM, Konstantin Shvachko <sh...@gmail.com> wrote:
> 
> Hi everybody,
> 
> Here is the next release of Apache Hadoop 2.7 line. The previous stable
> release 2.7.3 was available since 25 August, 2016.
> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
> critical bug fixes and major optimizations. See more details in Release
> Note:
> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
> 
> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
> 
> Please give it a try and vote on this thread. The vote will run for 5 days
> ending 08/04/2017.
> 
> Please note that my up to date public key are available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> Please don't forget to refresh the page if you've been there recently.
> There are other place on Apache sites, which may contain my outdated key.
> 
> Thanks,
> --Konstantin


---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Sunil G <su...@apache.org>.
Thanks Konstantin

+1 (binding)

1. Build tar ball from source package
2. Ran basic MR jobs and verified UI.
3. Enabled node labels and ran sleep job. Works fine.
4. Verified CLI commands related to node labels and its working fine.
5. RM WorkPreserving restart cases are also verified, and looks fine

Thanks
Sunil



On Sun, Jul 30, 2017 at 4:59 AM Konstantin Shvachko <sh...@gmail.com>
wrote:

> Hi everybody,
>
> Here is the next release of Apache Hadoop 2.7 line. The previous stable
> release 2.7.3 was available since 25 August, 2016.
> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
> critical bug fixes and major optimizations. See more details in Release
> Note:
> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>
> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>
> Please give it a try and vote on this thread. The vote will run for 5 days
> ending 08/04/2017.
>
> Please note that my up to date public key are available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> Please don't forget to refresh the page if you've been there recently.
> There are other place on Apache sites, which may contain my outdated key.
>
> Thanks,
> --Konstantin
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Chen Liang <cl...@hortonworks.com>.
Hi Konstantin,

Thanks for putting up 2.7.4-RC0 release!

+1 (non-binding).

With following checks:
- build the source on MacOS 10.12.5 with java version 1.8.0_91.
- deployed on a single node pseudo-custer
- tested HDFS basics: write/read/append/acl
- mapreduce job wordcount/bbp/grep

Thanks!
Chen 

________________________________________
From: Konstantin Shvachko <sh...@gmail.com>
Sent: Saturday, July 29, 2017 4:29 PM
To: common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org
Subject: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Hi everybody,

Here is the next release of Apache Hadoop 2.7 line. The previous stable
release 2.7.3 was available since 25 August, 2016.
Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
critical bug fixes and major optimizations. See more details in Release
Note:
http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html

The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/

Please give it a try and vote on this thread. The vote will run for 5 days
ending 08/04/2017.

Please note that my up to date public key are available from:
https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
Please don't forget to refresh the page if you've been there recently.
There are other place on Apache sites, which may contain my outdated key.

Thanks,
--Konstantin



---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Sunil G <su...@apache.org>.
Thanks Konstantin

+1 (binding)

1. Build tar ball from source package
2. Ran basic MR jobs and verified UI.
3. Enabled node labels and ran sleep job. Works fine.
4. Verified CLI commands related to node labels and its working fine.
5. RM WorkPreserving restart cases are also verified, and looks fine

Thanks
Sunil



On Sun, Jul 30, 2017 at 4:59 AM Konstantin Shvachko <sh...@gmail.com>
wrote:

> Hi everybody,
>
> Here is the next release of Apache Hadoop 2.7 line. The previous stable
> release 2.7.3 was available since 25 August, 2016.
> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
> critical bug fixes and major optimizations. See more details in Release
> Note:
> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>
> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>
> Please give it a try and vote on this thread. The vote will run for 5 days
> ending 08/04/2017.
>
> Please note that my up to date public key are available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> Please don't forget to refresh the page if you've been there recently.
> There are other place on Apache sites, which may contain my outdated key.
>
> Thanks,
> --Konstantin
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Akira Ajisaka <aa...@apache.org>.
Thanks Konstantin for the work!
I have a question: Where are the maven artifacts deployed?

-Akira

On 2017/07/30 8:29, Konstantin Shvachko wrote:
> Hi everybody,
>
> Here is the next release of Apache Hadoop 2.7 line. The previous stable
> release 2.7.3 was available since 25 August, 2016.
> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
> critical bug fixes and major optimizations. See more details in Release
> Note:
> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>
> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>
> Please give it a try and vote on this thread. The vote will run for 5 days
> ending 08/04/2017.
>
> Please note that my up to date public key are available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> Please don't forget to refresh the page if you've been there recently.
> There are other place on Apache sites, which may contain my outdated key.
>
> Thanks,
> --Konstantin
>

---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Brahma Reddy Battula <br...@huawei.com>.
Thanks konstantin.

Native files (lib/native) is missed
And src folder exists in tar ball.

Please check the same.

Host1:/home/Brahma/Release/hadoop-2.7.4 # ll
total 144
-rw-r--r--  1 20415 messagebus 86424 Jul 30 02:54 LICENSE.txt
-rw-r--r--  1 20415 messagebus 14978 Jul 30 02:54 NOTICE.txt
-rw-r--r--  1 20415 messagebus  1366 Jul 30 02:54 README.txt
drwxr-xr-x  2 20415 messagebus  4096 Jul 30 02:54 bin
drwxr-xr-x  3 20415 messagebus  4096 Jul 30 02:54 etc
-rw-r--r--  1 20415 messagebus  1683 Jul 30 03:15 hadoop-client.list
drwxr-xr-x  2 20415 messagebus  4096 Jul 30 02:54 include
drwxr-xr-x  2 20415 messagebus  4096 Jul 30 02:54 libexec
drwxr-xr-x  2 20415 messagebus  4096 Jul 30 02:54 sbin
drwxr-xr-x  4 20415 messagebus  4096 Jul 30 02:54 share
drwxr-xr-x 19 20415 messagebus  4096 Jul 30 03:01 src



--Brahma Reddy Battula

-----Original Message-----
From: Konstantin Shvachko [mailto:shv.hadoop@gmail.com] 
Sent: 30 July 2017 07:29
To: common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org
Subject: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Hi everybody,

Here is the next release of Apache Hadoop 2.7 line. The previous stable release 2.7.3 was available since 25 August, 2016.
Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are critical bug fixes and major optimizations. See more details in Release
Note:
http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html

The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/

Please give it a try and vote on this thread. The vote will run for 5 days ending 08/04/2017.

Please note that my up to date public key are available from:
https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
Please don't forget to refresh the page if you've been there recently.
There are other place on Apache sites, which may contain my outdated key.

Thanks,
--Konstantin

---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Masatake Iwasaki <iw...@oss.nttdata.co.jp>.
Thanks for putting this up, Konstantin.

I'm +1(non-binding) on the source tarball.

* verified signature and mds,
* built from source on CentOS 7 and OpenJDK 8 with native profile,
* built RPMs by bigtop, deployed 5 nodes cluster by docker provisioner, 
ran smoke-tests of hdfs, yarn and mapreduce,
* built site documentation and skimmed the contents.

The binary tarball seems to be inconsistent with previous 2.7.x releases 
as Brahma pointed out.

Bests,
Masatake Iwasaki


On 7/30/17 08:29, Konstantin Shvachko wrote:
> Hi everybody,
>
> Here is the next release of Apache Hadoop 2.7 line. The previous stable
> release 2.7.3 was available since 25 August, 2016.
> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
> critical bug fixes and major optimizations. See more details in Release
> Note:
> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>
> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>
> Please give it a try and vote on this thread. The vote will run for 5 days
> ending 08/04/2017.
>
> Please note that my up to date public key are available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> Please don't forget to refresh the page if you've been there recently.
> There are other place on Apache sites, which may contain my outdated key.
>
> Thanks,
> --Konstantin
>


---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Jason Lowe <jl...@yahoo-inc.com.INVALID>.
Thanks for driving the 2.7.4 release!
+1 (binding)
- Verified signatures and digests- Successfully built from source including native- Deployed to a single-node cluster and ran sample MapReduce jobs
Jason 

    On Saturday, July 29, 2017 6:29 PM, Konstantin Shvachko <sh...@gmail.com> wrote:
 

 Hi everybody,

Here is the next release of Apache Hadoop 2.7 line. The previous stable
release 2.7.3 was available since 25 August, 2016.
Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
critical bug fixes and major optimizations. See more details in Release
Note:
http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html

The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/

Please give it a try and vote on this thread. The vote will run for 5 days
ending 08/04/2017.

Please note that my up to date public key are available from:
https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
Please don't forget to refresh the page if you've been there recently.
There are other place on Apache sites, which may contain my outdated key.

Thanks,
--Konstantin


   

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Akira Ajisaka <aa...@apache.org>.
Thanks Konstantin for the work!
I have a question: Where are the maven artifacts deployed?

-Akira

On 2017/07/30 8:29, Konstantin Shvachko wrote:
> Hi everybody,
>
> Here is the next release of Apache Hadoop 2.7 line. The previous stable
> release 2.7.3 was available since 25 August, 2016.
> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
> critical bug fixes and major optimizations. See more details in Release
> Note:
> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>
> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>
> Please give it a try and vote on this thread. The vote will run for 5 days
> ending 08/04/2017.
>
> Please note that my up to date public key are available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> Please don't forget to refresh the page if you've been there recently.
> There are other place on Apache sites, which may contain my outdated key.
>
> Thanks,
> --Konstantin
>

---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Mingliang Liu <li...@gmail.com>.
Thanks Konstantin!

+1 (non-binding)

I have tried several steps including:
- Download source package and check the checksums
- Build from source using Java 8
- Deploy a test cluster using docker containers w/ 5 DNs and 1 NN
- Run basic HDFS client/admin operations (e.g. read/write files, dfsadmin)
- Run NNThroughputBenchmark (using the new -fs option)
- Run DistCp and example apps (wordcount, sort)

All looked good to me.

> On Jul 29, 2017, at 4:29 PM, Konstantin Shvachko <sh...@gmail.com> wrote:
> 
> Hi everybody,
> 
> Here is the next release of Apache Hadoop 2.7 line. The previous stable
> release 2.7.3 was available since 25 August, 2016.
> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
> critical bug fixes and major optimizations. See more details in Release
> Note:
> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
> 
> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
> 
> Please give it a try and vote on this thread. The vote will run for 5 days
> ending 08/04/2017.
> 
> Please note that my up to date public key are available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> Please don't forget to refresh the page if you've been there recently.
> There are other place on Apache sites, which may contain my outdated key.
> 
> Thanks,
> --Konstantin


---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Chris Douglas <ch...@gmail.com>.
+1 (binding)

Looked through the src tarball. Checksum and signature match, skimmed
NOTICE/LICENSE, ran some unit tests. -C

On Sat, Jul 29, 2017 at 4:29 PM, Konstantin Shvachko
<sh...@gmail.com> wrote:
> Hi everybody,
>
> Here is the next release of Apache Hadoop 2.7 line. The previous stable
> release 2.7.3 was available since 25 August, 2016.
> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
> critical bug fixes and major optimizations. See more details in Release
> Note:
> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>
> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>
> Please give it a try and vote on this thread. The vote will run for 5 days
> ending 08/04/2017.
>
> Please note that my up to date public key are available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> Please don't forget to refresh the page if you've been there recently.
> There are other place on Apache sites, which may contain my outdated key.
>
> Thanks,
> --Konstantin

---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Chen Liang <cl...@hortonworks.com>.
Hi Konstantin,

Thanks for putting up 2.7.4-RC0 release!

+1 (non-binding).

With following checks:
- build the source on MacOS 10.12.5 with java version 1.8.0_91.
- deployed on a single node pseudo-custer
- tested HDFS basics: write/read/append/acl
- mapreduce job wordcount/bbp/grep

Thanks!
Chen 

________________________________________
From: Konstantin Shvachko <sh...@gmail.com>
Sent: Saturday, July 29, 2017 4:29 PM
To: common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org
Subject: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Hi everybody,

Here is the next release of Apache Hadoop 2.7 line. The previous stable
release 2.7.3 was available since 25 August, 2016.
Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
critical bug fixes and major optimizations. See more details in Release
Note:
http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html

The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/

Please give it a try and vote on this thread. The vote will run for 5 days
ending 08/04/2017.

Please note that my up to date public key are available from:
https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
Please don't forget to refresh the page if you've been there recently.
There are other place on Apache sites, which may contain my outdated key.

Thanks,
--Konstantin



---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Mingliang Liu <li...@gmail.com>.
Thanks Konstantin!

+1 (non-binding)

I have tried several steps including:
- Download source package and check the checksums
- Build from source using Java 8
- Deploy a test cluster using docker containers w/ 5 DNs and 1 NN
- Run basic HDFS client/admin operations (e.g. read/write files, dfsadmin)
- Run NNThroughputBenchmark (using the new -fs option)
- Run DistCp and example apps (wordcount, sort)

All looked good to me.

> On Jul 29, 2017, at 4:29 PM, Konstantin Shvachko <sh...@gmail.com> wrote:
> 
> Hi everybody,
> 
> Here is the next release of Apache Hadoop 2.7 line. The previous stable
> release 2.7.3 was available since 25 August, 2016.
> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
> critical bug fixes and major optimizations. See more details in Release
> Note:
> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
> 
> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
> 
> Please give it a try and vote on this thread. The vote will run for 5 days
> ending 08/04/2017.
> 
> Please note that my up to date public key are available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> Please don't forget to refresh the page if you've been there recently.
> There are other place on Apache sites, which may contain my outdated key.
> 
> Thanks,
> --Konstantin


---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Sunil G <su...@apache.org>.
Thanks Konstantin

+1 (binding)

1. Build tar ball from source package
2. Ran basic MR jobs and verified UI.
3. Enabled node labels and ran sleep job. Works fine.
4. Verified CLI commands related to node labels and its working fine.
5. RM WorkPreserving restart cases are also verified, and looks fine

Thanks
Sunil



On Sun, Jul 30, 2017 at 4:59 AM Konstantin Shvachko <sh...@gmail.com>
wrote:

> Hi everybody,
>
> Here is the next release of Apache Hadoop 2.7 line. The previous stable
> release 2.7.3 was available since 25 August, 2016.
> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
> critical bug fixes and major optimizations. See more details in Release
> Note:
> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>
> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>
> Please give it a try and vote on this thread. The vote will run for 5 days
> ending 08/04/2017.
>
> Please note that my up to date public key are available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> Please don't forget to refresh the page if you've been there recently.
> There are other place on Apache sites, which may contain my outdated key.
>
> Thanks,
> --Konstantin
>

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Mingliang Liu <li...@gmail.com>.
Thanks Konstantin!

+1 (non-binding)

I have tried several steps including:
- Download source package and check the checksums
- Build from source using Java 8
- Deploy a test cluster using docker containers w/ 5 DNs and 1 NN
- Run basic HDFS client/admin operations (e.g. read/write files, dfsadmin)
- Run NNThroughputBenchmark (using the new -fs option)
- Run DistCp and example apps (wordcount, sort)

All looked good to me.

> On Jul 29, 2017, at 4:29 PM, Konstantin Shvachko <sh...@gmail.com> wrote:
> 
> Hi everybody,
> 
> Here is the next release of Apache Hadoop 2.7 line. The previous stable
> release 2.7.3 was available since 25 August, 2016.
> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
> critical bug fixes and major optimizations. See more details in Release
> Note:
> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
> 
> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
> 
> Please give it a try and vote on this thread. The vote will run for 5 days
> ending 08/04/2017.
> 
> Please note that my up to date public key are available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> Please don't forget to refresh the page if you've been there recently.
> There are other place on Apache sites, which may contain my outdated key.
> 
> Thanks,
> --Konstantin


---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Masatake Iwasaki <iw...@oss.nttdata.co.jp>.
Thanks for putting this up, Konstantin.

I'm +1(non-binding) on the source tarball.

* verified signature and mds,
* built from source on CentOS 7 and OpenJDK 8 with native profile,
* built RPMs by bigtop, deployed 5 nodes cluster by docker provisioner, 
ran smoke-tests of hdfs, yarn and mapreduce,
* built site documentation and skimmed the contents.

The binary tarball seems to be inconsistent with previous 2.7.x releases 
as Brahma pointed out.

Bests,
Masatake Iwasaki


On 7/30/17 08:29, Konstantin Shvachko wrote:
> Hi everybody,
>
> Here is the next release of Apache Hadoop 2.7 line. The previous stable
> release 2.7.3 was available since 25 August, 2016.
> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
> critical bug fixes and major optimizations. See more details in Release
> Note:
> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>
> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>
> Please give it a try and vote on this thread. The vote will run for 5 days
> ending 08/04/2017.
>
> Please note that my up to date public key are available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> Please don't forget to refresh the page if you've been there recently.
> There are other place on Apache sites, which may contain my outdated key.
>
> Thanks,
> --Konstantin
>


---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Jason Lowe <jl...@yahoo-inc.com.INVALID>.
Thanks for driving the 2.7.4 release!
+1 (binding)
- Verified signatures and digests- Successfully built from source including native- Deployed to a single-node cluster and ran sample MapReduce jobs
Jason 

    On Saturday, July 29, 2017 6:29 PM, Konstantin Shvachko <sh...@gmail.com> wrote:
 

 Hi everybody,

Here is the next release of Apache Hadoop 2.7 line. The previous stable
release 2.7.3 was available since 25 August, 2016.
Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
critical bug fixes and major optimizations. See more details in Release
Note:
http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html

The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/

Please give it a try and vote on this thread. The vote will run for 5 days
ending 08/04/2017.

Please note that my up to date public key are available from:
https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
Please don't forget to refresh the page if you've been there recently.
There are other place on Apache sites, which may contain my outdated key.

Thanks,
--Konstantin


   

RE: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Brahma Reddy Battula <br...@huawei.com>.
Thanks konstantin.

Native files (lib/native) is missed
And src folder exists in tar ball.

Please check the same.

Host1:/home/Brahma/Release/hadoop-2.7.4 # ll
total 144
-rw-r--r--  1 20415 messagebus 86424 Jul 30 02:54 LICENSE.txt
-rw-r--r--  1 20415 messagebus 14978 Jul 30 02:54 NOTICE.txt
-rw-r--r--  1 20415 messagebus  1366 Jul 30 02:54 README.txt
drwxr-xr-x  2 20415 messagebus  4096 Jul 30 02:54 bin
drwxr-xr-x  3 20415 messagebus  4096 Jul 30 02:54 etc
-rw-r--r--  1 20415 messagebus  1683 Jul 30 03:15 hadoop-client.list
drwxr-xr-x  2 20415 messagebus  4096 Jul 30 02:54 include
drwxr-xr-x  2 20415 messagebus  4096 Jul 30 02:54 libexec
drwxr-xr-x  2 20415 messagebus  4096 Jul 30 02:54 sbin
drwxr-xr-x  4 20415 messagebus  4096 Jul 30 02:54 share
drwxr-xr-x 19 20415 messagebus  4096 Jul 30 03:01 src



--Brahma Reddy Battula

-----Original Message-----
From: Konstantin Shvachko [mailto:shv.hadoop@gmail.com] 
Sent: 30 July 2017 07:29
To: common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org
Subject: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Hi everybody,

Here is the next release of Apache Hadoop 2.7 line. The previous stable release 2.7.3 was available since 25 August, 2016.
Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are critical bug fixes and major optimizations. See more details in Release
Note:
http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html

The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/

Please give it a try and vote on this thread. The vote will run for 5 days ending 08/04/2017.

Please note that my up to date public key are available from:
https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
Please don't forget to refresh the page if you've been there recently.
There are other place on Apache sites, which may contain my outdated key.

Thanks,
--Konstantin

---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Chen Liang <cl...@hortonworks.com>.
Hi Konstantin,

Thanks for putting up 2.7.4-RC0 release!

+1 (non-binding).

With following checks:
- build the source on MacOS 10.12.5 with java version 1.8.0_91.
- deployed on a single node pseudo-custer
- tested HDFS basics: write/read/append/acl
- mapreduce job wordcount/bbp/grep

Thanks!
Chen 

________________________________________
From: Konstantin Shvachko <sh...@gmail.com>
Sent: Saturday, July 29, 2017 4:29 PM
To: common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org
Subject: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Hi everybody,

Here is the next release of Apache Hadoop 2.7 line. The previous stable
release 2.7.3 was available since 25 August, 2016.
Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
critical bug fixes and major optimizations. See more details in Release
Note:
http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html

The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/

Please give it a try and vote on this thread. The vote will run for 5 days
ending 08/04/2017.

Please note that my up to date public key are available from:
https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
Please don't forget to refresh the page if you've been there recently.
There are other place on Apache sites, which may contain my outdated key.

Thanks,
--Konstantin



---------------------------------------------------------------------
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.7.4 (RC0)

Posted by John Zhuge <jo...@gmail.com>.
Hi Konstantin,

Thanks a lot for the effort to prepare the 2.7.4-RC0 release!

+1 (non-binding)

   - Verified checksums and signatures of all tarballs
   - Built source with native, Java 1.8.0_131-b11 on Mac OS X 10.12.6
   - Verified cloud connectors:
      - All S3A integration tests
   - Deployed both binary and built source to a pseudo cluster, passed the
   following sanity tests in insecure, SSL, and SSL+Kerberos mode:
      - HDFS basic and ACL
      - DistCp basic
      - MapReduce wordcount (only failed in SSL+Kerberos mode for binary
      tarball, probably unrelated)
      - KMS and HttpFS basic
      - Balancer start/stop

Shall we worry this test failures? Likely fixed by
https://issues.apache.org/jira/browse/HADOOP-13707.

   - Got “curl: (22) The requested URL returned error: 403 User dr.who is
   unauthorized to access this page.” when accessing NameNode web servlet
   /jmx, /conf, /logLevel, and /stacks. It passed in branch-2.8.


On Sat, Jul 29, 2017 at 4:29 PM, Konstantin Shvachko <sh...@gmail.com>
wrote:

> Hi everybody,
>
> Here is the next release of Apache Hadoop 2.7 line. The previous stable
> release 2.7.3 was available since 25 August, 2016.
> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
> critical bug fixes and major optimizations. See more details in Release
> Note:
> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>
> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>
> Please give it a try and vote on this thread. The vote will run for 5 days
> ending 08/04/2017.
>
> Please note that my up to date public key are available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> Please don't forget to refresh the page if you've been there recently.
> There are other place on Apache sites, which may contain my outdated key.
>
> Thanks,
> --Konstantin
>



-- 
John

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Akira Ajisaka <aa...@apache.org>.
Thanks Konstantin for the work!
I have a question: Where are the maven artifacts deployed?

-Akira

On 2017/07/30 8:29, Konstantin Shvachko wrote:
> Hi everybody,
>
> Here is the next release of Apache Hadoop 2.7 line. The previous stable
> release 2.7.3 was available since 25 August, 2016.
> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
> critical bug fixes and major optimizations. See more details in Release
> Note:
> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>
> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>
> Please give it a try and vote on this thread. The vote will run for 5 days
> ending 08/04/2017.
>
> Please note that my up to date public key are available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> Please don't forget to refresh the page if you've been there recently.
> There are other place on Apache sites, which may contain my outdated key.
>
> Thanks,
> --Konstantin
>

---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Chris Douglas <ch...@gmail.com>.
+1 (binding)

Looked through the src tarball. Checksum and signature match, skimmed
NOTICE/LICENSE, ran some unit tests. -C

On Sat, Jul 29, 2017 at 4:29 PM, Konstantin Shvachko
<sh...@gmail.com> wrote:
> Hi everybody,
>
> Here is the next release of Apache Hadoop 2.7 line. The previous stable
> release 2.7.3 was available since 25 August, 2016.
> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
> critical bug fixes and major optimizations. See more details in Release
> Note:
> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>
> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>
> Please give it a try and vote on this thread. The vote will run for 5 days
> ending 08/04/2017.
>
> Please note that my up to date public key are available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> Please don't forget to refresh the page if you've been there recently.
> There are other place on Apache sites, which may contain my outdated key.
>
> Thanks,
> --Konstantin

---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Chen Liang <cl...@hortonworks.com>.
Hi Konstantin,

Thanks for putting up 2.7.4-RC0 release!

+1 (non-binding).

With following checks:
- build the source on MacOS 10.12.5 with java version 1.8.0_91.
- deployed on a single node pseudo-custer
- tested HDFS basics: write/read/append/acl
- mapreduce job wordcount/bbp/grep

Thanks!
Chen 

________________________________________
From: Konstantin Shvachko <sh...@gmail.com>
Sent: Saturday, July 29, 2017 4:29 PM
To: common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org
Subject: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Hi everybody,

Here is the next release of Apache Hadoop 2.7 line. The previous stable
release 2.7.3 was available since 25 August, 2016.
Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
critical bug fixes and major optimizations. See more details in Release
Note:
http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html

The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/

Please give it a try and vote on this thread. The vote will run for 5 days
ending 08/04/2017.

Please note that my up to date public key are available from:
https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
Please don't forget to refresh the page if you've been there recently.
There are other place on Apache sites, which may contain my outdated key.

Thanks,
--Konstantin



---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Masatake Iwasaki <iw...@oss.nttdata.co.jp>.
Thanks for putting this up, Konstantin.

I'm +1(non-binding) on the source tarball.

* verified signature and mds,
* built from source on CentOS 7 and OpenJDK 8 with native profile,
* built RPMs by bigtop, deployed 5 nodes cluster by docker provisioner, 
ran smoke-tests of hdfs, yarn and mapreduce,
* built site documentation and skimmed the contents.

The binary tarball seems to be inconsistent with previous 2.7.x releases 
as Brahma pointed out.

Bests,
Masatake Iwasaki


On 7/30/17 08:29, Konstantin Shvachko wrote:
> Hi everybody,
>
> Here is the next release of Apache Hadoop 2.7 line. The previous stable
> release 2.7.3 was available since 25 August, 2016.
> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
> critical bug fixes and major optimizations. See more details in Release
> Note:
> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>
> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>
> Please give it a try and vote on this thread. The vote will run for 5 days
> ending 08/04/2017.
>
> Please note that my up to date public key are available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> Please don't forget to refresh the page if you've been there recently.
> There are other place on Apache sites, which may contain my outdated key.
>
> Thanks,
> --Konstantin
>


---------------------------------------------------------------------
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.7.4 (RC0)

Posted by John Zhuge <jo...@gmail.com>.
Hi Konstantin,

Thanks a lot for the effort to prepare the 2.7.4-RC0 release!

+1 (non-binding)

   - Verified checksums and signatures of all tarballs
   - Built source with native, Java 1.8.0_131-b11 on Mac OS X 10.12.6
   - Verified cloud connectors:
      - All S3A integration tests
   - Deployed both binary and built source to a pseudo cluster, passed the
   following sanity tests in insecure, SSL, and SSL+Kerberos mode:
      - HDFS basic and ACL
      - DistCp basic
      - MapReduce wordcount (only failed in SSL+Kerberos mode for binary
      tarball, probably unrelated)
      - KMS and HttpFS basic
      - Balancer start/stop

Shall we worry this test failures? Likely fixed by
https://issues.apache.org/jira/browse/HADOOP-13707.

   - Got “curl: (22) The requested URL returned error: 403 User dr.who is
   unauthorized to access this page.” when accessing NameNode web servlet
   /jmx, /conf, /logLevel, and /stacks. It passed in branch-2.8.


On Sat, Jul 29, 2017 at 4:29 PM, Konstantin Shvachko <sh...@gmail.com>
wrote:

> Hi everybody,
>
> Here is the next release of Apache Hadoop 2.7 line. The previous stable
> release 2.7.3 was available since 25 August, 2016.
> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
> critical bug fixes and major optimizations. See more details in Release
> Note:
> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>
> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>
> Please give it a try and vote on this thread. The vote will run for 5 days
> ending 08/04/2017.
>
> Please note that my up to date public key are available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> Please don't forget to refresh the page if you've been there recently.
> There are other place on Apache sites, which may contain my outdated key.
>
> Thanks,
> --Konstantin
>



-- 
John

RE: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by surendra lilhore <su...@huawei.com>.
+1 (non-binding)

   -Installed HA cluster.
   -Verified HDFS basic.
	-Read/Write/Append.
	-Snapshot
	-ACL
	-xAttr
	-Truncate
	-Quota
	-Admin operations


-Surendra Singh Lilhore


-----Original Message-----
From: Konstantin Shvachko [mailto:shv.hadoop@gmail.com] 
Sent: 30 July 2017 04:59
To: common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org
Subject: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Hi everybody,

Here is the next release of Apache Hadoop 2.7 line. The previous stable release 2.7.3 was available since 25 August, 2016.
Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are critical bug fixes and major optimizations. See more details in Release
Note:
http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html

The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/

Please give it a try and vote on this thread. The vote will run for 5 days ending 08/04/2017.

Please note that my up to date public key are available from:
https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
Please don't forget to refresh the page if you've been there recently.
There are other place on Apache sites, which may contain my outdated key.

Thanks,
--Konstantin

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Chris Douglas <ch...@gmail.com>.
+1 (binding)

Looked through the src tarball. Checksum and signature match, skimmed
NOTICE/LICENSE, ran some unit tests. -C

On Sat, Jul 29, 2017 at 4:29 PM, Konstantin Shvachko
<sh...@gmail.com> wrote:
> Hi everybody,
>
> Here is the next release of Apache Hadoop 2.7 line. The previous stable
> release 2.7.3 was available since 25 August, 2016.
> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
> critical bug fixes and major optimizations. See more details in Release
> Note:
> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>
> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>
> Please give it a try and vote on this thread. The vote will run for 5 days
> ending 08/04/2017.
>
> Please note that my up to date public key are available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> Please don't forget to refresh the page if you've been there recently.
> There are other place on Apache sites, which may contain my outdated key.
>
> Thanks,
> --Konstantin

---------------------------------------------------------------------
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.7.4 (RC0)

Posted by Jason Lowe <jl...@yahoo-inc.com.INVALID>.
Thanks for driving the 2.7.4 release!
+1 (binding)
- Verified signatures and digests- Successfully built from source including native- Deployed to a single-node cluster and ran sample MapReduce jobs
Jason 

    On Saturday, July 29, 2017 6:29 PM, Konstantin Shvachko <sh...@gmail.com> wrote:
 

 Hi everybody,

Here is the next release of Apache Hadoop 2.7 line. The previous stable
release 2.7.3 was available since 25 August, 2016.
Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
critical bug fixes and major optimizations. See more details in Release
Note:
http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html

The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/

Please give it a try and vote on this thread. The vote will run for 5 days
ending 08/04/2017.

Please note that my up to date public key are available from:
https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
Please don't forget to refresh the page if you've been there recently.
There are other place on Apache sites, which may contain my outdated key.

Thanks,
--Konstantin


   

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by John Zhuge <jo...@gmail.com>.
Hi Konstantin,

Thanks a lot for the effort to prepare the 2.7.4-RC0 release!

+1 (non-binding)

   - Verified checksums and signatures of all tarballs
   - Built source with native, Java 1.8.0_131-b11 on Mac OS X 10.12.6
   - Verified cloud connectors:
      - All S3A integration tests
   - Deployed both binary and built source to a pseudo cluster, passed the
   following sanity tests in insecure, SSL, and SSL+Kerberos mode:
      - HDFS basic and ACL
      - DistCp basic
      - MapReduce wordcount (only failed in SSL+Kerberos mode for binary
      tarball, probably unrelated)
      - KMS and HttpFS basic
      - Balancer start/stop

Shall we worry this test failures? Likely fixed by
https://issues.apache.org/jira/browse/HADOOP-13707.

   - Got “curl: (22) The requested URL returned error: 403 User dr.who is
   unauthorized to access this page.” when accessing NameNode web servlet
   /jmx, /conf, /logLevel, and /stacks. It passed in branch-2.8.


On Sat, Jul 29, 2017 at 4:29 PM, Konstantin Shvachko <sh...@gmail.com>
wrote:

> Hi everybody,
>
> Here is the next release of Apache Hadoop 2.7 line. The previous stable
> release 2.7.3 was available since 25 August, 2016.
> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
> critical bug fixes and major optimizations. See more details in Release
> Note:
> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>
> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>
> Please give it a try and vote on this thread. The vote will run for 5 days
> ending 08/04/2017.
>
> Please note that my up to date public key are available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> Please don't forget to refresh the page if you've been there recently.
> There are other place on Apache sites, which may contain my outdated key.
>
> Thanks,
> --Konstantin
>



-- 
John

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

Posted by Masatake Iwasaki <iw...@oss.nttdata.co.jp>.
Thanks for putting this up, Konstantin.

I'm +1(non-binding) on the source tarball.

* verified signature and mds,
* built from source on CentOS 7 and OpenJDK 8 with native profile,
* built RPMs by bigtop, deployed 5 nodes cluster by docker provisioner, 
ran smoke-tests of hdfs, yarn and mapreduce,
* built site documentation and skimmed the contents.

The binary tarball seems to be inconsistent with previous 2.7.x releases 
as Brahma pointed out.

Bests,
Masatake Iwasaki


On 7/30/17 08:29, Konstantin Shvachko wrote:
> Hi everybody,
>
> Here is the next release of Apache Hadoop 2.7 line. The previous stable
> release 2.7.3 was available since 25 August, 2016.
> Release 2.7.4 includes 264 issues fixed after release 2.7.3, which are
> critical bug fixes and major optimizations. See more details in Release
> Note:
> http://home.apache.org/~shv/hadoop-2.7.4-RC0/releasenotes.html
>
> The RC0 is available at: http://home.apache.org/~shv/hadoop-2.7.4-RC0/
>
> Please give it a try and vote on this thread. The vote will run for 5 days
> ending 08/04/2017.
>
> Please note that my up to date public key are available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> Please don't forget to refresh the page if you've been there recently.
> There are other place on Apache sites, which may contain my outdated key.
>
> Thanks,
> --Konstantin
>


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