You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by Vinod Kumar Vavilapalli <vi...@apache.org> on 2015/12/17 03:49:29 UTC
[VOTE] Release Apache Hadoop 2.7.2 RC1
Hi all,
I've created a release candidate RC1 for Apache Hadoop 2.7.2.
As discussed before, this is the next maintenance release to follow up 2.7.1.
The RC is available for validation at: http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
The RC tag in git is: release-2.7.2-RC1
The maven artifacts are available via repository.apache.org <http://repository.apache.org/> at https://repository.apache.org/content/repositories/orgapachehadoop-1026/ <https://repository.apache.org/content/repositories/orgapachehadoop-1026/>
The release-notes are inside the tar-balls at location hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I hosted this at http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for quick perusal.
As you may have noted,
- The RC0 related voting thread got halted due to some critical issues. It took a while again for getting all those blockers out of the way. See the previous voting thread [3] for details.
- Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by quite a bit. This release's related discussion threads are linked below: [1] and [2].
Please try the release and vote; the vote will run for the usual 5 days.
Thanks,
Vinod
[1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <http://markmail.org/message/oozq3gvd4nhzsaes>
[2]: Planning Apache Hadoop 2.7.2 http://markmail.org/message/iktqss2qdeykgpqk <http://markmail.org/message/iktqss2qdeykgpqk>
[3]: [VOTE] Release Apache Hadoop 2.7.2 RC0: http://markmail.org/message/5txhvr2qdiqglrwc
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Sunil Govind <su...@gmail.com>.
+1 (Non Binding)
* Built tar ball from source and deployed
* Ran few MR Jobs successfully. Also tested preemption, node labels sanity
scenarios including HA.
* Verified RM Web UI and ran few REST queries. Seems fine.
* CLI commands related to refresh are also working fine.
Thanks and Regards
Sunil G
On Mon, Dec 21, 2015 at 5:41 PM Naganarasimha G R (Naga) <
garlanaganarasimha@huawei.com> wrote:
> +1 (Non binding)
>
> * Release notes and CHANGES.txt looked fine
> * Verified md5 checksums for both source and binary tar balls
> * Ran `mvn apache-rat:check` on source tarball, passed
> * Installed pseudo cluster
> * Did some basic filesystem operations
> * Ran a grep, sleepjob, word count successfully
> * Verified the jobs RM, job history server and ATS Web ui's successfully
> * Verified some RM REST apis
> * Verified basic admin operations of Node Labels.
>
> Regards,
> +Naga
> ________________________________________
> From: Akira AJISAKA [ajisakaa@oss.nttdata.co.jp]
> Sent: Monday, December 21, 2015 14:29
> To: common-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org;
> hdfs-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org
> Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
>
> +1 (binding)
>
> - Downloaded source tarball
> - Verified signatures and checksums
> - Compiled and built a single node cluster
> - Confirmed commons-collections is upgraded to 3.2.2
> - Compiled Hive 1.2.1 and Tez 0.7.0/0.8.1-alpha using Hadoop 2.7.2 pom
> successfully
> - Ran some Hive on Tez/MRv2 queries successfully
>
> On 12/19/15 02:24, Jason Lowe wrote:
> > +1 (binding)
> > - Verified signatures and digests- Spot checked CHANGES.txt files-
> Successfully performed a native build from source- Deployed to a single
> node cluster and ran sample jobs
> > We have been running with the fix for YARN-4354 on two of our clusters
> for some time with no issues, so I feel confident that prior blocker is now
> fixed.
> > Jason
> >
> >
> > From: Vinod Kumar Vavilapalli <vi...@apache.org>
> > To: Hadoop Common <co...@hadoop.apache.org>;
> hdfs-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org;
> mapreduce-dev@hadoop.apache.org
> > Cc: Vinod Kumar Vavilapalli <vi...@apache.org>
> > Sent: Wednesday, December 16, 2015 8:49 PM
> > Subject: [VOTE] Release Apache Hadoop 2.7.2 RC1
> >
> > Hi all,
> >
> > I've created a release candidate RC1 for Apache Hadoop 2.7.2.
> >
> > As discussed before, this is the next maintenance release to follow up
> 2.7.1.
> >
> > The RC is available for validation at:
> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <
> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
> >
> > The RC tag in git is: release-2.7.2-RC1
> >
> > The maven artifacts are available via repository.apache.org <
> http://repository.apache.org/> at
> https://repository.apache.org/content/repositories/orgapachehadoop-1026/ <
> https://repository.apache.org/content/repositories/orgapachehadoop-1026/>
> >
> > The release-notes are inside the tar-balls at location
> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I
> hosted this at
> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for
> quick perusal.
> >
> > As you may have noted,
> > - The RC0 related voting thread got halted due to some critical
> issues. It took a while again for getting all those blockers out of the
> way. See the previous voting thread [3] for details.
> > - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by
> quite a bit. This release's related discussion threads are linked below:
> [1] and [2].
> >
> > Please try the release and vote; the vote will run for the usual 5 days.
> >
> > Thanks,
> > Vinod
> >
> > [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <
> http://markmail.org/message/oozq3gvd4nhzsaes>
> > [2]: Planning Apache Hadoop 2.7.2
> http://markmail.org/message/iktqss2qdeykgpqk <
> http://markmail.org/message/iktqss2qdeykgpqk>
> > [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
> http://markmail.org/message/5txhvr2qdiqglrwc
> >
> >
> >
> >
>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Sunil Govind <su...@gmail.com>.
+1 (Non Binding)
* Built tar ball from source and deployed
* Ran few MR Jobs successfully. Also tested preemption, node labels sanity
scenarios including HA.
* Verified RM Web UI and ran few REST queries. Seems fine.
* CLI commands related to refresh are also working fine.
Thanks and Regards
Sunil G
On Mon, Dec 21, 2015 at 5:41 PM Naganarasimha G R (Naga) <
garlanaganarasimha@huawei.com> wrote:
> +1 (Non binding)
>
> * Release notes and CHANGES.txt looked fine
> * Verified md5 checksums for both source and binary tar balls
> * Ran `mvn apache-rat:check` on source tarball, passed
> * Installed pseudo cluster
> * Did some basic filesystem operations
> * Ran a grep, sleepjob, word count successfully
> * Verified the jobs RM, job history server and ATS Web ui's successfully
> * Verified some RM REST apis
> * Verified basic admin operations of Node Labels.
>
> Regards,
> +Naga
> ________________________________________
> From: Akira AJISAKA [ajisakaa@oss.nttdata.co.jp]
> Sent: Monday, December 21, 2015 14:29
> To: common-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org;
> hdfs-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org
> Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
>
> +1 (binding)
>
> - Downloaded source tarball
> - Verified signatures and checksums
> - Compiled and built a single node cluster
> - Confirmed commons-collections is upgraded to 3.2.2
> - Compiled Hive 1.2.1 and Tez 0.7.0/0.8.1-alpha using Hadoop 2.7.2 pom
> successfully
> - Ran some Hive on Tez/MRv2 queries successfully
>
> On 12/19/15 02:24, Jason Lowe wrote:
> > +1 (binding)
> > - Verified signatures and digests- Spot checked CHANGES.txt files-
> Successfully performed a native build from source- Deployed to a single
> node cluster and ran sample jobs
> > We have been running with the fix for YARN-4354 on two of our clusters
> for some time with no issues, so I feel confident that prior blocker is now
> fixed.
> > Jason
> >
> >
> > From: Vinod Kumar Vavilapalli <vi...@apache.org>
> > To: Hadoop Common <co...@hadoop.apache.org>;
> hdfs-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org;
> mapreduce-dev@hadoop.apache.org
> > Cc: Vinod Kumar Vavilapalli <vi...@apache.org>
> > Sent: Wednesday, December 16, 2015 8:49 PM
> > Subject: [VOTE] Release Apache Hadoop 2.7.2 RC1
> >
> > Hi all,
> >
> > I've created a release candidate RC1 for Apache Hadoop 2.7.2.
> >
> > As discussed before, this is the next maintenance release to follow up
> 2.7.1.
> >
> > The RC is available for validation at:
> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <
> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
> >
> > The RC tag in git is: release-2.7.2-RC1
> >
> > The maven artifacts are available via repository.apache.org <
> http://repository.apache.org/> at
> https://repository.apache.org/content/repositories/orgapachehadoop-1026/ <
> https://repository.apache.org/content/repositories/orgapachehadoop-1026/>
> >
> > The release-notes are inside the tar-balls at location
> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I
> hosted this at
> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for
> quick perusal.
> >
> > As you may have noted,
> > - The RC0 related voting thread got halted due to some critical
> issues. It took a while again for getting all those blockers out of the
> way. See the previous voting thread [3] for details.
> > - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by
> quite a bit. This release's related discussion threads are linked below:
> [1] and [2].
> >
> > Please try the release and vote; the vote will run for the usual 5 days.
> >
> > Thanks,
> > Vinod
> >
> > [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <
> http://markmail.org/message/oozq3gvd4nhzsaes>
> > [2]: Planning Apache Hadoop 2.7.2
> http://markmail.org/message/iktqss2qdeykgpqk <
> http://markmail.org/message/iktqss2qdeykgpqk>
> > [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
> http://markmail.org/message/5txhvr2qdiqglrwc
> >
> >
> >
> >
>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Sunil Govind <su...@gmail.com>.
+1 (Non Binding)
* Built tar ball from source and deployed
* Ran few MR Jobs successfully. Also tested preemption, node labels sanity
scenarios including HA.
* Verified RM Web UI and ran few REST queries. Seems fine.
* CLI commands related to refresh are also working fine.
Thanks and Regards
Sunil G
On Mon, Dec 21, 2015 at 5:41 PM Naganarasimha G R (Naga) <
garlanaganarasimha@huawei.com> wrote:
> +1 (Non binding)
>
> * Release notes and CHANGES.txt looked fine
> * Verified md5 checksums for both source and binary tar balls
> * Ran `mvn apache-rat:check` on source tarball, passed
> * Installed pseudo cluster
> * Did some basic filesystem operations
> * Ran a grep, sleepjob, word count successfully
> * Verified the jobs RM, job history server and ATS Web ui's successfully
> * Verified some RM REST apis
> * Verified basic admin operations of Node Labels.
>
> Regards,
> +Naga
> ________________________________________
> From: Akira AJISAKA [ajisakaa@oss.nttdata.co.jp]
> Sent: Monday, December 21, 2015 14:29
> To: common-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org;
> hdfs-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org
> Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
>
> +1 (binding)
>
> - Downloaded source tarball
> - Verified signatures and checksums
> - Compiled and built a single node cluster
> - Confirmed commons-collections is upgraded to 3.2.2
> - Compiled Hive 1.2.1 and Tez 0.7.0/0.8.1-alpha using Hadoop 2.7.2 pom
> successfully
> - Ran some Hive on Tez/MRv2 queries successfully
>
> On 12/19/15 02:24, Jason Lowe wrote:
> > +1 (binding)
> > - Verified signatures and digests- Spot checked CHANGES.txt files-
> Successfully performed a native build from source- Deployed to a single
> node cluster and ran sample jobs
> > We have been running with the fix for YARN-4354 on two of our clusters
> for some time with no issues, so I feel confident that prior blocker is now
> fixed.
> > Jason
> >
> >
> > From: Vinod Kumar Vavilapalli <vi...@apache.org>
> > To: Hadoop Common <co...@hadoop.apache.org>;
> hdfs-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org;
> mapreduce-dev@hadoop.apache.org
> > Cc: Vinod Kumar Vavilapalli <vi...@apache.org>
> > Sent: Wednesday, December 16, 2015 8:49 PM
> > Subject: [VOTE] Release Apache Hadoop 2.7.2 RC1
> >
> > Hi all,
> >
> > I've created a release candidate RC1 for Apache Hadoop 2.7.2.
> >
> > As discussed before, this is the next maintenance release to follow up
> 2.7.1.
> >
> > The RC is available for validation at:
> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <
> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
> >
> > The RC tag in git is: release-2.7.2-RC1
> >
> > The maven artifacts are available via repository.apache.org <
> http://repository.apache.org/> at
> https://repository.apache.org/content/repositories/orgapachehadoop-1026/ <
> https://repository.apache.org/content/repositories/orgapachehadoop-1026/>
> >
> > The release-notes are inside the tar-balls at location
> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I
> hosted this at
> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for
> quick perusal.
> >
> > As you may have noted,
> > - The RC0 related voting thread got halted due to some critical
> issues. It took a while again for getting all those blockers out of the
> way. See the previous voting thread [3] for details.
> > - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by
> quite a bit. This release's related discussion threads are linked below:
> [1] and [2].
> >
> > Please try the release and vote; the vote will run for the usual 5 days.
> >
> > Thanks,
> > Vinod
> >
> > [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <
> http://markmail.org/message/oozq3gvd4nhzsaes>
> > [2]: Planning Apache Hadoop 2.7.2
> http://markmail.org/message/iktqss2qdeykgpqk <
> http://markmail.org/message/iktqss2qdeykgpqk>
> > [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
> http://markmail.org/message/5txhvr2qdiqglrwc
> >
> >
> >
> >
>
>
RE: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by "Naganarasimha G R (Naga)" <ga...@huawei.com>.
+1 (Non binding)
* Release notes and CHANGES.txt looked fine
* Verified md5 checksums for both source and binary tar balls
* Ran `mvn apache-rat:check` on source tarball, passed
* Installed pseudo cluster
* Did some basic filesystem operations
* Ran a grep, sleepjob, word count successfully
* Verified the jobs RM, job history server and ATS Web ui's successfully
* Verified some RM REST apis
* Verified basic admin operations of Node Labels.
Regards,
+Naga
________________________________________
From: Akira AJISAKA [ajisakaa@oss.nttdata.co.jp]
Sent: Monday, December 21, 2015 14:29
To: common-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org
Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
+1 (binding)
- Downloaded source tarball
- Verified signatures and checksums
- Compiled and built a single node cluster
- Confirmed commons-collections is upgraded to 3.2.2
- Compiled Hive 1.2.1 and Tez 0.7.0/0.8.1-alpha using Hadoop 2.7.2 pom
successfully
- Ran some Hive on Tez/MRv2 queries successfully
On 12/19/15 02:24, Jason Lowe wrote:
> +1 (binding)
> - Verified signatures and digests- Spot checked CHANGES.txt files- Successfully performed a native build from source- Deployed to a single node cluster and ran sample jobs
> We have been running with the fix for YARN-4354 on two of our clusters for some time with no issues, so I feel confident that prior blocker is now fixed.
> Jason
>
>
> From: Vinod Kumar Vavilapalli <vi...@apache.org>
> To: Hadoop Common <co...@hadoop.apache.org>; hdfs-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org
> Cc: Vinod Kumar Vavilapalli <vi...@apache.org>
> Sent: Wednesday, December 16, 2015 8:49 PM
> Subject: [VOTE] Release Apache Hadoop 2.7.2 RC1
>
> Hi all,
>
> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>
> As discussed before, this is the next maintenance release to follow up 2.7.1.
>
> The RC is available for validation at: http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>
> The RC tag in git is: release-2.7.2-RC1
>
> The maven artifacts are available via repository.apache.org <http://repository.apache.org/> at https://repository.apache.org/content/repositories/orgapachehadoop-1026/ <https://repository.apache.org/content/repositories/orgapachehadoop-1026/>
>
> The release-notes are inside the tar-balls at location hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I hosted this at http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for quick perusal.
>
> As you may have noted,
> - The RC0 related voting thread got halted due to some critical issues. It took a while again for getting all those blockers out of the way. See the previous voting thread [3] for details.
> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by quite a bit. This release's related discussion threads are linked below: [1] and [2].
>
> Please try the release and vote; the vote will run for the usual 5 days.
>
> Thanks,
> Vinod
>
> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <http://markmail.org/message/oozq3gvd4nhzsaes>
> [2]: Planning Apache Hadoop 2.7.2 http://markmail.org/message/iktqss2qdeykgpqk <http://markmail.org/message/iktqss2qdeykgpqk>
> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0: http://markmail.org/message/5txhvr2qdiqglrwc
>
>
>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Akira AJISAKA <aj...@oss.nttdata.co.jp>.
+1 (binding)
- Downloaded source tarball
- Verified signatures and checksums
- Compiled and built a single node cluster
- Confirmed commons-collections is upgraded to 3.2.2
- Compiled Hive 1.2.1 and Tez 0.7.0/0.8.1-alpha using Hadoop 2.7.2 pom
successfully
- Ran some Hive on Tez/MRv2 queries successfully
On 12/19/15 02:24, Jason Lowe wrote:
> +1 (binding)
> - Verified signatures and digests- Spot checked CHANGES.txt files- Successfully performed a native build from source- Deployed to a single node cluster and ran sample jobs
> We have been running with the fix for YARN-4354 on two of our clusters for some time with no issues, so I feel confident that prior blocker is now fixed.
> Jason
>
>
> From: Vinod Kumar Vavilapalli <vi...@apache.org>
> To: Hadoop Common <co...@hadoop.apache.org>; hdfs-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org
> Cc: Vinod Kumar Vavilapalli <vi...@apache.org>
> Sent: Wednesday, December 16, 2015 8:49 PM
> Subject: [VOTE] Release Apache Hadoop 2.7.2 RC1
>
> Hi all,
>
> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>
> As discussed before, this is the next maintenance release to follow up 2.7.1.
>
> The RC is available for validation at: http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>
> The RC tag in git is: release-2.7.2-RC1
>
> The maven artifacts are available via repository.apache.org <http://repository.apache.org/> at https://repository.apache.org/content/repositories/orgapachehadoop-1026/ <https://repository.apache.org/content/repositories/orgapachehadoop-1026/>
>
> The release-notes are inside the tar-balls at location hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I hosted this at http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for quick perusal.
>
> As you may have noted,
> - The RC0 related voting thread got halted due to some critical issues. It took a while again for getting all those blockers out of the way. See the previous voting thread [3] for details.
> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by quite a bit. This release's related discussion threads are linked below: [1] and [2].
>
> Please try the release and vote; the vote will run for the usual 5 days.
>
> Thanks,
> Vinod
>
> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <http://markmail.org/message/oozq3gvd4nhzsaes>
> [2]: Planning Apache Hadoop 2.7.2 http://markmail.org/message/iktqss2qdeykgpqk <http://markmail.org/message/iktqss2qdeykgpqk>
> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0: http://markmail.org/message/5txhvr2qdiqglrwc
>
>
>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Akira AJISAKA <aj...@oss.nttdata.co.jp>.
+1 (binding)
- Downloaded source tarball
- Verified signatures and checksums
- Compiled and built a single node cluster
- Confirmed commons-collections is upgraded to 3.2.2
- Compiled Hive 1.2.1 and Tez 0.7.0/0.8.1-alpha using Hadoop 2.7.2 pom
successfully
- Ran some Hive on Tez/MRv2 queries successfully
On 12/19/15 02:24, Jason Lowe wrote:
> +1 (binding)
> - Verified signatures and digests- Spot checked CHANGES.txt files- Successfully performed a native build from source- Deployed to a single node cluster and ran sample jobs
> We have been running with the fix for YARN-4354 on two of our clusters for some time with no issues, so I feel confident that prior blocker is now fixed.
> Jason
>
>
> From: Vinod Kumar Vavilapalli <vi...@apache.org>
> To: Hadoop Common <co...@hadoop.apache.org>; hdfs-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org
> Cc: Vinod Kumar Vavilapalli <vi...@apache.org>
> Sent: Wednesday, December 16, 2015 8:49 PM
> Subject: [VOTE] Release Apache Hadoop 2.7.2 RC1
>
> Hi all,
>
> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>
> As discussed before, this is the next maintenance release to follow up 2.7.1.
>
> The RC is available for validation at: http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>
> The RC tag in git is: release-2.7.2-RC1
>
> The maven artifacts are available via repository.apache.org <http://repository.apache.org/> at https://repository.apache.org/content/repositories/orgapachehadoop-1026/ <https://repository.apache.org/content/repositories/orgapachehadoop-1026/>
>
> The release-notes are inside the tar-balls at location hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I hosted this at http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for quick perusal.
>
> As you may have noted,
> - The RC0 related voting thread got halted due to some critical issues. It took a while again for getting all those blockers out of the way. See the previous voting thread [3] for details.
> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by quite a bit. This release's related discussion threads are linked below: [1] and [2].
>
> Please try the release and vote; the vote will run for the usual 5 days.
>
> Thanks,
> Vinod
>
> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <http://markmail.org/message/oozq3gvd4nhzsaes>
> [2]: Planning Apache Hadoop 2.7.2 http://markmail.org/message/iktqss2qdeykgpqk <http://markmail.org/message/iktqss2qdeykgpqk>
> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0: http://markmail.org/message/5txhvr2qdiqglrwc
>
>
>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Akira AJISAKA <aj...@oss.nttdata.co.jp>.
+1 (binding)
- Downloaded source tarball
- Verified signatures and checksums
- Compiled and built a single node cluster
- Confirmed commons-collections is upgraded to 3.2.2
- Compiled Hive 1.2.1 and Tez 0.7.0/0.8.1-alpha using Hadoop 2.7.2 pom
successfully
- Ran some Hive on Tez/MRv2 queries successfully
On 12/19/15 02:24, Jason Lowe wrote:
> +1 (binding)
> - Verified signatures and digests- Spot checked CHANGES.txt files- Successfully performed a native build from source- Deployed to a single node cluster and ran sample jobs
> We have been running with the fix for YARN-4354 on two of our clusters for some time with no issues, so I feel confident that prior blocker is now fixed.
> Jason
>
>
> From: Vinod Kumar Vavilapalli <vi...@apache.org>
> To: Hadoop Common <co...@hadoop.apache.org>; hdfs-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org
> Cc: Vinod Kumar Vavilapalli <vi...@apache.org>
> Sent: Wednesday, December 16, 2015 8:49 PM
> Subject: [VOTE] Release Apache Hadoop 2.7.2 RC1
>
> Hi all,
>
> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>
> As discussed before, this is the next maintenance release to follow up 2.7.1.
>
> The RC is available for validation at: http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>
> The RC tag in git is: release-2.7.2-RC1
>
> The maven artifacts are available via repository.apache.org <http://repository.apache.org/> at https://repository.apache.org/content/repositories/orgapachehadoop-1026/ <https://repository.apache.org/content/repositories/orgapachehadoop-1026/>
>
> The release-notes are inside the tar-balls at location hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I hosted this at http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for quick perusal.
>
> As you may have noted,
> - The RC0 related voting thread got halted due to some critical issues. It took a while again for getting all those blockers out of the way. See the previous voting thread [3] for details.
> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by quite a bit. This release's related discussion threads are linked below: [1] and [2].
>
> Please try the release and vote; the vote will run for the usual 5 days.
>
> Thanks,
> Vinod
>
> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <http://markmail.org/message/oozq3gvd4nhzsaes>
> [2]: Planning Apache Hadoop 2.7.2 http://markmail.org/message/iktqss2qdeykgpqk <http://markmail.org/message/iktqss2qdeykgpqk>
> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0: http://markmail.org/message/5txhvr2qdiqglrwc
>
>
>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Akira AJISAKA <aj...@oss.nttdata.co.jp>.
+1 (binding)
- Downloaded source tarball
- Verified signatures and checksums
- Compiled and built a single node cluster
- Confirmed commons-collections is upgraded to 3.2.2
- Compiled Hive 1.2.1 and Tez 0.7.0/0.8.1-alpha using Hadoop 2.7.2 pom
successfully
- Ran some Hive on Tez/MRv2 queries successfully
On 12/19/15 02:24, Jason Lowe wrote:
> +1 (binding)
> - Verified signatures and digests- Spot checked CHANGES.txt files- Successfully performed a native build from source- Deployed to a single node cluster and ran sample jobs
> We have been running with the fix for YARN-4354 on two of our clusters for some time with no issues, so I feel confident that prior blocker is now fixed.
> Jason
>
>
> From: Vinod Kumar Vavilapalli <vi...@apache.org>
> To: Hadoop Common <co...@hadoop.apache.org>; hdfs-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org
> Cc: Vinod Kumar Vavilapalli <vi...@apache.org>
> Sent: Wednesday, December 16, 2015 8:49 PM
> Subject: [VOTE] Release Apache Hadoop 2.7.2 RC1
>
> Hi all,
>
> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>
> As discussed before, this is the next maintenance release to follow up 2.7.1.
>
> The RC is available for validation at: http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>
> The RC tag in git is: release-2.7.2-RC1
>
> The maven artifacts are available via repository.apache.org <http://repository.apache.org/> at https://repository.apache.org/content/repositories/orgapachehadoop-1026/ <https://repository.apache.org/content/repositories/orgapachehadoop-1026/>
>
> The release-notes are inside the tar-balls at location hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I hosted this at http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for quick perusal.
>
> As you may have noted,
> - The RC0 related voting thread got halted due to some critical issues. It took a while again for getting all those blockers out of the way. See the previous voting thread [3] for details.
> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by quite a bit. This release's related discussion threads are linked below: [1] and [2].
>
> Please try the release and vote; the vote will run for the usual 5 days.
>
> Thanks,
> Vinod
>
> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <http://markmail.org/message/oozq3gvd4nhzsaes>
> [2]: Planning Apache Hadoop 2.7.2 http://markmail.org/message/iktqss2qdeykgpqk <http://markmail.org/message/iktqss2qdeykgpqk>
> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0: http://markmail.org/message/5txhvr2qdiqglrwc
>
>
>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Jason Lowe <jl...@yahoo-inc.com.INVALID>.
+1 (binding)
- Verified signatures and digests- Spot checked CHANGES.txt files- Successfully performed a native build from source- Deployed to a single node cluster and ran sample jobs
We have been running with the fix for YARN-4354 on two of our clusters for some time with no issues, so I feel confident that prior blocker is now fixed.
Jason
From: Vinod Kumar Vavilapalli <vi...@apache.org>
To: Hadoop Common <co...@hadoop.apache.org>; hdfs-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org
Cc: Vinod Kumar Vavilapalli <vi...@apache.org>
Sent: Wednesday, December 16, 2015 8:49 PM
Subject: [VOTE] Release Apache Hadoop 2.7.2 RC1
Hi all,
I've created a release candidate RC1 for Apache Hadoop 2.7.2.
As discussed before, this is the next maintenance release to follow up 2.7.1.
The RC is available for validation at: http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
The RC tag in git is: release-2.7.2-RC1
The maven artifacts are available via repository.apache.org <http://repository.apache.org/> at https://repository.apache.org/content/repositories/orgapachehadoop-1026/ <https://repository.apache.org/content/repositories/orgapachehadoop-1026/>
The release-notes are inside the tar-balls at location hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I hosted this at http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for quick perusal.
As you may have noted,
- The RC0 related voting thread got halted due to some critical issues. It took a while again for getting all those blockers out of the way. See the previous voting thread [3] for details.
- Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by quite a bit. This release's related discussion threads are linked below: [1] and [2].
Please try the release and vote; the vote will run for the usual 5 days.
Thanks,
Vinod
[1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <http://markmail.org/message/oozq3gvd4nhzsaes>
[2]: Planning Apache Hadoop 2.7.2 http://markmail.org/message/iktqss2qdeykgpqk <http://markmail.org/message/iktqss2qdeykgpqk>
[3]: [VOTE] Release Apache Hadoop 2.7.2 RC0: http://markmail.org/message/5txhvr2qdiqglrwc
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Jason Lowe <jl...@yahoo-inc.com.INVALID>.
+1 (binding)
- Verified signatures and digests- Spot checked CHANGES.txt files- Successfully performed a native build from source- Deployed to a single node cluster and ran sample jobs
We have been running with the fix for YARN-4354 on two of our clusters for some time with no issues, so I feel confident that prior blocker is now fixed.
Jason
From: Vinod Kumar Vavilapalli <vi...@apache.org>
To: Hadoop Common <co...@hadoop.apache.org>; hdfs-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org
Cc: Vinod Kumar Vavilapalli <vi...@apache.org>
Sent: Wednesday, December 16, 2015 8:49 PM
Subject: [VOTE] Release Apache Hadoop 2.7.2 RC1
Hi all,
I've created a release candidate RC1 for Apache Hadoop 2.7.2.
As discussed before, this is the next maintenance release to follow up 2.7.1.
The RC is available for validation at: http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
The RC tag in git is: release-2.7.2-RC1
The maven artifacts are available via repository.apache.org <http://repository.apache.org/> at https://repository.apache.org/content/repositories/orgapachehadoop-1026/ <https://repository.apache.org/content/repositories/orgapachehadoop-1026/>
The release-notes are inside the tar-balls at location hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I hosted this at http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for quick perusal.
As you may have noted,
- The RC0 related voting thread got halted due to some critical issues. It took a while again for getting all those blockers out of the way. See the previous voting thread [3] for details.
- Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by quite a bit. This release's related discussion threads are linked below: [1] and [2].
Please try the release and vote; the vote will run for the usual 5 days.
Thanks,
Vinod
[1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <http://markmail.org/message/oozq3gvd4nhzsaes>
[2]: Planning Apache Hadoop 2.7.2 http://markmail.org/message/iktqss2qdeykgpqk <http://markmail.org/message/iktqss2qdeykgpqk>
[3]: [VOTE] Release Apache Hadoop 2.7.2 RC0: http://markmail.org/message/5txhvr2qdiqglrwc
RE: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Rohith Sharma K S <ro...@huawei.com>.
+1(non-binding)
-Built from source and deployed in 3 node cluster
-Tested with combination of RMRestart/RM HA/RM work preserving restart/NM work preserving restart modes.
-Ran MR and distributed shell sample applications.
-Verified signature and md5 of binary
Thanks & Regards
Rohith Sharma K S
-----Original Message-----
From: Tsuyoshi Ozawa [mailto:ozawa@apache.org]
Sent: 22 December 2015 09:04
To: common-dev@hadoop.apache.org
Cc: yarn-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org; Vinod Kumar Vavilapalli
Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
+1
- downloaded src and bin tar balls and verified signatures.
- built Tez and Spark with 2.7.2 artifacts and JDK7.
- ran tests of Tez with 2.7.2 artifacts, it passed.
FYI: YARN-4348, reported by Jian, is one of critical issues of 2.7.2 release.It's better to release 2.7.3 as soon as possible after this release.
Thanks,
- Tsuyoshi
On Tue, Dec 22, 2015 at 4:51 AM, Wangda Tan <wh...@gmail.com> wrote:
> +1 (binding)
>
> - Build & deploy single-node Hadoop from source code
> - Add/Remove node labels to queues/nodes
> - Run distributed shell commanding using default/specified node labels
>
> Thanks,
> Wangda
>
>
> On Mon, Dec 21, 2015 at 9:58 AM, Masatake Iwasaki <
> iwasakims@oss.nttdata.co.jp> wrote:
>
>> +1(non-binding)
>>
>> - verified mds and signature of source and binary tarball
>> - started 3 node cluster and ran example jobs such as wordcount and
>> terasort
>> - built from source tarball with -Pnative on CentOS 7 and OpenJDK 7
>> - built site documentation and skimmed the contents
>>
>> Thanks,
>> Masatake Iwasaki
>>
>>
>>
>> On 12/17/15 11:49, Vinod Kumar Vavilapalli wrote:
>>
>>> Hi all,
>>>
>>> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>>>
>>> As discussed before, this is the next maintenance release to follow
>>> up 2.7.1.
>>>
>>> The RC is available for validation at:
>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <
>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>>>
>>> The RC tag in git is: release-2.7.2-RC1
>>>
>>> The maven artifacts are available via repository.apache.org <
>>> http://repository.apache.org/> at
>>> https://repository.apache.org/content/repositories/orgapachehadoop-1
>>> 026/
>>> <https://repository.apache.org/content/repositories/orgapachehadoop-
>>> 1026/
>>> >
>>>
>>> The release-notes are inside the tar-balls at location
>>> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html.
>>> I hosted this at
>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html
>>> for quick perusal.
>>>
>>> As you may have noted,
>>> - The RC0 related voting thread got halted due to some critical issues.
>>> It took a while again for getting all those blockers out of the way.
>>> See the previous voting thread [3] for details.
>>> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip
>>> by quite a bit. This release's related discussion threads are linked below:
>>> [1] and [2].
>>>
>>> Please try the release and vote; the vote will run for the usual 5 days.
>>>
>>> Thanks,
>>> Vinod
>>>
>>> [1]: 2.7.2 release plan:
>>> http://markmail.org/message/oozq3gvd4nhzsaes <
>>> http://markmail.org/message/oozq3gvd4nhzsaes>
>>> [2]: Planning Apache Hadoop 2.7.2
>>> http://markmail.org/message/iktqss2qdeykgpqk <
>>> http://markmail.org/message/iktqss2qdeykgpqk>
>>> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
>>> http://markmail.org/message/5txhvr2qdiqglrwc
>>>
>>>
>>>
>>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Andrew Wang <an...@cloudera.com>.
On Mon, Jan 11, 2016 at 7:22 AM, Junping Du <jd...@hortonworks.com> wrote:
> bq. Is it difficult to backport to 2.7.x if you're already backporting to
> 2.6.x? I don't follow why special casing some class of fixes is desirable.
> It is not difficult to backport the commits between 2.6.x and 2.7.x.
> However, it do *difficult* to track exactly for hundreds of commits between
> them. Taking HDFS-9470 as an example, the committer totally forget to merge
> the commit into 2.7.2 when it is resolved as fixed in 2.7.2. The commit was
> merged into 2.6.3 later but get missed on 2.7.2 RC1. If this is not a
> critical fix, I don't think 2.7.2 should get a new RC to wait this commit
> to land on. That's why classifying on priority of fixes are important and
> desirable when we are facing this situation.
>
> Gotcha, so this in this case it is the exception and not the rule? I'd
still rather the rule be simple, and then exceptions like this addressed on
a case-by-case basis.
Colin also wrote a branch-diff tool that looks at git log, which makes
tracking easier. You can do things like diff 2.6.0 with 2.6.3, 2.7.0 with
2.7.2, and then make sure that the 2.7 diff is a superset of 2.6.
https://github.com/cmccabe/cmccabe-hbin/blob/master/jirafun.go
Wouldn't be the worst idea to make this part of our release validation
process. The report could be automated as a Jenkins job.
> bq. Also for maintenance releases, aren't all included fixes supposed to
> be for serious bugs? Minor JIRAs can wait for the next minor release. If
> there are strong reasons to include a minor JIRA in a maintenance release,
> then maybe it's not really a minor JIRA.
> If a committer commit a major/minor priority patch on a maintenance
> release, what RM should do? Revert it or upgrade the priority to critical
> even it doesn't belong to critical?
> I believe only commit critical/blocker patch to maintenance release can
> only be a general guideline for maintenance release, but not a strict rule
> for all committers in practice. RMs should obey this guideline strictly in
> cherry-pick commits but there are more commits get committed by other
> committers. The committer choose the fixed branch not only by priority but
> also by target branch proposed by patch contributor who may only work on
> that branch release for a long time. I think this target/fix branch
> negotiation mechanism going on well and we shouldn't break it.
>
> This sounds like another reminder for everyone to:
- Please be judicious about what gets backported to maintenance releases.
- When backporting, please backport to all intermediate maintenance
branches.
Based on what I've seen, the RMs have been very responsive, so the safest
thing is to ping them about inclusion before backporting. I'd be in favor
of a guideline like "get an RM to +1 before backporting."
Best,
Andrew
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Sangjin Lee <sj...@apache.org>.
I agree that it would be a good practice to maintain parity between 2.6.x
and 2.7.x as much as possible. Departure from it should be more of an
exception than the norm.
That said, it is also true that we're not exactly following the semantic
versioning the moment we started to maintain multiple simultaneous release
branches. In semantic versioning, the timing of the release doesn't really
matter. If we were following semantic versioning, all releases in 2.6.x
would be considered "earlier versions" than 2.7.x regardless of their
release time. Obviously we cannot ensure no regression in that situation.
FWIW.
On Fri, Jan 8, 2016 at 11:43 AM, Andrew Wang <an...@cloudera.com>
wrote:
> I like monotonic releases since it's simple for users to understand. Is it
> difficult to backport to 2.7.x if you're already backporting to 2.6.x? I
> don't follow why special casing some class of fixes is desirable.
>
> Also for maintenance releases, aren't all included fixes supposed to be for
> serious bugs? Minor JIRAs can wait for the next minor release. If there are
> strong reasons to include a minor JIRA in a maintenance release, then maybe
> it's not really a minor JIRA.
>
> Best,
> Andrew
>
> On Fri, Jan 8, 2016 at 8:43 AM, Akira AJISAKA <aj...@oss.nttdata.co.jp>
> wrote:
>
> > The general rule sounds good to me.
> >
> > > "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that
> > get out after 2.x.y release date"
> >
> > +1
> >
> > > I would prefer this rule only applies on critical/blocker fixes, but
> not
> > applies on minor/trivial issues.
> >
> > +1
> >
> > Thanks,
> > Akira
> >
> >
> > On 12/29/15 23:50, Junping Du wrote:
> >
> >> I am +1 with pulling all of these tickets into 2.7.2.
> >>
> >> - For “any fix in 2.6.3 to be there in all releases that get out after
> >> 2.6.3 release date”
> >>
> >> Shall we conclude this as a general rule - "any fix in 2.x.y to be there
> >> in all 2.b.c releases (while b>=x) that get out after 2.x.y release
> date"?
> >> I am generally fine with this, but just feel it sounds to set too strong
> >> restrictions among branches. Some fixes could be trivial (test case fix,
> >> etc.) enough to deserve more flexibility. I would prefer this rule only
> >> applies on critical/blocker fixes, but not applies on minor/trivial
> issues.
> >>
> >> Just 2 cents.
> >>
> >>
> >> Thanks,
> >>
> >>
> >> Junping
> >>
> >>
> >> ________________________________
> >> From: Vinod Kumar Vavilapalli <vi...@apache.org>
> >> Sent: Thursday, December 24, 2015 12:47 AM
> >> To: Junping Du
> >> Cc: mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org;
> >> common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org
> >> Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
> >>
> >> I retract my -1. I think we will need to discuss this a bit more.
> >>
> >> Beyond those two tickets, there are a bunch more (totaling to 16) that
> >> are in 2.6.3 but *not* in 2.7.2. See this:
> >>
> https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0
> >> <
> >>
> https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0
> >> >
> >>
> >> Two options here, depending on the importance of ‘causality' between
> >> 2.6.x and 2.7.x lines.
> >> - Ship 2.7.2 as we voted on here
> >> - Pull these 16 tickets into 2.7.2 and roll a new RC
> >>
> >> What do people think? Do folks expect “any fix in 2.6.3 to be there in
> >> all releases that get out after 2.6.3 release date (December 16th)”?
> >>
> >> Thanks
> >> +Vinod
> >>
> >> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <
> vinodkv@apache.org
> >> <ma...@apache.org>> wrote:
> >>
> >> Sigh. Missed this.
> >>
> >> To retain causality ("any fix in 2.6.3 will be there in all releases
> that
> >> got out after 2.6.3”), I’ll get these patches in.
> >>
> >> Reverting my +1, and casting -1 for the RC myself.
> >>
> >> Will spin a new RC, this voting thread is marked dead.
> >>
> >> Thanks
> >> +Vinod
> >>
> >> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com<mailto:
> >> jdu@hortonworks.com>> wrote:
> >>
> >> However, when I look at our commit log and CHANGES.txt, I found
> something
> >> we are missing:
> >> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1
> tag.
> >> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
> >>
> >>
> >>
> >
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Sangjin Lee <sj...@apache.org>.
I agree that it would be a good practice to maintain parity between 2.6.x
and 2.7.x as much as possible. Departure from it should be more of an
exception than the norm.
That said, it is also true that we're not exactly following the semantic
versioning the moment we started to maintain multiple simultaneous release
branches. In semantic versioning, the timing of the release doesn't really
matter. If we were following semantic versioning, all releases in 2.6.x
would be considered "earlier versions" than 2.7.x regardless of their
release time. Obviously we cannot ensure no regression in that situation.
FWIW.
On Fri, Jan 8, 2016 at 11:43 AM, Andrew Wang <an...@cloudera.com>
wrote:
> I like monotonic releases since it's simple for users to understand. Is it
> difficult to backport to 2.7.x if you're already backporting to 2.6.x? I
> don't follow why special casing some class of fixes is desirable.
>
> Also for maintenance releases, aren't all included fixes supposed to be for
> serious bugs? Minor JIRAs can wait for the next minor release. If there are
> strong reasons to include a minor JIRA in a maintenance release, then maybe
> it's not really a minor JIRA.
>
> Best,
> Andrew
>
> On Fri, Jan 8, 2016 at 8:43 AM, Akira AJISAKA <aj...@oss.nttdata.co.jp>
> wrote:
>
> > The general rule sounds good to me.
> >
> > > "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that
> > get out after 2.x.y release date"
> >
> > +1
> >
> > > I would prefer this rule only applies on critical/blocker fixes, but
> not
> > applies on minor/trivial issues.
> >
> > +1
> >
> > Thanks,
> > Akira
> >
> >
> > On 12/29/15 23:50, Junping Du wrote:
> >
> >> I am +1 with pulling all of these tickets into 2.7.2.
> >>
> >> - For “any fix in 2.6.3 to be there in all releases that get out after
> >> 2.6.3 release date”
> >>
> >> Shall we conclude this as a general rule - "any fix in 2.x.y to be there
> >> in all 2.b.c releases (while b>=x) that get out after 2.x.y release
> date"?
> >> I am generally fine with this, but just feel it sounds to set too strong
> >> restrictions among branches. Some fixes could be trivial (test case fix,
> >> etc.) enough to deserve more flexibility. I would prefer this rule only
> >> applies on critical/blocker fixes, but not applies on minor/trivial
> issues.
> >>
> >> Just 2 cents.
> >>
> >>
> >> Thanks,
> >>
> >>
> >> Junping
> >>
> >>
> >> ________________________________
> >> From: Vinod Kumar Vavilapalli <vi...@apache.org>
> >> Sent: Thursday, December 24, 2015 12:47 AM
> >> To: Junping Du
> >> Cc: mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org;
> >> common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org
> >> Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
> >>
> >> I retract my -1. I think we will need to discuss this a bit more.
> >>
> >> Beyond those two tickets, there are a bunch more (totaling to 16) that
> >> are in 2.6.3 but *not* in 2.7.2. See this:
> >>
> https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0
> >> <
> >>
> https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0
> >> >
> >>
> >> Two options here, depending on the importance of ‘causality' between
> >> 2.6.x and 2.7.x lines.
> >> - Ship 2.7.2 as we voted on here
> >> - Pull these 16 tickets into 2.7.2 and roll a new RC
> >>
> >> What do people think? Do folks expect “any fix in 2.6.3 to be there in
> >> all releases that get out after 2.6.3 release date (December 16th)”?
> >>
> >> Thanks
> >> +Vinod
> >>
> >> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <
> vinodkv@apache.org
> >> <ma...@apache.org>> wrote:
> >>
> >> Sigh. Missed this.
> >>
> >> To retain causality ("any fix in 2.6.3 will be there in all releases
> that
> >> got out after 2.6.3”), I’ll get these patches in.
> >>
> >> Reverting my +1, and casting -1 for the RC myself.
> >>
> >> Will spin a new RC, this voting thread is marked dead.
> >>
> >> Thanks
> >> +Vinod
> >>
> >> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com<mailto:
> >> jdu@hortonworks.com>> wrote:
> >>
> >> However, when I look at our commit log and CHANGES.txt, I found
> something
> >> we are missing:
> >> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1
> tag.
> >> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
> >>
> >>
> >>
> >
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Sangjin Lee <sj...@apache.org>.
I agree that it would be a good practice to maintain parity between 2.6.x
and 2.7.x as much as possible. Departure from it should be more of an
exception than the norm.
That said, it is also true that we're not exactly following the semantic
versioning the moment we started to maintain multiple simultaneous release
branches. In semantic versioning, the timing of the release doesn't really
matter. If we were following semantic versioning, all releases in 2.6.x
would be considered "earlier versions" than 2.7.x regardless of their
release time. Obviously we cannot ensure no regression in that situation.
FWIW.
On Fri, Jan 8, 2016 at 11:43 AM, Andrew Wang <an...@cloudera.com>
wrote:
> I like monotonic releases since it's simple for users to understand. Is it
> difficult to backport to 2.7.x if you're already backporting to 2.6.x? I
> don't follow why special casing some class of fixes is desirable.
>
> Also for maintenance releases, aren't all included fixes supposed to be for
> serious bugs? Minor JIRAs can wait for the next minor release. If there are
> strong reasons to include a minor JIRA in a maintenance release, then maybe
> it's not really a minor JIRA.
>
> Best,
> Andrew
>
> On Fri, Jan 8, 2016 at 8:43 AM, Akira AJISAKA <aj...@oss.nttdata.co.jp>
> wrote:
>
> > The general rule sounds good to me.
> >
> > > "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that
> > get out after 2.x.y release date"
> >
> > +1
> >
> > > I would prefer this rule only applies on critical/blocker fixes, but
> not
> > applies on minor/trivial issues.
> >
> > +1
> >
> > Thanks,
> > Akira
> >
> >
> > On 12/29/15 23:50, Junping Du wrote:
> >
> >> I am +1 with pulling all of these tickets into 2.7.2.
> >>
> >> - For “any fix in 2.6.3 to be there in all releases that get out after
> >> 2.6.3 release date”
> >>
> >> Shall we conclude this as a general rule - "any fix in 2.x.y to be there
> >> in all 2.b.c releases (while b>=x) that get out after 2.x.y release
> date"?
> >> I am generally fine with this, but just feel it sounds to set too strong
> >> restrictions among branches. Some fixes could be trivial (test case fix,
> >> etc.) enough to deserve more flexibility. I would prefer this rule only
> >> applies on critical/blocker fixes, but not applies on minor/trivial
> issues.
> >>
> >> Just 2 cents.
> >>
> >>
> >> Thanks,
> >>
> >>
> >> Junping
> >>
> >>
> >> ________________________________
> >> From: Vinod Kumar Vavilapalli <vi...@apache.org>
> >> Sent: Thursday, December 24, 2015 12:47 AM
> >> To: Junping Du
> >> Cc: mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org;
> >> common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org
> >> Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
> >>
> >> I retract my -1. I think we will need to discuss this a bit more.
> >>
> >> Beyond those two tickets, there are a bunch more (totaling to 16) that
> >> are in 2.6.3 but *not* in 2.7.2. See this:
> >>
> https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0
> >> <
> >>
> https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0
> >> >
> >>
> >> Two options here, depending on the importance of ‘causality' between
> >> 2.6.x and 2.7.x lines.
> >> - Ship 2.7.2 as we voted on here
> >> - Pull these 16 tickets into 2.7.2 and roll a new RC
> >>
> >> What do people think? Do folks expect “any fix in 2.6.3 to be there in
> >> all releases that get out after 2.6.3 release date (December 16th)”?
> >>
> >> Thanks
> >> +Vinod
> >>
> >> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <
> vinodkv@apache.org
> >> <ma...@apache.org>> wrote:
> >>
> >> Sigh. Missed this.
> >>
> >> To retain causality ("any fix in 2.6.3 will be there in all releases
> that
> >> got out after 2.6.3”), I’ll get these patches in.
> >>
> >> Reverting my +1, and casting -1 for the RC myself.
> >>
> >> Will spin a new RC, this voting thread is marked dead.
> >>
> >> Thanks
> >> +Vinod
> >>
> >> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com<mailto:
> >> jdu@hortonworks.com>> wrote:
> >>
> >> However, when I look at our commit log and CHANGES.txt, I found
> something
> >> we are missing:
> >> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1
> tag.
> >> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
> >>
> >>
> >>
> >
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Sangjin Lee <sj...@apache.org>.
I agree that it would be a good practice to maintain parity between 2.6.x
and 2.7.x as much as possible. Departure from it should be more of an
exception than the norm.
That said, it is also true that we're not exactly following the semantic
versioning the moment we started to maintain multiple simultaneous release
branches. In semantic versioning, the timing of the release doesn't really
matter. If we were following semantic versioning, all releases in 2.6.x
would be considered "earlier versions" than 2.7.x regardless of their
release time. Obviously we cannot ensure no regression in that situation.
FWIW.
On Fri, Jan 8, 2016 at 11:43 AM, Andrew Wang <an...@cloudera.com>
wrote:
> I like monotonic releases since it's simple for users to understand. Is it
> difficult to backport to 2.7.x if you're already backporting to 2.6.x? I
> don't follow why special casing some class of fixes is desirable.
>
> Also for maintenance releases, aren't all included fixes supposed to be for
> serious bugs? Minor JIRAs can wait for the next minor release. If there are
> strong reasons to include a minor JIRA in a maintenance release, then maybe
> it's not really a minor JIRA.
>
> Best,
> Andrew
>
> On Fri, Jan 8, 2016 at 8:43 AM, Akira AJISAKA <aj...@oss.nttdata.co.jp>
> wrote:
>
> > The general rule sounds good to me.
> >
> > > "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that
> > get out after 2.x.y release date"
> >
> > +1
> >
> > > I would prefer this rule only applies on critical/blocker fixes, but
> not
> > applies on minor/trivial issues.
> >
> > +1
> >
> > Thanks,
> > Akira
> >
> >
> > On 12/29/15 23:50, Junping Du wrote:
> >
> >> I am +1 with pulling all of these tickets into 2.7.2.
> >>
> >> - For “any fix in 2.6.3 to be there in all releases that get out after
> >> 2.6.3 release date”
> >>
> >> Shall we conclude this as a general rule - "any fix in 2.x.y to be there
> >> in all 2.b.c releases (while b>=x) that get out after 2.x.y release
> date"?
> >> I am generally fine with this, but just feel it sounds to set too strong
> >> restrictions among branches. Some fixes could be trivial (test case fix,
> >> etc.) enough to deserve more flexibility. I would prefer this rule only
> >> applies on critical/blocker fixes, but not applies on minor/trivial
> issues.
> >>
> >> Just 2 cents.
> >>
> >>
> >> Thanks,
> >>
> >>
> >> Junping
> >>
> >>
> >> ________________________________
> >> From: Vinod Kumar Vavilapalli <vi...@apache.org>
> >> Sent: Thursday, December 24, 2015 12:47 AM
> >> To: Junping Du
> >> Cc: mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org;
> >> common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org
> >> Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
> >>
> >> I retract my -1. I think we will need to discuss this a bit more.
> >>
> >> Beyond those two tickets, there are a bunch more (totaling to 16) that
> >> are in 2.6.3 but *not* in 2.7.2. See this:
> >>
> https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0
> >> <
> >>
> https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0
> >> >
> >>
> >> Two options here, depending on the importance of ‘causality' between
> >> 2.6.x and 2.7.x lines.
> >> - Ship 2.7.2 as we voted on here
> >> - Pull these 16 tickets into 2.7.2 and roll a new RC
> >>
> >> What do people think? Do folks expect “any fix in 2.6.3 to be there in
> >> all releases that get out after 2.6.3 release date (December 16th)”?
> >>
> >> Thanks
> >> +Vinod
> >>
> >> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <
> vinodkv@apache.org
> >> <ma...@apache.org>> wrote:
> >>
> >> Sigh. Missed this.
> >>
> >> To retain causality ("any fix in 2.6.3 will be there in all releases
> that
> >> got out after 2.6.3”), I’ll get these patches in.
> >>
> >> Reverting my +1, and casting -1 for the RC myself.
> >>
> >> Will spin a new RC, this voting thread is marked dead.
> >>
> >> Thanks
> >> +Vinod
> >>
> >> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com<mailto:
> >> jdu@hortonworks.com>> wrote:
> >>
> >> However, when I look at our commit log and CHANGES.txt, I found
> something
> >> we are missing:
> >> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1
> tag.
> >> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
> >>
> >>
> >>
> >
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Junping Du <jd...@hortonworks.com>.
bq. Is it difficult to backport to 2.7.x if you're already backporting to 2.6.x? I don't follow why special casing some class of fixes is desirable.
It is not difficult to backport the commits between 2.6.x and 2.7.x. However, it do *difficult* to track exactly for hundreds of commits between them. Taking HDFS-9470 as an example, the committer totally forget to merge the commit into 2.7.2 when it is resolved as fixed in 2.7.2. The commit was merged into 2.6.3 later but get missed on 2.7.2 RC1. If this is not a critical fix, I don't think 2.7.2 should get a new RC to wait this commit to land on. That's why classifying on priority of fixes are important and desirable when we are facing this situation.
bq. Also for maintenance releases, aren't all included fixes supposed to be for serious bugs? Minor JIRAs can wait for the next minor release. If there are strong reasons to include a minor JIRA in a maintenance release, then maybe it's not really a minor JIRA.
If a committer commit a major/minor priority patch on a maintenance release, what RM should do? Revert it or upgrade the priority to critical even it doesn't belong to critical?
I believe only commit critical/blocker patch to maintenance release can only be a general guideline for maintenance release, but not a strict rule for all committers in practice. RMs should obey this guideline strictly in cherry-pick commits but there are more commits get committed by other committers. The committer choose the fixed branch not only by priority but also by target branch proposed by patch contributor who may only work on that branch release for a long time. I think this target/fix branch negotiation mechanism going on well and we shouldn't break it.
Thanks,
Junping
________________________________________
From: Andrew Wang <an...@cloudera.com>
Sent: Friday, January 08, 2016 7:43 PM
To: common-dev@hadoop.apache.org
Cc: mapreduce-dev@hadoop.apache.org; Vinod Kumar Vavilapalli; yarn-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org
Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
I like monotonic releases since it's simple for users to understand. Is it
difficult to backport to 2.7.x if you're already backporting to 2.6.x? I
don't follow why special casing some class of fixes is desirable.
Also for maintenance releases, aren't all included fixes supposed to be for
serious bugs? Minor JIRAs can wait for the next minor release. If there are
strong reasons to include a minor JIRA in a maintenance release, then maybe
it's not really a minor JIRA.
Best,
Andrew
On Fri, Jan 8, 2016 at 8:43 AM, Akira AJISAKA <aj...@oss.nttdata.co.jp>
wrote:
> The general rule sounds good to me.
>
> > "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that
> get out after 2.x.y release date"
>
> +1
>
> > I would prefer this rule only applies on critical/blocker fixes, but not
> applies on minor/trivial issues.
>
> +1
>
> Thanks,
> Akira
>
>
> On 12/29/15 23:50, Junping Du wrote:
>
>> I am +1 with pulling all of these tickets into 2.7.2.
>>
>> - For “any fix in 2.6.3 to be there in all releases that get out after
>> 2.6.3 release date”
>>
>> Shall we conclude this as a general rule - "any fix in 2.x.y to be there
>> in all 2.b.c releases (while b>=x) that get out after 2.x.y release date"?
>> I am generally fine with this, but just feel it sounds to set too strong
>> restrictions among branches. Some fixes could be trivial (test case fix,
>> etc.) enough to deserve more flexibility. I would prefer this rule only
>> applies on critical/blocker fixes, but not applies on minor/trivial issues.
>>
>> Just 2 cents.
>>
>>
>> Thanks,
>>
>>
>> Junping
>>
>>
>> ________________________________
>> From: Vinod Kumar Vavilapalli <vi...@apache.org>
>> Sent: Thursday, December 24, 2015 12:47 AM
>> To: Junping Du
>> Cc: mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org;
>> common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org
>> Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
>>
>> I retract my -1. I think we will need to discuss this a bit more.
>>
>> Beyond those two tickets, there are a bunch more (totaling to 16) that
>> are in 2.6.3 but *not* in 2.7.2. See this:
>> https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0
>> <
>> https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0
>> >
>>
>> Two options here, depending on the importance of ‘causality' between
>> 2.6.x and 2.7.x lines.
>> - Ship 2.7.2 as we voted on here
>> - Pull these 16 tickets into 2.7.2 and roll a new RC
>>
>> What do people think? Do folks expect “any fix in 2.6.3 to be there in
>> all releases that get out after 2.6.3 release date (December 16th)”?
>>
>> Thanks
>> +Vinod
>>
>> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vinodkv@apache.org
>> <ma...@apache.org>> wrote:
>>
>> Sigh. Missed this.
>>
>> To retain causality ("any fix in 2.6.3 will be there in all releases that
>> got out after 2.6.3”), I’ll get these patches in.
>>
>> Reverting my +1, and casting -1 for the RC myself.
>>
>> Will spin a new RC, this voting thread is marked dead.
>>
>> Thanks
>> +Vinod
>>
>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com<mailto:
>> jdu@hortonworks.com>> wrote:
>>
>> However, when I look at our commit log and CHANGES.txt, I found something
>> we are missing:
>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>>
>>
>>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Junping Du <jd...@hortonworks.com>.
bq. Is it difficult to backport to 2.7.x if you're already backporting to 2.6.x? I don't follow why special casing some class of fixes is desirable.
It is not difficult to backport the commits between 2.6.x and 2.7.x. However, it do *difficult* to track exactly for hundreds of commits between them. Taking HDFS-9470 as an example, the committer totally forget to merge the commit into 2.7.2 when it is resolved as fixed in 2.7.2. The commit was merged into 2.6.3 later but get missed on 2.7.2 RC1. If this is not a critical fix, I don't think 2.7.2 should get a new RC to wait this commit to land on. That's why classifying on priority of fixes are important and desirable when we are facing this situation.
bq. Also for maintenance releases, aren't all included fixes supposed to be for serious bugs? Minor JIRAs can wait for the next minor release. If there are strong reasons to include a minor JIRA in a maintenance release, then maybe it's not really a minor JIRA.
If a committer commit a major/minor priority patch on a maintenance release, what RM should do? Revert it or upgrade the priority to critical even it doesn't belong to critical?
I believe only commit critical/blocker patch to maintenance release can only be a general guideline for maintenance release, but not a strict rule for all committers in practice. RMs should obey this guideline strictly in cherry-pick commits but there are more commits get committed by other committers. The committer choose the fixed branch not only by priority but also by target branch proposed by patch contributor who may only work on that branch release for a long time. I think this target/fix branch negotiation mechanism going on well and we shouldn't break it.
Thanks,
Junping
________________________________________
From: Andrew Wang <an...@cloudera.com>
Sent: Friday, January 08, 2016 7:43 PM
To: common-dev@hadoop.apache.org
Cc: mapreduce-dev@hadoop.apache.org; Vinod Kumar Vavilapalli; yarn-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org
Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
I like monotonic releases since it's simple for users to understand. Is it
difficult to backport to 2.7.x if you're already backporting to 2.6.x? I
don't follow why special casing some class of fixes is desirable.
Also for maintenance releases, aren't all included fixes supposed to be for
serious bugs? Minor JIRAs can wait for the next minor release. If there are
strong reasons to include a minor JIRA in a maintenance release, then maybe
it's not really a minor JIRA.
Best,
Andrew
On Fri, Jan 8, 2016 at 8:43 AM, Akira AJISAKA <aj...@oss.nttdata.co.jp>
wrote:
> The general rule sounds good to me.
>
> > "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that
> get out after 2.x.y release date"
>
> +1
>
> > I would prefer this rule only applies on critical/blocker fixes, but not
> applies on minor/trivial issues.
>
> +1
>
> Thanks,
> Akira
>
>
> On 12/29/15 23:50, Junping Du wrote:
>
>> I am +1 with pulling all of these tickets into 2.7.2.
>>
>> - For “any fix in 2.6.3 to be there in all releases that get out after
>> 2.6.3 release date”
>>
>> Shall we conclude this as a general rule - "any fix in 2.x.y to be there
>> in all 2.b.c releases (while b>=x) that get out after 2.x.y release date"?
>> I am generally fine with this, but just feel it sounds to set too strong
>> restrictions among branches. Some fixes could be trivial (test case fix,
>> etc.) enough to deserve more flexibility. I would prefer this rule only
>> applies on critical/blocker fixes, but not applies on minor/trivial issues.
>>
>> Just 2 cents.
>>
>>
>> Thanks,
>>
>>
>> Junping
>>
>>
>> ________________________________
>> From: Vinod Kumar Vavilapalli <vi...@apache.org>
>> Sent: Thursday, December 24, 2015 12:47 AM
>> To: Junping Du
>> Cc: mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org;
>> common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org
>> Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
>>
>> I retract my -1. I think we will need to discuss this a bit more.
>>
>> Beyond those two tickets, there are a bunch more (totaling to 16) that
>> are in 2.6.3 but *not* in 2.7.2. See this:
>> https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0
>> <
>> https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0
>> >
>>
>> Two options here, depending on the importance of ‘causality' between
>> 2.6.x and 2.7.x lines.
>> - Ship 2.7.2 as we voted on here
>> - Pull these 16 tickets into 2.7.2 and roll a new RC
>>
>> What do people think? Do folks expect “any fix in 2.6.3 to be there in
>> all releases that get out after 2.6.3 release date (December 16th)”?
>>
>> Thanks
>> +Vinod
>>
>> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vinodkv@apache.org
>> <ma...@apache.org>> wrote:
>>
>> Sigh. Missed this.
>>
>> To retain causality ("any fix in 2.6.3 will be there in all releases that
>> got out after 2.6.3”), I’ll get these patches in.
>>
>> Reverting my +1, and casting -1 for the RC myself.
>>
>> Will spin a new RC, this voting thread is marked dead.
>>
>> Thanks
>> +Vinod
>>
>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com<mailto:
>> jdu@hortonworks.com>> wrote:
>>
>> However, when I look at our commit log and CHANGES.txt, I found something
>> we are missing:
>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>>
>>
>>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Junping Du <jd...@hortonworks.com>.
bq. Is it difficult to backport to 2.7.x if you're already backporting to 2.6.x? I don't follow why special casing some class of fixes is desirable.
It is not difficult to backport the commits between 2.6.x and 2.7.x. However, it do *difficult* to track exactly for hundreds of commits between them. Taking HDFS-9470 as an example, the committer totally forget to merge the commit into 2.7.2 when it is resolved as fixed in 2.7.2. The commit was merged into 2.6.3 later but get missed on 2.7.2 RC1. If this is not a critical fix, I don't think 2.7.2 should get a new RC to wait this commit to land on. That's why classifying on priority of fixes are important and desirable when we are facing this situation.
bq. Also for maintenance releases, aren't all included fixes supposed to be for serious bugs? Minor JIRAs can wait for the next minor release. If there are strong reasons to include a minor JIRA in a maintenance release, then maybe it's not really a minor JIRA.
If a committer commit a major/minor priority patch on a maintenance release, what RM should do? Revert it or upgrade the priority to critical even it doesn't belong to critical?
I believe only commit critical/blocker patch to maintenance release can only be a general guideline for maintenance release, but not a strict rule for all committers in practice. RMs should obey this guideline strictly in cherry-pick commits but there are more commits get committed by other committers. The committer choose the fixed branch not only by priority but also by target branch proposed by patch contributor who may only work on that branch release for a long time. I think this target/fix branch negotiation mechanism going on well and we shouldn't break it.
Thanks,
Junping
________________________________________
From: Andrew Wang <an...@cloudera.com>
Sent: Friday, January 08, 2016 7:43 PM
To: common-dev@hadoop.apache.org
Cc: mapreduce-dev@hadoop.apache.org; Vinod Kumar Vavilapalli; yarn-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org
Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
I like monotonic releases since it's simple for users to understand. Is it
difficult to backport to 2.7.x if you're already backporting to 2.6.x? I
don't follow why special casing some class of fixes is desirable.
Also for maintenance releases, aren't all included fixes supposed to be for
serious bugs? Minor JIRAs can wait for the next minor release. If there are
strong reasons to include a minor JIRA in a maintenance release, then maybe
it's not really a minor JIRA.
Best,
Andrew
On Fri, Jan 8, 2016 at 8:43 AM, Akira AJISAKA <aj...@oss.nttdata.co.jp>
wrote:
> The general rule sounds good to me.
>
> > "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that
> get out after 2.x.y release date"
>
> +1
>
> > I would prefer this rule only applies on critical/blocker fixes, but not
> applies on minor/trivial issues.
>
> +1
>
> Thanks,
> Akira
>
>
> On 12/29/15 23:50, Junping Du wrote:
>
>> I am +1 with pulling all of these tickets into 2.7.2.
>>
>> - For “any fix in 2.6.3 to be there in all releases that get out after
>> 2.6.3 release date”
>>
>> Shall we conclude this as a general rule - "any fix in 2.x.y to be there
>> in all 2.b.c releases (while b>=x) that get out after 2.x.y release date"?
>> I am generally fine with this, but just feel it sounds to set too strong
>> restrictions among branches. Some fixes could be trivial (test case fix,
>> etc.) enough to deserve more flexibility. I would prefer this rule only
>> applies on critical/blocker fixes, but not applies on minor/trivial issues.
>>
>> Just 2 cents.
>>
>>
>> Thanks,
>>
>>
>> Junping
>>
>>
>> ________________________________
>> From: Vinod Kumar Vavilapalli <vi...@apache.org>
>> Sent: Thursday, December 24, 2015 12:47 AM
>> To: Junping Du
>> Cc: mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org;
>> common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org
>> Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
>>
>> I retract my -1. I think we will need to discuss this a bit more.
>>
>> Beyond those two tickets, there are a bunch more (totaling to 16) that
>> are in 2.6.3 but *not* in 2.7.2. See this:
>> https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0
>> <
>> https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0
>> >
>>
>> Two options here, depending on the importance of ‘causality' between
>> 2.6.x and 2.7.x lines.
>> - Ship 2.7.2 as we voted on here
>> - Pull these 16 tickets into 2.7.2 and roll a new RC
>>
>> What do people think? Do folks expect “any fix in 2.6.3 to be there in
>> all releases that get out after 2.6.3 release date (December 16th)”?
>>
>> Thanks
>> +Vinod
>>
>> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vinodkv@apache.org
>> <ma...@apache.org>> wrote:
>>
>> Sigh. Missed this.
>>
>> To retain causality ("any fix in 2.6.3 will be there in all releases that
>> got out after 2.6.3”), I’ll get these patches in.
>>
>> Reverting my +1, and casting -1 for the RC myself.
>>
>> Will spin a new RC, this voting thread is marked dead.
>>
>> Thanks
>> +Vinod
>>
>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com<mailto:
>> jdu@hortonworks.com>> wrote:
>>
>> However, when I look at our commit log and CHANGES.txt, I found something
>> we are missing:
>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>>
>>
>>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Junping Du <jd...@hortonworks.com>.
bq. Is it difficult to backport to 2.7.x if you're already backporting to 2.6.x? I don't follow why special casing some class of fixes is desirable.
It is not difficult to backport the commits between 2.6.x and 2.7.x. However, it do *difficult* to track exactly for hundreds of commits between them. Taking HDFS-9470 as an example, the committer totally forget to merge the commit into 2.7.2 when it is resolved as fixed in 2.7.2. The commit was merged into 2.6.3 later but get missed on 2.7.2 RC1. If this is not a critical fix, I don't think 2.7.2 should get a new RC to wait this commit to land on. That's why classifying on priority of fixes are important and desirable when we are facing this situation.
bq. Also for maintenance releases, aren't all included fixes supposed to be for serious bugs? Minor JIRAs can wait for the next minor release. If there are strong reasons to include a minor JIRA in a maintenance release, then maybe it's not really a minor JIRA.
If a committer commit a major/minor priority patch on a maintenance release, what RM should do? Revert it or upgrade the priority to critical even it doesn't belong to critical?
I believe only commit critical/blocker patch to maintenance release can only be a general guideline for maintenance release, but not a strict rule for all committers in practice. RMs should obey this guideline strictly in cherry-pick commits but there are more commits get committed by other committers. The committer choose the fixed branch not only by priority but also by target branch proposed by patch contributor who may only work on that branch release for a long time. I think this target/fix branch negotiation mechanism going on well and we shouldn't break it.
Thanks,
Junping
________________________________________
From: Andrew Wang <an...@cloudera.com>
Sent: Friday, January 08, 2016 7:43 PM
To: common-dev@hadoop.apache.org
Cc: mapreduce-dev@hadoop.apache.org; Vinod Kumar Vavilapalli; yarn-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org
Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
I like monotonic releases since it's simple for users to understand. Is it
difficult to backport to 2.7.x if you're already backporting to 2.6.x? I
don't follow why special casing some class of fixes is desirable.
Also for maintenance releases, aren't all included fixes supposed to be for
serious bugs? Minor JIRAs can wait for the next minor release. If there are
strong reasons to include a minor JIRA in a maintenance release, then maybe
it's not really a minor JIRA.
Best,
Andrew
On Fri, Jan 8, 2016 at 8:43 AM, Akira AJISAKA <aj...@oss.nttdata.co.jp>
wrote:
> The general rule sounds good to me.
>
> > "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that
> get out after 2.x.y release date"
>
> +1
>
> > I would prefer this rule only applies on critical/blocker fixes, but not
> applies on minor/trivial issues.
>
> +1
>
> Thanks,
> Akira
>
>
> On 12/29/15 23:50, Junping Du wrote:
>
>> I am +1 with pulling all of these tickets into 2.7.2.
>>
>> - For “any fix in 2.6.3 to be there in all releases that get out after
>> 2.6.3 release date”
>>
>> Shall we conclude this as a general rule - "any fix in 2.x.y to be there
>> in all 2.b.c releases (while b>=x) that get out after 2.x.y release date"?
>> I am generally fine with this, but just feel it sounds to set too strong
>> restrictions among branches. Some fixes could be trivial (test case fix,
>> etc.) enough to deserve more flexibility. I would prefer this rule only
>> applies on critical/blocker fixes, but not applies on minor/trivial issues.
>>
>> Just 2 cents.
>>
>>
>> Thanks,
>>
>>
>> Junping
>>
>>
>> ________________________________
>> From: Vinod Kumar Vavilapalli <vi...@apache.org>
>> Sent: Thursday, December 24, 2015 12:47 AM
>> To: Junping Du
>> Cc: mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org;
>> common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org
>> Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
>>
>> I retract my -1. I think we will need to discuss this a bit more.
>>
>> Beyond those two tickets, there are a bunch more (totaling to 16) that
>> are in 2.6.3 but *not* in 2.7.2. See this:
>> https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0
>> <
>> https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0
>> >
>>
>> Two options here, depending on the importance of ‘causality' between
>> 2.6.x and 2.7.x lines.
>> - Ship 2.7.2 as we voted on here
>> - Pull these 16 tickets into 2.7.2 and roll a new RC
>>
>> What do people think? Do folks expect “any fix in 2.6.3 to be there in
>> all releases that get out after 2.6.3 release date (December 16th)”?
>>
>> Thanks
>> +Vinod
>>
>> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vinodkv@apache.org
>> <ma...@apache.org>> wrote:
>>
>> Sigh. Missed this.
>>
>> To retain causality ("any fix in 2.6.3 will be there in all releases that
>> got out after 2.6.3”), I’ll get these patches in.
>>
>> Reverting my +1, and casting -1 for the RC myself.
>>
>> Will spin a new RC, this voting thread is marked dead.
>>
>> Thanks
>> +Vinod
>>
>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com<mailto:
>> jdu@hortonworks.com>> wrote:
>>
>> However, when I look at our commit log and CHANGES.txt, I found something
>> we are missing:
>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>>
>>
>>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Andrew Wang <an...@cloudera.com>.
I like monotonic releases since it's simple for users to understand. Is it
difficult to backport to 2.7.x if you're already backporting to 2.6.x? I
don't follow why special casing some class of fixes is desirable.
Also for maintenance releases, aren't all included fixes supposed to be for
serious bugs? Minor JIRAs can wait for the next minor release. If there are
strong reasons to include a minor JIRA in a maintenance release, then maybe
it's not really a minor JIRA.
Best,
Andrew
On Fri, Jan 8, 2016 at 8:43 AM, Akira AJISAKA <aj...@oss.nttdata.co.jp>
wrote:
> The general rule sounds good to me.
>
> > "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that
> get out after 2.x.y release date"
>
> +1
>
> > I would prefer this rule only applies on critical/blocker fixes, but not
> applies on minor/trivial issues.
>
> +1
>
> Thanks,
> Akira
>
>
> On 12/29/15 23:50, Junping Du wrote:
>
>> I am +1 with pulling all of these tickets into 2.7.2.
>>
>> - For “any fix in 2.6.3 to be there in all releases that get out after
>> 2.6.3 release date”
>>
>> Shall we conclude this as a general rule - "any fix in 2.x.y to be there
>> in all 2.b.c releases (while b>=x) that get out after 2.x.y release date"?
>> I am generally fine with this, but just feel it sounds to set too strong
>> restrictions among branches. Some fixes could be trivial (test case fix,
>> etc.) enough to deserve more flexibility. I would prefer this rule only
>> applies on critical/blocker fixes, but not applies on minor/trivial issues.
>>
>> Just 2 cents.
>>
>>
>> Thanks,
>>
>>
>> Junping
>>
>>
>> ________________________________
>> From: Vinod Kumar Vavilapalli <vi...@apache.org>
>> Sent: Thursday, December 24, 2015 12:47 AM
>> To: Junping Du
>> Cc: mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org;
>> common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org
>> Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
>>
>> I retract my -1. I think we will need to discuss this a bit more.
>>
>> Beyond those two tickets, there are a bunch more (totaling to 16) that
>> are in 2.6.3 but *not* in 2.7.2. See this:
>> https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0
>> <
>> https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0
>> >
>>
>> Two options here, depending on the importance of ‘causality' between
>> 2.6.x and 2.7.x lines.
>> - Ship 2.7.2 as we voted on here
>> - Pull these 16 tickets into 2.7.2 and roll a new RC
>>
>> What do people think? Do folks expect “any fix in 2.6.3 to be there in
>> all releases that get out after 2.6.3 release date (December 16th)”?
>>
>> Thanks
>> +Vinod
>>
>> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vinodkv@apache.org
>> <ma...@apache.org>> wrote:
>>
>> Sigh. Missed this.
>>
>> To retain causality ("any fix in 2.6.3 will be there in all releases that
>> got out after 2.6.3”), I’ll get these patches in.
>>
>> Reverting my +1, and casting -1 for the RC myself.
>>
>> Will spin a new RC, this voting thread is marked dead.
>>
>> Thanks
>> +Vinod
>>
>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com<mailto:
>> jdu@hortonworks.com>> wrote:
>>
>> However, when I look at our commit log and CHANGES.txt, I found something
>> we are missing:
>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>>
>>
>>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Andrew Wang <an...@cloudera.com>.
I like monotonic releases since it's simple for users to understand. Is it
difficult to backport to 2.7.x if you're already backporting to 2.6.x? I
don't follow why special casing some class of fixes is desirable.
Also for maintenance releases, aren't all included fixes supposed to be for
serious bugs? Minor JIRAs can wait for the next minor release. If there are
strong reasons to include a minor JIRA in a maintenance release, then maybe
it's not really a minor JIRA.
Best,
Andrew
On Fri, Jan 8, 2016 at 8:43 AM, Akira AJISAKA <aj...@oss.nttdata.co.jp>
wrote:
> The general rule sounds good to me.
>
> > "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that
> get out after 2.x.y release date"
>
> +1
>
> > I would prefer this rule only applies on critical/blocker fixes, but not
> applies on minor/trivial issues.
>
> +1
>
> Thanks,
> Akira
>
>
> On 12/29/15 23:50, Junping Du wrote:
>
>> I am +1 with pulling all of these tickets into 2.7.2.
>>
>> - For “any fix in 2.6.3 to be there in all releases that get out after
>> 2.6.3 release date”
>>
>> Shall we conclude this as a general rule - "any fix in 2.x.y to be there
>> in all 2.b.c releases (while b>=x) that get out after 2.x.y release date"?
>> I am generally fine with this, but just feel it sounds to set too strong
>> restrictions among branches. Some fixes could be trivial (test case fix,
>> etc.) enough to deserve more flexibility. I would prefer this rule only
>> applies on critical/blocker fixes, but not applies on minor/trivial issues.
>>
>> Just 2 cents.
>>
>>
>> Thanks,
>>
>>
>> Junping
>>
>>
>> ________________________________
>> From: Vinod Kumar Vavilapalli <vi...@apache.org>
>> Sent: Thursday, December 24, 2015 12:47 AM
>> To: Junping Du
>> Cc: mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org;
>> common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org
>> Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
>>
>> I retract my -1. I think we will need to discuss this a bit more.
>>
>> Beyond those two tickets, there are a bunch more (totaling to 16) that
>> are in 2.6.3 but *not* in 2.7.2. See this:
>> https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0
>> <
>> https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0
>> >
>>
>> Two options here, depending on the importance of ‘causality' between
>> 2.6.x and 2.7.x lines.
>> - Ship 2.7.2 as we voted on here
>> - Pull these 16 tickets into 2.7.2 and roll a new RC
>>
>> What do people think? Do folks expect “any fix in 2.6.3 to be there in
>> all releases that get out after 2.6.3 release date (December 16th)”?
>>
>> Thanks
>> +Vinod
>>
>> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vinodkv@apache.org
>> <ma...@apache.org>> wrote:
>>
>> Sigh. Missed this.
>>
>> To retain causality ("any fix in 2.6.3 will be there in all releases that
>> got out after 2.6.3”), I’ll get these patches in.
>>
>> Reverting my +1, and casting -1 for the RC myself.
>>
>> Will spin a new RC, this voting thread is marked dead.
>>
>> Thanks
>> +Vinod
>>
>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com<mailto:
>> jdu@hortonworks.com>> wrote:
>>
>> However, when I look at our commit log and CHANGES.txt, I found something
>> we are missing:
>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>>
>>
>>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Andrew Wang <an...@cloudera.com>.
I like monotonic releases since it's simple for users to understand. Is it
difficult to backport to 2.7.x if you're already backporting to 2.6.x? I
don't follow why special casing some class of fixes is desirable.
Also for maintenance releases, aren't all included fixes supposed to be for
serious bugs? Minor JIRAs can wait for the next minor release. If there are
strong reasons to include a minor JIRA in a maintenance release, then maybe
it's not really a minor JIRA.
Best,
Andrew
On Fri, Jan 8, 2016 at 8:43 AM, Akira AJISAKA <aj...@oss.nttdata.co.jp>
wrote:
> The general rule sounds good to me.
>
> > "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that
> get out after 2.x.y release date"
>
> +1
>
> > I would prefer this rule only applies on critical/blocker fixes, but not
> applies on minor/trivial issues.
>
> +1
>
> Thanks,
> Akira
>
>
> On 12/29/15 23:50, Junping Du wrote:
>
>> I am +1 with pulling all of these tickets into 2.7.2.
>>
>> - For “any fix in 2.6.3 to be there in all releases that get out after
>> 2.6.3 release date”
>>
>> Shall we conclude this as a general rule - "any fix in 2.x.y to be there
>> in all 2.b.c releases (while b>=x) that get out after 2.x.y release date"?
>> I am generally fine with this, but just feel it sounds to set too strong
>> restrictions among branches. Some fixes could be trivial (test case fix,
>> etc.) enough to deserve more flexibility. I would prefer this rule only
>> applies on critical/blocker fixes, but not applies on minor/trivial issues.
>>
>> Just 2 cents.
>>
>>
>> Thanks,
>>
>>
>> Junping
>>
>>
>> ________________________________
>> From: Vinod Kumar Vavilapalli <vi...@apache.org>
>> Sent: Thursday, December 24, 2015 12:47 AM
>> To: Junping Du
>> Cc: mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org;
>> common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org
>> Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
>>
>> I retract my -1. I think we will need to discuss this a bit more.
>>
>> Beyond those two tickets, there are a bunch more (totaling to 16) that
>> are in 2.6.3 but *not* in 2.7.2. See this:
>> https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0
>> <
>> https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0
>> >
>>
>> Two options here, depending on the importance of ‘causality' between
>> 2.6.x and 2.7.x lines.
>> - Ship 2.7.2 as we voted on here
>> - Pull these 16 tickets into 2.7.2 and roll a new RC
>>
>> What do people think? Do folks expect “any fix in 2.6.3 to be there in
>> all releases that get out after 2.6.3 release date (December 16th)”?
>>
>> Thanks
>> +Vinod
>>
>> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vinodkv@apache.org
>> <ma...@apache.org>> wrote:
>>
>> Sigh. Missed this.
>>
>> To retain causality ("any fix in 2.6.3 will be there in all releases that
>> got out after 2.6.3”), I’ll get these patches in.
>>
>> Reverting my +1, and casting -1 for the RC myself.
>>
>> Will spin a new RC, this voting thread is marked dead.
>>
>> Thanks
>> +Vinod
>>
>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com<mailto:
>> jdu@hortonworks.com>> wrote:
>>
>> However, when I look at our commit log and CHANGES.txt, I found something
>> we are missing:
>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>>
>>
>>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Andrew Wang <an...@cloudera.com>.
I like monotonic releases since it's simple for users to understand. Is it
difficult to backport to 2.7.x if you're already backporting to 2.6.x? I
don't follow why special casing some class of fixes is desirable.
Also for maintenance releases, aren't all included fixes supposed to be for
serious bugs? Minor JIRAs can wait for the next minor release. If there are
strong reasons to include a minor JIRA in a maintenance release, then maybe
it's not really a minor JIRA.
Best,
Andrew
On Fri, Jan 8, 2016 at 8:43 AM, Akira AJISAKA <aj...@oss.nttdata.co.jp>
wrote:
> The general rule sounds good to me.
>
> > "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that
> get out after 2.x.y release date"
>
> +1
>
> > I would prefer this rule only applies on critical/blocker fixes, but not
> applies on minor/trivial issues.
>
> +1
>
> Thanks,
> Akira
>
>
> On 12/29/15 23:50, Junping Du wrote:
>
>> I am +1 with pulling all of these tickets into 2.7.2.
>>
>> - For “any fix in 2.6.3 to be there in all releases that get out after
>> 2.6.3 release date”
>>
>> Shall we conclude this as a general rule - "any fix in 2.x.y to be there
>> in all 2.b.c releases (while b>=x) that get out after 2.x.y release date"?
>> I am generally fine with this, but just feel it sounds to set too strong
>> restrictions among branches. Some fixes could be trivial (test case fix,
>> etc.) enough to deserve more flexibility. I would prefer this rule only
>> applies on critical/blocker fixes, but not applies on minor/trivial issues.
>>
>> Just 2 cents.
>>
>>
>> Thanks,
>>
>>
>> Junping
>>
>>
>> ________________________________
>> From: Vinod Kumar Vavilapalli <vi...@apache.org>
>> Sent: Thursday, December 24, 2015 12:47 AM
>> To: Junping Du
>> Cc: mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org;
>> common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org
>> Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
>>
>> I retract my -1. I think we will need to discuss this a bit more.
>>
>> Beyond those two tickets, there are a bunch more (totaling to 16) that
>> are in 2.6.3 but *not* in 2.7.2. See this:
>> https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0
>> <
>> https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0
>> >
>>
>> Two options here, depending on the importance of ‘causality' between
>> 2.6.x and 2.7.x lines.
>> - Ship 2.7.2 as we voted on here
>> - Pull these 16 tickets into 2.7.2 and roll a new RC
>>
>> What do people think? Do folks expect “any fix in 2.6.3 to be there in
>> all releases that get out after 2.6.3 release date (December 16th)”?
>>
>> Thanks
>> +Vinod
>>
>> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vinodkv@apache.org
>> <ma...@apache.org>> wrote:
>>
>> Sigh. Missed this.
>>
>> To retain causality ("any fix in 2.6.3 will be there in all releases that
>> got out after 2.6.3”), I’ll get these patches in.
>>
>> Reverting my +1, and casting -1 for the RC myself.
>>
>> Will spin a new RC, this voting thread is marked dead.
>>
>> Thanks
>> +Vinod
>>
>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com<mailto:
>> jdu@hortonworks.com>> wrote:
>>
>> However, when I look at our commit log and CHANGES.txt, I found something
>> we are missing:
>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>>
>>
>>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Akira AJISAKA <aj...@oss.nttdata.co.jp>.
The general rule sounds good to me.
> "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that
get out after 2.x.y release date"
+1
> I would prefer this rule only applies on critical/blocker fixes, but
not applies on minor/trivial issues.
+1
Thanks,
Akira
On 12/29/15 23:50, Junping Du wrote:
> I am +1 with pulling all of these tickets into 2.7.2.
>
> - For “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date”
>
> Shall we conclude this as a general rule - "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that get out after 2.x.y release date"? I am generally fine with this, but just feel it sounds to set too strong restrictions among branches. Some fixes could be trivial (test case fix, etc.) enough to deserve more flexibility. I would prefer this rule only applies on critical/blocker fixes, but not applies on minor/trivial issues.
>
> Just 2 cents.
>
>
> Thanks,
>
>
> Junping
>
>
> ________________________________
> From: Vinod Kumar Vavilapalli <vi...@apache.org>
> Sent: Thursday, December 24, 2015 12:47 AM
> To: Junping Du
> Cc: mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org
> Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
>
> I retract my -1. I think we will need to discuss this a bit more.
>
> Beyond those two tickets, there are a bunch more (totaling to 16) that are in 2.6.3 but *not* in 2.7.2. See this: https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0<https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0>
>
> Two options here, depending on the importance of ‘causality' between 2.6.x and 2.7.x lines.
> - Ship 2.7.2 as we voted on here
> - Pull these 16 tickets into 2.7.2 and roll a new RC
>
> What do people think? Do folks expect “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date (December 16th)”?
>
> Thanks
> +Vinod
>
> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vi...@apache.org>> wrote:
>
> Sigh. Missed this.
>
> To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in.
>
> Reverting my +1, and casting -1 for the RC myself.
>
> Will spin a new RC, this voting thread is marked dead.
>
> Thanks
> +Vinod
>
> On Dec 22, 2015, at 8:24 AM, Junping Du <jd...@hortonworks.com>> wrote:
>
> However, when I look at our commit log and CHANGES.txt, I found something we are missing:
> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Akira AJISAKA <aj...@oss.nttdata.co.jp>.
The general rule sounds good to me.
> "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that
get out after 2.x.y release date"
+1
> I would prefer this rule only applies on critical/blocker fixes, but
not applies on minor/trivial issues.
+1
Thanks,
Akira
On 12/29/15 23:50, Junping Du wrote:
> I am +1 with pulling all of these tickets into 2.7.2.
>
> - For “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date”
>
> Shall we conclude this as a general rule - "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that get out after 2.x.y release date"? I am generally fine with this, but just feel it sounds to set too strong restrictions among branches. Some fixes could be trivial (test case fix, etc.) enough to deserve more flexibility. I would prefer this rule only applies on critical/blocker fixes, but not applies on minor/trivial issues.
>
> Just 2 cents.
>
>
> Thanks,
>
>
> Junping
>
>
> ________________________________
> From: Vinod Kumar Vavilapalli <vi...@apache.org>
> Sent: Thursday, December 24, 2015 12:47 AM
> To: Junping Du
> Cc: mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org
> Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
>
> I retract my -1. I think we will need to discuss this a bit more.
>
> Beyond those two tickets, there are a bunch more (totaling to 16) that are in 2.6.3 but *not* in 2.7.2. See this: https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0<https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0>
>
> Two options here, depending on the importance of ‘causality' between 2.6.x and 2.7.x lines.
> - Ship 2.7.2 as we voted on here
> - Pull these 16 tickets into 2.7.2 and roll a new RC
>
> What do people think? Do folks expect “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date (December 16th)”?
>
> Thanks
> +Vinod
>
> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vi...@apache.org>> wrote:
>
> Sigh. Missed this.
>
> To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in.
>
> Reverting my +1, and casting -1 for the RC myself.
>
> Will spin a new RC, this voting thread is marked dead.
>
> Thanks
> +Vinod
>
> On Dec 22, 2015, at 8:24 AM, Junping Du <jd...@hortonworks.com>> wrote:
>
> However, when I look at our commit log and CHANGES.txt, I found something we are missing:
> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Junping Du <jd...@hortonworks.com>.
Thanks Vinod for working hard on this! It is really a huge effort to take care of a release with 154 commits.
I did a sanity check for commits on 2.7.2, all looks fine except HDFS-8767 is missing from CHANGES.txt due to original commit issue. I already update it, and I think we are in good shape now.
Thanks,
Junping
________________________________
From: Vinod Kumar Vavilapalli <vi...@apache.org>
Sent: Wednesday, January 13, 2016 11:15 PM
To: Junping Du
Cc: mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org
Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Okay, did a whole bunch of things on 2.7.2.
Fixing CHANGES.txt entry that Junping reported on the voting thread
- 56e2dcc HADOOP-5323. Trash documentation should describe its directory structure and configurations. (Weiwei Yang via ozawa) Moved entry from HDFS CHANGES.txt to that of common.
Detected one more issue: YARN-2859 addendum’s got missed in 2.7.2
- 2e1c617 YARN-2859 addendum: move the entry from 2.6.2 to 2.6.3 in hadoop-yarn/CHANGES.txt.
- d738e2e YARN-2859.addendum: fix the remaining issue from the previous patch
Also removed multiple duplicate CHANGES.txt entries for MAPREDUCE-6549
Backports
- 91b7f94 YARN-4326. Fix TestDistributedShell timeout as AHS in MiniYarnCluster no longer binds to default port 8188. (Meng Ding via wangda)
- 3c1b25b HADOOP-12413. AccessControlList should avoid calling getGroupNames in isUserInList with empty groups. Contributed by Zhihai Xu. (cherry picked from commit b2017d9b032af20044fdf60ddbd1575a554ccb79)
- 17ad3b1 HADOOP-12526. there are duplicate dependency definitions in pom's (sjlee)
- c3ba72c YARN-4241. Fix typo of property name in yarn-default.xml. Contributed by Anthony Rojas.
- 096ac9e MAPREDUCE-6540. TestMRTimelineEventHandling fails (sjlee)
- 3c0e4de HDFS-8615. Correct HTTP method in WebHDFS document. Contributed by Brahma Reddy Battula.
- ad829ff MAPREDUCE-6377. JHS sorting on state column not working in webUi. Contributed by zhihai xu. (cherry picked from commit 790a861766dcd60212d83f444f2f96d3acf20a94)
- 10f23dc HDFS-9431. DistributedFileSystem#concat fails if the target path is relative. Contributed by Kazuho Fujii.
- 10a6298 YARN-4344. NMs reconnecting with changed capabilities can lead to wrong cluster resource calculations. Contributed by Varun Vasudev (cherry picked from commit d36b6e045f317c94e97cb41a163aa974d161a404)
- 09d3e47 HDFS-9289. Make DataStreamer#block thread safe and verify genStamp in commitBlock. Contributed by Chang Li.
- 89f6716 MAPREDUCE-5883. "Total megabyte-seconds" in job counters is slightly misleading. Contributed by Nathan Roberts (cherry picked from commit cab3c7c8892ad33a7eb0955b01e99872ab95e192)
- 4e84a8b YARN-4365. FileSystemNodeLabelStore should check for root dir existence on startup. Contributed by Kuhu Shukla (cherry picked from commit f5acf94ecafb301a0cc8e8f91f19c8bcbc8da701)
- 4765a65 MAPREDUCE-6549. multibyte delimiters with LineRecordReader cause duplicate records (wilfreds via rkanter) (cherry picked from commit 7fd00b3db4b7d73afd41276ba9a06ec06a0e1762)
- 0fc19f6 YARN-4348. ZKRMStateStore.syncInternal shouldn't wait for sync completion for avoiding blocking ZK's event thread. (ozawa)
- 3e192f8 YARN-4434. NodeManager Disk Checker parameter documentation is not correct. Contributed by Weiwei Yang.
Ran these tests that got changed in the above patches, before pushing the backports:
- TestAccessControlList,DFSTestUtil,TestCommitBlockWithInvalidGenStamp,TestHDFSConcat,TestLineRecordReader,TestMRTimelineEventHandling,TestDistributedShell,TestFileSystemNodeLabelsStore,TestCapacityScheduler
@Junping, mind giving a look at the branch for sanity checks?
Thanks
+Vinod
On Jan 13, 2016, at 11:02 AM, Vinod Kumar Vavilapalli <vi...@apache.org>> wrote:
Thanks for the comments Tsuyoshi / Andrew / Varun / Junping / Akira.
I agree that where possible we should serialize releases and make them incremental w.r.t fixes.
Will roll a new RC for 2.7.2 after the backports.
If there are more thoughts on releases, which I’m sure we will all do have, let’s fork the thread off from this voting conversation.
Thanks
+Vinod
On Dec 29, 2015, at 6:50 AM, Junping Du <jd...@hortonworks.com>> wrote:
I am +1 with pulling all of these tickets into 2.7.2.
- For “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date”
Shall we conclude this as a general rule - "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that get out after 2.x.y release date"? I am generally fine with this, but just feel it sounds to set too strong restrictions among branches. Some fixes could be trivial (test case fix, etc.) enough to deserve more flexibility. I would prefer this rule only applies on critical/blocker fixes, but not applies on minor/trivial issues.
Just 2 cents.
Thanks,
Junping
________________________________
From: Vinod Kumar Vavilapalli <vi...@apache.org>>
Sent: Thursday, December 24, 2015 12:47 AM
To: Junping Du
Cc: mapreduce-dev@hadoop.apache.org<ma...@hadoop.apache.org>; yarn-dev@hadoop.apache.org<ma...@hadoop.apache.org>; common-dev@hadoop.apache.org<ma...@hadoop.apache.org>; hdfs-dev@hadoop.apache.org<ma...@hadoop.apache.org>
Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
I retract my -1. I think we will need to discuss this a bit more.
Beyond those two tickets, there are a bunch more (totaling to 16) that are in 2.6.3 but *not* in 2.7.2. See this: https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0<https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0>
Two options here, depending on the importance of ‘causality' between 2.6.x and 2.7.x lines.
- Ship 2.7.2 as we voted on here
- Pull these 16 tickets into 2.7.2 and roll a new RC
What do people think? Do folks expect “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date (December 16th)”?
Thanks
+Vinod
On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vi...@apache.org>> wrote:
Sigh. Missed this.
To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in.
Reverting my +1, and casting -1 for the RC myself.
Will spin a new RC, this voting thread is marked dead.
Thanks
+Vinod
On Dec 22, 2015, at 8:24 AM, Junping Du <jd...@hortonworks.com>> wrote:
However, when I look at our commit log and CHANGES.txt, I found something we are missing:
1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Junping Du <jd...@hortonworks.com>.
Thanks Vinod for working hard on this! It is really a huge effort to take care of a release with 154 commits.
I did a sanity check for commits on 2.7.2, all looks fine except HDFS-8767 is missing from CHANGES.txt due to original commit issue. I already update it, and I think we are in good shape now.
Thanks,
Junping
________________________________
From: Vinod Kumar Vavilapalli <vi...@apache.org>
Sent: Wednesday, January 13, 2016 11:15 PM
To: Junping Du
Cc: mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org
Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Okay, did a whole bunch of things on 2.7.2.
Fixing CHANGES.txt entry that Junping reported on the voting thread
- 56e2dcc HADOOP-5323. Trash documentation should describe its directory structure and configurations. (Weiwei Yang via ozawa) Moved entry from HDFS CHANGES.txt to that of common.
Detected one more issue: YARN-2859 addendum’s got missed in 2.7.2
- 2e1c617 YARN-2859 addendum: move the entry from 2.6.2 to 2.6.3 in hadoop-yarn/CHANGES.txt.
- d738e2e YARN-2859.addendum: fix the remaining issue from the previous patch
Also removed multiple duplicate CHANGES.txt entries for MAPREDUCE-6549
Backports
- 91b7f94 YARN-4326. Fix TestDistributedShell timeout as AHS in MiniYarnCluster no longer binds to default port 8188. (Meng Ding via wangda)
- 3c1b25b HADOOP-12413. AccessControlList should avoid calling getGroupNames in isUserInList with empty groups. Contributed by Zhihai Xu. (cherry picked from commit b2017d9b032af20044fdf60ddbd1575a554ccb79)
- 17ad3b1 HADOOP-12526. there are duplicate dependency definitions in pom's (sjlee)
- c3ba72c YARN-4241. Fix typo of property name in yarn-default.xml. Contributed by Anthony Rojas.
- 096ac9e MAPREDUCE-6540. TestMRTimelineEventHandling fails (sjlee)
- 3c0e4de HDFS-8615. Correct HTTP method in WebHDFS document. Contributed by Brahma Reddy Battula.
- ad829ff MAPREDUCE-6377. JHS sorting on state column not working in webUi. Contributed by zhihai xu. (cherry picked from commit 790a861766dcd60212d83f444f2f96d3acf20a94)
- 10f23dc HDFS-9431. DistributedFileSystem#concat fails if the target path is relative. Contributed by Kazuho Fujii.
- 10a6298 YARN-4344. NMs reconnecting with changed capabilities can lead to wrong cluster resource calculations. Contributed by Varun Vasudev (cherry picked from commit d36b6e045f317c94e97cb41a163aa974d161a404)
- 09d3e47 HDFS-9289. Make DataStreamer#block thread safe and verify genStamp in commitBlock. Contributed by Chang Li.
- 89f6716 MAPREDUCE-5883. "Total megabyte-seconds" in job counters is slightly misleading. Contributed by Nathan Roberts (cherry picked from commit cab3c7c8892ad33a7eb0955b01e99872ab95e192)
- 4e84a8b YARN-4365. FileSystemNodeLabelStore should check for root dir existence on startup. Contributed by Kuhu Shukla (cherry picked from commit f5acf94ecafb301a0cc8e8f91f19c8bcbc8da701)
- 4765a65 MAPREDUCE-6549. multibyte delimiters with LineRecordReader cause duplicate records (wilfreds via rkanter) (cherry picked from commit 7fd00b3db4b7d73afd41276ba9a06ec06a0e1762)
- 0fc19f6 YARN-4348. ZKRMStateStore.syncInternal shouldn't wait for sync completion for avoiding blocking ZK's event thread. (ozawa)
- 3e192f8 YARN-4434. NodeManager Disk Checker parameter documentation is not correct. Contributed by Weiwei Yang.
Ran these tests that got changed in the above patches, before pushing the backports:
- TestAccessControlList,DFSTestUtil,TestCommitBlockWithInvalidGenStamp,TestHDFSConcat,TestLineRecordReader,TestMRTimelineEventHandling,TestDistributedShell,TestFileSystemNodeLabelsStore,TestCapacityScheduler
@Junping, mind giving a look at the branch for sanity checks?
Thanks
+Vinod
On Jan 13, 2016, at 11:02 AM, Vinod Kumar Vavilapalli <vi...@apache.org>> wrote:
Thanks for the comments Tsuyoshi / Andrew / Varun / Junping / Akira.
I agree that where possible we should serialize releases and make them incremental w.r.t fixes.
Will roll a new RC for 2.7.2 after the backports.
If there are more thoughts on releases, which I’m sure we will all do have, let’s fork the thread off from this voting conversation.
Thanks
+Vinod
On Dec 29, 2015, at 6:50 AM, Junping Du <jd...@hortonworks.com>> wrote:
I am +1 with pulling all of these tickets into 2.7.2.
- For “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date”
Shall we conclude this as a general rule - "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that get out after 2.x.y release date"? I am generally fine with this, but just feel it sounds to set too strong restrictions among branches. Some fixes could be trivial (test case fix, etc.) enough to deserve more flexibility. I would prefer this rule only applies on critical/blocker fixes, but not applies on minor/trivial issues.
Just 2 cents.
Thanks,
Junping
________________________________
From: Vinod Kumar Vavilapalli <vi...@apache.org>>
Sent: Thursday, December 24, 2015 12:47 AM
To: Junping Du
Cc: mapreduce-dev@hadoop.apache.org<ma...@hadoop.apache.org>; yarn-dev@hadoop.apache.org<ma...@hadoop.apache.org>; common-dev@hadoop.apache.org<ma...@hadoop.apache.org>; hdfs-dev@hadoop.apache.org<ma...@hadoop.apache.org>
Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
I retract my -1. I think we will need to discuss this a bit more.
Beyond those two tickets, there are a bunch more (totaling to 16) that are in 2.6.3 but *not* in 2.7.2. See this: https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0<https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0>
Two options here, depending on the importance of ‘causality' between 2.6.x and 2.7.x lines.
- Ship 2.7.2 as we voted on here
- Pull these 16 tickets into 2.7.2 and roll a new RC
What do people think? Do folks expect “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date (December 16th)”?
Thanks
+Vinod
On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vi...@apache.org>> wrote:
Sigh. Missed this.
To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in.
Reverting my +1, and casting -1 for the RC myself.
Will spin a new RC, this voting thread is marked dead.
Thanks
+Vinod
On Dec 22, 2015, at 8:24 AM, Junping Du <jd...@hortonworks.com>> wrote:
However, when I look at our commit log and CHANGES.txt, I found something we are missing:
1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Junping Du <jd...@hortonworks.com>.
Thanks Vinod for working hard on this! It is really a huge effort to take care of a release with 154 commits.
I did a sanity check for commits on 2.7.2, all looks fine except HDFS-8767 is missing from CHANGES.txt due to original commit issue. I already update it, and I think we are in good shape now.
Thanks,
Junping
________________________________
From: Vinod Kumar Vavilapalli <vi...@apache.org>
Sent: Wednesday, January 13, 2016 11:15 PM
To: Junping Du
Cc: mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org
Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Okay, did a whole bunch of things on 2.7.2.
Fixing CHANGES.txt entry that Junping reported on the voting thread
- 56e2dcc HADOOP-5323. Trash documentation should describe its directory structure and configurations. (Weiwei Yang via ozawa) Moved entry from HDFS CHANGES.txt to that of common.
Detected one more issue: YARN-2859 addendum’s got missed in 2.7.2
- 2e1c617 YARN-2859 addendum: move the entry from 2.6.2 to 2.6.3 in hadoop-yarn/CHANGES.txt.
- d738e2e YARN-2859.addendum: fix the remaining issue from the previous patch
Also removed multiple duplicate CHANGES.txt entries for MAPREDUCE-6549
Backports
- 91b7f94 YARN-4326. Fix TestDistributedShell timeout as AHS in MiniYarnCluster no longer binds to default port 8188. (Meng Ding via wangda)
- 3c1b25b HADOOP-12413. AccessControlList should avoid calling getGroupNames in isUserInList with empty groups. Contributed by Zhihai Xu. (cherry picked from commit b2017d9b032af20044fdf60ddbd1575a554ccb79)
- 17ad3b1 HADOOP-12526. there are duplicate dependency definitions in pom's (sjlee)
- c3ba72c YARN-4241. Fix typo of property name in yarn-default.xml. Contributed by Anthony Rojas.
- 096ac9e MAPREDUCE-6540. TestMRTimelineEventHandling fails (sjlee)
- 3c0e4de HDFS-8615. Correct HTTP method in WebHDFS document. Contributed by Brahma Reddy Battula.
- ad829ff MAPREDUCE-6377. JHS sorting on state column not working in webUi. Contributed by zhihai xu. (cherry picked from commit 790a861766dcd60212d83f444f2f96d3acf20a94)
- 10f23dc HDFS-9431. DistributedFileSystem#concat fails if the target path is relative. Contributed by Kazuho Fujii.
- 10a6298 YARN-4344. NMs reconnecting with changed capabilities can lead to wrong cluster resource calculations. Contributed by Varun Vasudev (cherry picked from commit d36b6e045f317c94e97cb41a163aa974d161a404)
- 09d3e47 HDFS-9289. Make DataStreamer#block thread safe and verify genStamp in commitBlock. Contributed by Chang Li.
- 89f6716 MAPREDUCE-5883. "Total megabyte-seconds" in job counters is slightly misleading. Contributed by Nathan Roberts (cherry picked from commit cab3c7c8892ad33a7eb0955b01e99872ab95e192)
- 4e84a8b YARN-4365. FileSystemNodeLabelStore should check for root dir existence on startup. Contributed by Kuhu Shukla (cherry picked from commit f5acf94ecafb301a0cc8e8f91f19c8bcbc8da701)
- 4765a65 MAPREDUCE-6549. multibyte delimiters with LineRecordReader cause duplicate records (wilfreds via rkanter) (cherry picked from commit 7fd00b3db4b7d73afd41276ba9a06ec06a0e1762)
- 0fc19f6 YARN-4348. ZKRMStateStore.syncInternal shouldn't wait for sync completion for avoiding blocking ZK's event thread. (ozawa)
- 3e192f8 YARN-4434. NodeManager Disk Checker parameter documentation is not correct. Contributed by Weiwei Yang.
Ran these tests that got changed in the above patches, before pushing the backports:
- TestAccessControlList,DFSTestUtil,TestCommitBlockWithInvalidGenStamp,TestHDFSConcat,TestLineRecordReader,TestMRTimelineEventHandling,TestDistributedShell,TestFileSystemNodeLabelsStore,TestCapacityScheduler
@Junping, mind giving a look at the branch for sanity checks?
Thanks
+Vinod
On Jan 13, 2016, at 11:02 AM, Vinod Kumar Vavilapalli <vi...@apache.org>> wrote:
Thanks for the comments Tsuyoshi / Andrew / Varun / Junping / Akira.
I agree that where possible we should serialize releases and make them incremental w.r.t fixes.
Will roll a new RC for 2.7.2 after the backports.
If there are more thoughts on releases, which I’m sure we will all do have, let’s fork the thread off from this voting conversation.
Thanks
+Vinod
On Dec 29, 2015, at 6:50 AM, Junping Du <jd...@hortonworks.com>> wrote:
I am +1 with pulling all of these tickets into 2.7.2.
- For “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date”
Shall we conclude this as a general rule - "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that get out after 2.x.y release date"? I am generally fine with this, but just feel it sounds to set too strong restrictions among branches. Some fixes could be trivial (test case fix, etc.) enough to deserve more flexibility. I would prefer this rule only applies on critical/blocker fixes, but not applies on minor/trivial issues.
Just 2 cents.
Thanks,
Junping
________________________________
From: Vinod Kumar Vavilapalli <vi...@apache.org>>
Sent: Thursday, December 24, 2015 12:47 AM
To: Junping Du
Cc: mapreduce-dev@hadoop.apache.org<ma...@hadoop.apache.org>; yarn-dev@hadoop.apache.org<ma...@hadoop.apache.org>; common-dev@hadoop.apache.org<ma...@hadoop.apache.org>; hdfs-dev@hadoop.apache.org<ma...@hadoop.apache.org>
Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
I retract my -1. I think we will need to discuss this a bit more.
Beyond those two tickets, there are a bunch more (totaling to 16) that are in 2.6.3 but *not* in 2.7.2. See this: https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0<https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0>
Two options here, depending on the importance of ‘causality' between 2.6.x and 2.7.x lines.
- Ship 2.7.2 as we voted on here
- Pull these 16 tickets into 2.7.2 and roll a new RC
What do people think? Do folks expect “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date (December 16th)”?
Thanks
+Vinod
On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vi...@apache.org>> wrote:
Sigh. Missed this.
To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in.
Reverting my +1, and casting -1 for the RC myself.
Will spin a new RC, this voting thread is marked dead.
Thanks
+Vinod
On Dec 22, 2015, at 8:24 AM, Junping Du <jd...@hortonworks.com>> wrote:
However, when I look at our commit log and CHANGES.txt, I found something we are missing:
1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Junping Du <jd...@hortonworks.com>.
Thanks Vinod for working hard on this! It is really a huge effort to take care of a release with 154 commits.
I did a sanity check for commits on 2.7.2, all looks fine except HDFS-8767 is missing from CHANGES.txt due to original commit issue. I already update it, and I think we are in good shape now.
Thanks,
Junping
________________________________
From: Vinod Kumar Vavilapalli <vi...@apache.org>
Sent: Wednesday, January 13, 2016 11:15 PM
To: Junping Du
Cc: mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org
Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Okay, did a whole bunch of things on 2.7.2.
Fixing CHANGES.txt entry that Junping reported on the voting thread
- 56e2dcc HADOOP-5323. Trash documentation should describe its directory structure and configurations. (Weiwei Yang via ozawa) Moved entry from HDFS CHANGES.txt to that of common.
Detected one more issue: YARN-2859 addendum’s got missed in 2.7.2
- 2e1c617 YARN-2859 addendum: move the entry from 2.6.2 to 2.6.3 in hadoop-yarn/CHANGES.txt.
- d738e2e YARN-2859.addendum: fix the remaining issue from the previous patch
Also removed multiple duplicate CHANGES.txt entries for MAPREDUCE-6549
Backports
- 91b7f94 YARN-4326. Fix TestDistributedShell timeout as AHS in MiniYarnCluster no longer binds to default port 8188. (Meng Ding via wangda)
- 3c1b25b HADOOP-12413. AccessControlList should avoid calling getGroupNames in isUserInList with empty groups. Contributed by Zhihai Xu. (cherry picked from commit b2017d9b032af20044fdf60ddbd1575a554ccb79)
- 17ad3b1 HADOOP-12526. there are duplicate dependency definitions in pom's (sjlee)
- c3ba72c YARN-4241. Fix typo of property name in yarn-default.xml. Contributed by Anthony Rojas.
- 096ac9e MAPREDUCE-6540. TestMRTimelineEventHandling fails (sjlee)
- 3c0e4de HDFS-8615. Correct HTTP method in WebHDFS document. Contributed by Brahma Reddy Battula.
- ad829ff MAPREDUCE-6377. JHS sorting on state column not working in webUi. Contributed by zhihai xu. (cherry picked from commit 790a861766dcd60212d83f444f2f96d3acf20a94)
- 10f23dc HDFS-9431. DistributedFileSystem#concat fails if the target path is relative. Contributed by Kazuho Fujii.
- 10a6298 YARN-4344. NMs reconnecting with changed capabilities can lead to wrong cluster resource calculations. Contributed by Varun Vasudev (cherry picked from commit d36b6e045f317c94e97cb41a163aa974d161a404)
- 09d3e47 HDFS-9289. Make DataStreamer#block thread safe and verify genStamp in commitBlock. Contributed by Chang Li.
- 89f6716 MAPREDUCE-5883. "Total megabyte-seconds" in job counters is slightly misleading. Contributed by Nathan Roberts (cherry picked from commit cab3c7c8892ad33a7eb0955b01e99872ab95e192)
- 4e84a8b YARN-4365. FileSystemNodeLabelStore should check for root dir existence on startup. Contributed by Kuhu Shukla (cherry picked from commit f5acf94ecafb301a0cc8e8f91f19c8bcbc8da701)
- 4765a65 MAPREDUCE-6549. multibyte delimiters with LineRecordReader cause duplicate records (wilfreds via rkanter) (cherry picked from commit 7fd00b3db4b7d73afd41276ba9a06ec06a0e1762)
- 0fc19f6 YARN-4348. ZKRMStateStore.syncInternal shouldn't wait for sync completion for avoiding blocking ZK's event thread. (ozawa)
- 3e192f8 YARN-4434. NodeManager Disk Checker parameter documentation is not correct. Contributed by Weiwei Yang.
Ran these tests that got changed in the above patches, before pushing the backports:
- TestAccessControlList,DFSTestUtil,TestCommitBlockWithInvalidGenStamp,TestHDFSConcat,TestLineRecordReader,TestMRTimelineEventHandling,TestDistributedShell,TestFileSystemNodeLabelsStore,TestCapacityScheduler
@Junping, mind giving a look at the branch for sanity checks?
Thanks
+Vinod
On Jan 13, 2016, at 11:02 AM, Vinod Kumar Vavilapalli <vi...@apache.org>> wrote:
Thanks for the comments Tsuyoshi / Andrew / Varun / Junping / Akira.
I agree that where possible we should serialize releases and make them incremental w.r.t fixes.
Will roll a new RC for 2.7.2 after the backports.
If there are more thoughts on releases, which I’m sure we will all do have, let’s fork the thread off from this voting conversation.
Thanks
+Vinod
On Dec 29, 2015, at 6:50 AM, Junping Du <jd...@hortonworks.com>> wrote:
I am +1 with pulling all of these tickets into 2.7.2.
- For “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date”
Shall we conclude this as a general rule - "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that get out after 2.x.y release date"? I am generally fine with this, but just feel it sounds to set too strong restrictions among branches. Some fixes could be trivial (test case fix, etc.) enough to deserve more flexibility. I would prefer this rule only applies on critical/blocker fixes, but not applies on minor/trivial issues.
Just 2 cents.
Thanks,
Junping
________________________________
From: Vinod Kumar Vavilapalli <vi...@apache.org>>
Sent: Thursday, December 24, 2015 12:47 AM
To: Junping Du
Cc: mapreduce-dev@hadoop.apache.org<ma...@hadoop.apache.org>; yarn-dev@hadoop.apache.org<ma...@hadoop.apache.org>; common-dev@hadoop.apache.org<ma...@hadoop.apache.org>; hdfs-dev@hadoop.apache.org<ma...@hadoop.apache.org>
Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
I retract my -1. I think we will need to discuss this a bit more.
Beyond those two tickets, there are a bunch more (totaling to 16) that are in 2.6.3 but *not* in 2.7.2. See this: https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0<https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0>
Two options here, depending on the importance of ‘causality' between 2.6.x and 2.7.x lines.
- Ship 2.7.2 as we voted on here
- Pull these 16 tickets into 2.7.2 and roll a new RC
What do people think? Do folks expect “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date (December 16th)”?
Thanks
+Vinod
On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vi...@apache.org>> wrote:
Sigh. Missed this.
To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in.
Reverting my +1, and casting -1 for the RC myself.
Will spin a new RC, this voting thread is marked dead.
Thanks
+Vinod
On Dec 22, 2015, at 8:24 AM, Junping Du <jd...@hortonworks.com>> wrote:
However, when I look at our commit log and CHANGES.txt, I found something we are missing:
1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
Okay, did a whole bunch of things on 2.7.2.
Fixing CHANGES.txt entry that Junping reported on the voting thread
- 56e2dcc HADOOP-5323. Trash documentation should describe its directory structure and configurations. (Weiwei Yang via ozawa) Moved entry from HDFS CHANGES.txt to that of common.
Detected one more issue: YARN-2859 addendum’s got missed in 2.7.2
- 2e1c617 YARN-2859 addendum: move the entry from 2.6.2 to 2.6.3 in hadoop-yarn/CHANGES.txt.
- d738e2e YARN-2859.addendum: fix the remaining issue from the previous patch
Also removed multiple duplicate CHANGES.txt entries for MAPREDUCE-6549
Backports
- 91b7f94 YARN-4326. Fix TestDistributedShell timeout as AHS in MiniYarnCluster no longer binds to default port 8188. (Meng Ding via wangda)
- 3c1b25b HADOOP-12413. AccessControlList should avoid calling getGroupNames in isUserInList with empty groups. Contributed by Zhihai Xu. (cherry picked from commit b2017d9b032af20044fdf60ddbd1575a554ccb79)
- 17ad3b1 HADOOP-12526. there are duplicate dependency definitions in pom's (sjlee)
- c3ba72c YARN-4241. Fix typo of property name in yarn-default.xml. Contributed by Anthony Rojas.
- 096ac9e MAPREDUCE-6540. TestMRTimelineEventHandling fails (sjlee)
- 3c0e4de HDFS-8615. Correct HTTP method in WebHDFS document. Contributed by Brahma Reddy Battula.
- ad829ff MAPREDUCE-6377. JHS sorting on state column not working in webUi. Contributed by zhihai xu. (cherry picked from commit 790a861766dcd60212d83f444f2f96d3acf20a94)
- 10f23dc HDFS-9431. DistributedFileSystem#concat fails if the target path is relative. Contributed by Kazuho Fujii.
- 10a6298 YARN-4344. NMs reconnecting with changed capabilities can lead to wrong cluster resource calculations. Contributed by Varun Vasudev (cherry picked from commit d36b6e045f317c94e97cb41a163aa974d161a404)
- 09d3e47 HDFS-9289. Make DataStreamer#block thread safe and verify genStamp in commitBlock. Contributed by Chang Li.
- 89f6716 MAPREDUCE-5883. "Total megabyte-seconds" in job counters is slightly misleading. Contributed by Nathan Roberts (cherry picked from commit cab3c7c8892ad33a7eb0955b01e99872ab95e192)
- 4e84a8b YARN-4365. FileSystemNodeLabelStore should check for root dir existence on startup. Contributed by Kuhu Shukla (cherry picked from commit f5acf94ecafb301a0cc8e8f91f19c8bcbc8da701)
- 4765a65 MAPREDUCE-6549. multibyte delimiters with LineRecordReader cause duplicate records (wilfreds via rkanter) (cherry picked from commit 7fd00b3db4b7d73afd41276ba9a06ec06a0e1762)
- 0fc19f6 YARN-4348. ZKRMStateStore.syncInternal shouldn't wait for sync completion for avoiding blocking ZK's event thread. (ozawa)
- 3e192f8 YARN-4434. NodeManager Disk Checker parameter documentation is not correct. Contributed by Weiwei Yang.
Ran these tests that got changed in the above patches, before pushing the backports:
- TestAccessControlList,DFSTestUtil,TestCommitBlockWithInvalidGenStamp,TestHDFSConcat,TestLineRecordReader,TestMRTimelineEventHandling,TestDistributedShell,TestFileSystemNodeLabelsStore,TestCapacityScheduler
@Junping, mind giving a look at the branch for sanity checks?
Thanks
+Vinod
> On Jan 13, 2016, at 11:02 AM, Vinod Kumar Vavilapalli <vi...@apache.org> wrote:
>
> Thanks for the comments Tsuyoshi / Andrew / Varun / Junping / Akira.
>
> I agree that where possible we should serialize releases and make them incremental w.r.t fixes.
>
> Will roll a new RC for 2.7.2 after the backports.
>
> If there are more thoughts on releases, which I’m sure we will all do have, let’s fork the thread off from this voting conversation.
>
> Thanks
> +Vinod
>
>> On Dec 29, 2015, at 6:50 AM, Junping Du <jdu@hortonworks.com <ma...@hortonworks.com>> wrote:
>>
>> I am +1 with pulling all of these tickets into 2.7.2.
>> - For “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date”
>> Shall we conclude this as a general rule - "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that get out after 2.x.y release date"? I am generally fine with this, but just feel it sounds to set too strong restrictions among branches. Some fixes could be trivial (test case fix, etc.) enough to deserve more flexibility. I would prefer this rule only applies on critical/blocker fixes, but not applies on minor/trivial issues.
>> Just 2 cents.
>>
>> Thanks,
>>
>> Junping
>>
>> From: Vinod Kumar Vavilapalli <vinodkv@apache.org <ma...@apache.org>>
>> Sent: Thursday, December 24, 2015 12:47 AM
>> To: Junping Du
>> Cc: mapreduce-dev@hadoop.apache.org <ma...@hadoop.apache.org>; yarn-dev@hadoop.apache.org <ma...@hadoop.apache.org>; common-dev@hadoop.apache.org <ma...@hadoop.apache.org>; hdfs-dev@hadoop.apache.org <ma...@hadoop.apache.org>
>> Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
>>
>> I retract my -1. I think we will need to discuss this a bit more.
>>
>> Beyond those two tickets, there are a bunch more (totaling to 16) that are in 2.6.3 but *not* in 2.7.2. See this: https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0 <https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0>
>>
>> Two options here, depending on the importance of ‘causality' between 2.6.x and 2.7.x lines.
>> - Ship 2.7.2 as we voted on here
>> - Pull these 16 tickets into 2.7.2 and roll a new RC
>>
>> What do people think? Do folks expect “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date (December 16th)”?
>>
>> Thanks
>> +Vinod
>>
>>> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vinodkv@apache.org <ma...@apache.org>> wrote:
>>>
>>> Sigh. Missed this.
>>>
>>> To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in.
>>>
>>> Reverting my +1, and casting -1 for the RC myself.
>>>
>>> Will spin a new RC, this voting thread is marked dead.
>>>
>>> Thanks
>>> +Vinod
>>>
>>>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com <ma...@hortonworks.com>> wrote:
>>>>
>>>> However, when I look at our commit log and CHANGES.txt, I found something we are missing:
>>>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
>>>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>>>
>>
>>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
Okay, did a whole bunch of things on 2.7.2.
Fixing CHANGES.txt entry that Junping reported on the voting thread
- 56e2dcc HADOOP-5323. Trash documentation should describe its directory structure and configurations. (Weiwei Yang via ozawa) Moved entry from HDFS CHANGES.txt to that of common.
Detected one more issue: YARN-2859 addendum’s got missed in 2.7.2
- 2e1c617 YARN-2859 addendum: move the entry from 2.6.2 to 2.6.3 in hadoop-yarn/CHANGES.txt.
- d738e2e YARN-2859.addendum: fix the remaining issue from the previous patch
Also removed multiple duplicate CHANGES.txt entries for MAPREDUCE-6549
Backports
- 91b7f94 YARN-4326. Fix TestDistributedShell timeout as AHS in MiniYarnCluster no longer binds to default port 8188. (Meng Ding via wangda)
- 3c1b25b HADOOP-12413. AccessControlList should avoid calling getGroupNames in isUserInList with empty groups. Contributed by Zhihai Xu. (cherry picked from commit b2017d9b032af20044fdf60ddbd1575a554ccb79)
- 17ad3b1 HADOOP-12526. there are duplicate dependency definitions in pom's (sjlee)
- c3ba72c YARN-4241. Fix typo of property name in yarn-default.xml. Contributed by Anthony Rojas.
- 096ac9e MAPREDUCE-6540. TestMRTimelineEventHandling fails (sjlee)
- 3c0e4de HDFS-8615. Correct HTTP method in WebHDFS document. Contributed by Brahma Reddy Battula.
- ad829ff MAPREDUCE-6377. JHS sorting on state column not working in webUi. Contributed by zhihai xu. (cherry picked from commit 790a861766dcd60212d83f444f2f96d3acf20a94)
- 10f23dc HDFS-9431. DistributedFileSystem#concat fails if the target path is relative. Contributed by Kazuho Fujii.
- 10a6298 YARN-4344. NMs reconnecting with changed capabilities can lead to wrong cluster resource calculations. Contributed by Varun Vasudev (cherry picked from commit d36b6e045f317c94e97cb41a163aa974d161a404)
- 09d3e47 HDFS-9289. Make DataStreamer#block thread safe and verify genStamp in commitBlock. Contributed by Chang Li.
- 89f6716 MAPREDUCE-5883. "Total megabyte-seconds" in job counters is slightly misleading. Contributed by Nathan Roberts (cherry picked from commit cab3c7c8892ad33a7eb0955b01e99872ab95e192)
- 4e84a8b YARN-4365. FileSystemNodeLabelStore should check for root dir existence on startup. Contributed by Kuhu Shukla (cherry picked from commit f5acf94ecafb301a0cc8e8f91f19c8bcbc8da701)
- 4765a65 MAPREDUCE-6549. multibyte delimiters with LineRecordReader cause duplicate records (wilfreds via rkanter) (cherry picked from commit 7fd00b3db4b7d73afd41276ba9a06ec06a0e1762)
- 0fc19f6 YARN-4348. ZKRMStateStore.syncInternal shouldn't wait for sync completion for avoiding blocking ZK's event thread. (ozawa)
- 3e192f8 YARN-4434. NodeManager Disk Checker parameter documentation is not correct. Contributed by Weiwei Yang.
Ran these tests that got changed in the above patches, before pushing the backports:
- TestAccessControlList,DFSTestUtil,TestCommitBlockWithInvalidGenStamp,TestHDFSConcat,TestLineRecordReader,TestMRTimelineEventHandling,TestDistributedShell,TestFileSystemNodeLabelsStore,TestCapacityScheduler
@Junping, mind giving a look at the branch for sanity checks?
Thanks
+Vinod
> On Jan 13, 2016, at 11:02 AM, Vinod Kumar Vavilapalli <vi...@apache.org> wrote:
>
> Thanks for the comments Tsuyoshi / Andrew / Varun / Junping / Akira.
>
> I agree that where possible we should serialize releases and make them incremental w.r.t fixes.
>
> Will roll a new RC for 2.7.2 after the backports.
>
> If there are more thoughts on releases, which I’m sure we will all do have, let’s fork the thread off from this voting conversation.
>
> Thanks
> +Vinod
>
>> On Dec 29, 2015, at 6:50 AM, Junping Du <jdu@hortonworks.com <ma...@hortonworks.com>> wrote:
>>
>> I am +1 with pulling all of these tickets into 2.7.2.
>> - For “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date”
>> Shall we conclude this as a general rule - "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that get out after 2.x.y release date"? I am generally fine with this, but just feel it sounds to set too strong restrictions among branches. Some fixes could be trivial (test case fix, etc.) enough to deserve more flexibility. I would prefer this rule only applies on critical/blocker fixes, but not applies on minor/trivial issues.
>> Just 2 cents.
>>
>> Thanks,
>>
>> Junping
>>
>> From: Vinod Kumar Vavilapalli <vinodkv@apache.org <ma...@apache.org>>
>> Sent: Thursday, December 24, 2015 12:47 AM
>> To: Junping Du
>> Cc: mapreduce-dev@hadoop.apache.org <ma...@hadoop.apache.org>; yarn-dev@hadoop.apache.org <ma...@hadoop.apache.org>; common-dev@hadoop.apache.org <ma...@hadoop.apache.org>; hdfs-dev@hadoop.apache.org <ma...@hadoop.apache.org>
>> Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
>>
>> I retract my -1. I think we will need to discuss this a bit more.
>>
>> Beyond those two tickets, there are a bunch more (totaling to 16) that are in 2.6.3 but *not* in 2.7.2. See this: https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0 <https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0>
>>
>> Two options here, depending on the importance of ‘causality' between 2.6.x and 2.7.x lines.
>> - Ship 2.7.2 as we voted on here
>> - Pull these 16 tickets into 2.7.2 and roll a new RC
>>
>> What do people think? Do folks expect “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date (December 16th)”?
>>
>> Thanks
>> +Vinod
>>
>>> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vinodkv@apache.org <ma...@apache.org>> wrote:
>>>
>>> Sigh. Missed this.
>>>
>>> To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in.
>>>
>>> Reverting my +1, and casting -1 for the RC myself.
>>>
>>> Will spin a new RC, this voting thread is marked dead.
>>>
>>> Thanks
>>> +Vinod
>>>
>>>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com <ma...@hortonworks.com>> wrote:
>>>>
>>>> However, when I look at our commit log and CHANGES.txt, I found something we are missing:
>>>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
>>>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>>>
>>
>>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
Okay, did a whole bunch of things on 2.7.2.
Fixing CHANGES.txt entry that Junping reported on the voting thread
- 56e2dcc HADOOP-5323. Trash documentation should describe its directory structure and configurations. (Weiwei Yang via ozawa) Moved entry from HDFS CHANGES.txt to that of common.
Detected one more issue: YARN-2859 addendum’s got missed in 2.7.2
- 2e1c617 YARN-2859 addendum: move the entry from 2.6.2 to 2.6.3 in hadoop-yarn/CHANGES.txt.
- d738e2e YARN-2859.addendum: fix the remaining issue from the previous patch
Also removed multiple duplicate CHANGES.txt entries for MAPREDUCE-6549
Backports
- 91b7f94 YARN-4326. Fix TestDistributedShell timeout as AHS in MiniYarnCluster no longer binds to default port 8188. (Meng Ding via wangda)
- 3c1b25b HADOOP-12413. AccessControlList should avoid calling getGroupNames in isUserInList with empty groups. Contributed by Zhihai Xu. (cherry picked from commit b2017d9b032af20044fdf60ddbd1575a554ccb79)
- 17ad3b1 HADOOP-12526. there are duplicate dependency definitions in pom's (sjlee)
- c3ba72c YARN-4241. Fix typo of property name in yarn-default.xml. Contributed by Anthony Rojas.
- 096ac9e MAPREDUCE-6540. TestMRTimelineEventHandling fails (sjlee)
- 3c0e4de HDFS-8615. Correct HTTP method in WebHDFS document. Contributed by Brahma Reddy Battula.
- ad829ff MAPREDUCE-6377. JHS sorting on state column not working in webUi. Contributed by zhihai xu. (cherry picked from commit 790a861766dcd60212d83f444f2f96d3acf20a94)
- 10f23dc HDFS-9431. DistributedFileSystem#concat fails if the target path is relative. Contributed by Kazuho Fujii.
- 10a6298 YARN-4344. NMs reconnecting with changed capabilities can lead to wrong cluster resource calculations. Contributed by Varun Vasudev (cherry picked from commit d36b6e045f317c94e97cb41a163aa974d161a404)
- 09d3e47 HDFS-9289. Make DataStreamer#block thread safe and verify genStamp in commitBlock. Contributed by Chang Li.
- 89f6716 MAPREDUCE-5883. "Total megabyte-seconds" in job counters is slightly misleading. Contributed by Nathan Roberts (cherry picked from commit cab3c7c8892ad33a7eb0955b01e99872ab95e192)
- 4e84a8b YARN-4365. FileSystemNodeLabelStore should check for root dir existence on startup. Contributed by Kuhu Shukla (cherry picked from commit f5acf94ecafb301a0cc8e8f91f19c8bcbc8da701)
- 4765a65 MAPREDUCE-6549. multibyte delimiters with LineRecordReader cause duplicate records (wilfreds via rkanter) (cherry picked from commit 7fd00b3db4b7d73afd41276ba9a06ec06a0e1762)
- 0fc19f6 YARN-4348. ZKRMStateStore.syncInternal shouldn't wait for sync completion for avoiding blocking ZK's event thread. (ozawa)
- 3e192f8 YARN-4434. NodeManager Disk Checker parameter documentation is not correct. Contributed by Weiwei Yang.
Ran these tests that got changed in the above patches, before pushing the backports:
- TestAccessControlList,DFSTestUtil,TestCommitBlockWithInvalidGenStamp,TestHDFSConcat,TestLineRecordReader,TestMRTimelineEventHandling,TestDistributedShell,TestFileSystemNodeLabelsStore,TestCapacityScheduler
@Junping, mind giving a look at the branch for sanity checks?
Thanks
+Vinod
> On Jan 13, 2016, at 11:02 AM, Vinod Kumar Vavilapalli <vi...@apache.org> wrote:
>
> Thanks for the comments Tsuyoshi / Andrew / Varun / Junping / Akira.
>
> I agree that where possible we should serialize releases and make them incremental w.r.t fixes.
>
> Will roll a new RC for 2.7.2 after the backports.
>
> If there are more thoughts on releases, which I’m sure we will all do have, let’s fork the thread off from this voting conversation.
>
> Thanks
> +Vinod
>
>> On Dec 29, 2015, at 6:50 AM, Junping Du <jdu@hortonworks.com <ma...@hortonworks.com>> wrote:
>>
>> I am +1 with pulling all of these tickets into 2.7.2.
>> - For “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date”
>> Shall we conclude this as a general rule - "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that get out after 2.x.y release date"? I am generally fine with this, but just feel it sounds to set too strong restrictions among branches. Some fixes could be trivial (test case fix, etc.) enough to deserve more flexibility. I would prefer this rule only applies on critical/blocker fixes, but not applies on minor/trivial issues.
>> Just 2 cents.
>>
>> Thanks,
>>
>> Junping
>>
>> From: Vinod Kumar Vavilapalli <vinodkv@apache.org <ma...@apache.org>>
>> Sent: Thursday, December 24, 2015 12:47 AM
>> To: Junping Du
>> Cc: mapreduce-dev@hadoop.apache.org <ma...@hadoop.apache.org>; yarn-dev@hadoop.apache.org <ma...@hadoop.apache.org>; common-dev@hadoop.apache.org <ma...@hadoop.apache.org>; hdfs-dev@hadoop.apache.org <ma...@hadoop.apache.org>
>> Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
>>
>> I retract my -1. I think we will need to discuss this a bit more.
>>
>> Beyond those two tickets, there are a bunch more (totaling to 16) that are in 2.6.3 but *not* in 2.7.2. See this: https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0 <https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0>
>>
>> Two options here, depending on the importance of ‘causality' between 2.6.x and 2.7.x lines.
>> - Ship 2.7.2 as we voted on here
>> - Pull these 16 tickets into 2.7.2 and roll a new RC
>>
>> What do people think? Do folks expect “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date (December 16th)”?
>>
>> Thanks
>> +Vinod
>>
>>> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vinodkv@apache.org <ma...@apache.org>> wrote:
>>>
>>> Sigh. Missed this.
>>>
>>> To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in.
>>>
>>> Reverting my +1, and casting -1 for the RC myself.
>>>
>>> Will spin a new RC, this voting thread is marked dead.
>>>
>>> Thanks
>>> +Vinod
>>>
>>>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com <ma...@hortonworks.com>> wrote:
>>>>
>>>> However, when I look at our commit log and CHANGES.txt, I found something we are missing:
>>>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
>>>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>>>
>>
>>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
Okay, did a whole bunch of things on 2.7.2.
Fixing CHANGES.txt entry that Junping reported on the voting thread
- 56e2dcc HADOOP-5323. Trash documentation should describe its directory structure and configurations. (Weiwei Yang via ozawa) Moved entry from HDFS CHANGES.txt to that of common.
Detected one more issue: YARN-2859 addendum’s got missed in 2.7.2
- 2e1c617 YARN-2859 addendum: move the entry from 2.6.2 to 2.6.3 in hadoop-yarn/CHANGES.txt.
- d738e2e YARN-2859.addendum: fix the remaining issue from the previous patch
Also removed multiple duplicate CHANGES.txt entries for MAPREDUCE-6549
Backports
- 91b7f94 YARN-4326. Fix TestDistributedShell timeout as AHS in MiniYarnCluster no longer binds to default port 8188. (Meng Ding via wangda)
- 3c1b25b HADOOP-12413. AccessControlList should avoid calling getGroupNames in isUserInList with empty groups. Contributed by Zhihai Xu. (cherry picked from commit b2017d9b032af20044fdf60ddbd1575a554ccb79)
- 17ad3b1 HADOOP-12526. there are duplicate dependency definitions in pom's (sjlee)
- c3ba72c YARN-4241. Fix typo of property name in yarn-default.xml. Contributed by Anthony Rojas.
- 096ac9e MAPREDUCE-6540. TestMRTimelineEventHandling fails (sjlee)
- 3c0e4de HDFS-8615. Correct HTTP method in WebHDFS document. Contributed by Brahma Reddy Battula.
- ad829ff MAPREDUCE-6377. JHS sorting on state column not working in webUi. Contributed by zhihai xu. (cherry picked from commit 790a861766dcd60212d83f444f2f96d3acf20a94)
- 10f23dc HDFS-9431. DistributedFileSystem#concat fails if the target path is relative. Contributed by Kazuho Fujii.
- 10a6298 YARN-4344. NMs reconnecting with changed capabilities can lead to wrong cluster resource calculations. Contributed by Varun Vasudev (cherry picked from commit d36b6e045f317c94e97cb41a163aa974d161a404)
- 09d3e47 HDFS-9289. Make DataStreamer#block thread safe and verify genStamp in commitBlock. Contributed by Chang Li.
- 89f6716 MAPREDUCE-5883. "Total megabyte-seconds" in job counters is slightly misleading. Contributed by Nathan Roberts (cherry picked from commit cab3c7c8892ad33a7eb0955b01e99872ab95e192)
- 4e84a8b YARN-4365. FileSystemNodeLabelStore should check for root dir existence on startup. Contributed by Kuhu Shukla (cherry picked from commit f5acf94ecafb301a0cc8e8f91f19c8bcbc8da701)
- 4765a65 MAPREDUCE-6549. multibyte delimiters with LineRecordReader cause duplicate records (wilfreds via rkanter) (cherry picked from commit 7fd00b3db4b7d73afd41276ba9a06ec06a0e1762)
- 0fc19f6 YARN-4348. ZKRMStateStore.syncInternal shouldn't wait for sync completion for avoiding blocking ZK's event thread. (ozawa)
- 3e192f8 YARN-4434. NodeManager Disk Checker parameter documentation is not correct. Contributed by Weiwei Yang.
Ran these tests that got changed in the above patches, before pushing the backports:
- TestAccessControlList,DFSTestUtil,TestCommitBlockWithInvalidGenStamp,TestHDFSConcat,TestLineRecordReader,TestMRTimelineEventHandling,TestDistributedShell,TestFileSystemNodeLabelsStore,TestCapacityScheduler
@Junping, mind giving a look at the branch for sanity checks?
Thanks
+Vinod
> On Jan 13, 2016, at 11:02 AM, Vinod Kumar Vavilapalli <vi...@apache.org> wrote:
>
> Thanks for the comments Tsuyoshi / Andrew / Varun / Junping / Akira.
>
> I agree that where possible we should serialize releases and make them incremental w.r.t fixes.
>
> Will roll a new RC for 2.7.2 after the backports.
>
> If there are more thoughts on releases, which I’m sure we will all do have, let’s fork the thread off from this voting conversation.
>
> Thanks
> +Vinod
>
>> On Dec 29, 2015, at 6:50 AM, Junping Du <jdu@hortonworks.com <ma...@hortonworks.com>> wrote:
>>
>> I am +1 with pulling all of these tickets into 2.7.2.
>> - For “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date”
>> Shall we conclude this as a general rule - "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that get out after 2.x.y release date"? I am generally fine with this, but just feel it sounds to set too strong restrictions among branches. Some fixes could be trivial (test case fix, etc.) enough to deserve more flexibility. I would prefer this rule only applies on critical/blocker fixes, but not applies on minor/trivial issues.
>> Just 2 cents.
>>
>> Thanks,
>>
>> Junping
>>
>> From: Vinod Kumar Vavilapalli <vinodkv@apache.org <ma...@apache.org>>
>> Sent: Thursday, December 24, 2015 12:47 AM
>> To: Junping Du
>> Cc: mapreduce-dev@hadoop.apache.org <ma...@hadoop.apache.org>; yarn-dev@hadoop.apache.org <ma...@hadoop.apache.org>; common-dev@hadoop.apache.org <ma...@hadoop.apache.org>; hdfs-dev@hadoop.apache.org <ma...@hadoop.apache.org>
>> Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
>>
>> I retract my -1. I think we will need to discuss this a bit more.
>>
>> Beyond those two tickets, there are a bunch more (totaling to 16) that are in 2.6.3 but *not* in 2.7.2. See this: https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0 <https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0>
>>
>> Two options here, depending on the importance of ‘causality' between 2.6.x and 2.7.x lines.
>> - Ship 2.7.2 as we voted on here
>> - Pull these 16 tickets into 2.7.2 and roll a new RC
>>
>> What do people think? Do folks expect “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date (December 16th)”?
>>
>> Thanks
>> +Vinod
>>
>>> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vinodkv@apache.org <ma...@apache.org>> wrote:
>>>
>>> Sigh. Missed this.
>>>
>>> To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in.
>>>
>>> Reverting my +1, and casting -1 for the RC myself.
>>>
>>> Will spin a new RC, this voting thread is marked dead.
>>>
>>> Thanks
>>> +Vinod
>>>
>>>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com <ma...@hortonworks.com>> wrote:
>>>>
>>>> However, when I look at our commit log and CHANGES.txt, I found something we are missing:
>>>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
>>>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>>>
>>
>>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
Thanks for the comments Tsuyoshi / Andrew / Varun / Junping / Akira.
I agree that where possible we should serialize releases and make them incremental w.r.t fixes.
Will roll a new RC for 2.7.2 after the backports.
If there are more thoughts on releases, which I’m sure we will all do have, let’s fork the thread off from this voting conversation.
Thanks
+Vinod
> On Dec 29, 2015, at 6:50 AM, Junping Du <jd...@hortonworks.com> wrote:
>
> I am +1 with pulling all of these tickets into 2.7.2.
> - For “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date”
> Shall we conclude this as a general rule - "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that get out after 2.x.y release date"? I am generally fine with this, but just feel it sounds to set too strong restrictions among branches. Some fixes could be trivial (test case fix, etc.) enough to deserve more flexibility. I would prefer this rule only applies on critical/blocker fixes, but not applies on minor/trivial issues.
> Just 2 cents.
>
> Thanks,
>
> Junping
>
> From: Vinod Kumar Vavilapalli <vinodkv@apache.org <ma...@apache.org>>
> Sent: Thursday, December 24, 2015 12:47 AM
> To: Junping Du
> Cc: mapreduce-dev@hadoop.apache.org <ma...@hadoop.apache.org>; yarn-dev@hadoop.apache.org <ma...@hadoop.apache.org>; common-dev@hadoop.apache.org <ma...@hadoop.apache.org>; hdfs-dev@hadoop.apache.org <ma...@hadoop.apache.org>
> Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
>
> I retract my -1. I think we will need to discuss this a bit more.
>
> Beyond those two tickets, there are a bunch more (totaling to 16) that are in 2.6.3 but *not* in 2.7.2. See this: https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0 <https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0>
>
> Two options here, depending on the importance of ‘causality' between 2.6.x and 2.7.x lines.
> - Ship 2.7.2 as we voted on here
> - Pull these 16 tickets into 2.7.2 and roll a new RC
>
> What do people think? Do folks expect “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date (December 16th)”?
>
> Thanks
> +Vinod
>
>> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vinodkv@apache.org <ma...@apache.org>> wrote:
>>
>> Sigh. Missed this.
>>
>> To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in.
>>
>> Reverting my +1, and casting -1 for the RC myself.
>>
>> Will spin a new RC, this voting thread is marked dead.
>>
>> Thanks
>> +Vinod
>>
>>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com <ma...@hortonworks.com>> wrote:
>>>
>>> However, when I look at our commit log and CHANGES.txt, I found something we are missing:
>>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
>>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>>
>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
Thanks for the comments Tsuyoshi / Andrew / Varun / Junping / Akira.
I agree that where possible we should serialize releases and make them incremental w.r.t fixes.
Will roll a new RC for 2.7.2 after the backports.
If there are more thoughts on releases, which I’m sure we will all do have, let’s fork the thread off from this voting conversation.
Thanks
+Vinod
> On Dec 29, 2015, at 6:50 AM, Junping Du <jd...@hortonworks.com> wrote:
>
> I am +1 with pulling all of these tickets into 2.7.2.
> - For “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date”
> Shall we conclude this as a general rule - "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that get out after 2.x.y release date"? I am generally fine with this, but just feel it sounds to set too strong restrictions among branches. Some fixes could be trivial (test case fix, etc.) enough to deserve more flexibility. I would prefer this rule only applies on critical/blocker fixes, but not applies on minor/trivial issues.
> Just 2 cents.
>
> Thanks,
>
> Junping
>
> From: Vinod Kumar Vavilapalli <vinodkv@apache.org <ma...@apache.org>>
> Sent: Thursday, December 24, 2015 12:47 AM
> To: Junping Du
> Cc: mapreduce-dev@hadoop.apache.org <ma...@hadoop.apache.org>; yarn-dev@hadoop.apache.org <ma...@hadoop.apache.org>; common-dev@hadoop.apache.org <ma...@hadoop.apache.org>; hdfs-dev@hadoop.apache.org <ma...@hadoop.apache.org>
> Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
>
> I retract my -1. I think we will need to discuss this a bit more.
>
> Beyond those two tickets, there are a bunch more (totaling to 16) that are in 2.6.3 but *not* in 2.7.2. See this: https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0 <https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0>
>
> Two options here, depending on the importance of ‘causality' between 2.6.x and 2.7.x lines.
> - Ship 2.7.2 as we voted on here
> - Pull these 16 tickets into 2.7.2 and roll a new RC
>
> What do people think? Do folks expect “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date (December 16th)”?
>
> Thanks
> +Vinod
>
>> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vinodkv@apache.org <ma...@apache.org>> wrote:
>>
>> Sigh. Missed this.
>>
>> To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in.
>>
>> Reverting my +1, and casting -1 for the RC myself.
>>
>> Will spin a new RC, this voting thread is marked dead.
>>
>> Thanks
>> +Vinod
>>
>>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com <ma...@hortonworks.com>> wrote:
>>>
>>> However, when I look at our commit log and CHANGES.txt, I found something we are missing:
>>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
>>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>>
>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Akira AJISAKA <aj...@oss.nttdata.co.jp>.
The general rule sounds good to me.
> "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that
get out after 2.x.y release date"
+1
> I would prefer this rule only applies on critical/blocker fixes, but
not applies on minor/trivial issues.
+1
Thanks,
Akira
On 12/29/15 23:50, Junping Du wrote:
> I am +1 with pulling all of these tickets into 2.7.2.
>
> - For “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date”
>
> Shall we conclude this as a general rule - "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that get out after 2.x.y release date"? I am generally fine with this, but just feel it sounds to set too strong restrictions among branches. Some fixes could be trivial (test case fix, etc.) enough to deserve more flexibility. I would prefer this rule only applies on critical/blocker fixes, but not applies on minor/trivial issues.
>
> Just 2 cents.
>
>
> Thanks,
>
>
> Junping
>
>
> ________________________________
> From: Vinod Kumar Vavilapalli <vi...@apache.org>
> Sent: Thursday, December 24, 2015 12:47 AM
> To: Junping Du
> Cc: mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org
> Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
>
> I retract my -1. I think we will need to discuss this a bit more.
>
> Beyond those two tickets, there are a bunch more (totaling to 16) that are in 2.6.3 but *not* in 2.7.2. See this: https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0<https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0>
>
> Two options here, depending on the importance of ‘causality' between 2.6.x and 2.7.x lines.
> - Ship 2.7.2 as we voted on here
> - Pull these 16 tickets into 2.7.2 and roll a new RC
>
> What do people think? Do folks expect “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date (December 16th)”?
>
> Thanks
> +Vinod
>
> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vi...@apache.org>> wrote:
>
> Sigh. Missed this.
>
> To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in.
>
> Reverting my +1, and casting -1 for the RC myself.
>
> Will spin a new RC, this voting thread is marked dead.
>
> Thanks
> +Vinod
>
> On Dec 22, 2015, at 8:24 AM, Junping Du <jd...@hortonworks.com>> wrote:
>
> However, when I look at our commit log and CHANGES.txt, I found something we are missing:
> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
Thanks for the comments Tsuyoshi / Andrew / Varun / Junping / Akira.
I agree that where possible we should serialize releases and make them incremental w.r.t fixes.
Will roll a new RC for 2.7.2 after the backports.
If there are more thoughts on releases, which I’m sure we will all do have, let’s fork the thread off from this voting conversation.
Thanks
+Vinod
> On Dec 29, 2015, at 6:50 AM, Junping Du <jd...@hortonworks.com> wrote:
>
> I am +1 with pulling all of these tickets into 2.7.2.
> - For “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date”
> Shall we conclude this as a general rule - "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that get out after 2.x.y release date"? I am generally fine with this, but just feel it sounds to set too strong restrictions among branches. Some fixes could be trivial (test case fix, etc.) enough to deserve more flexibility. I would prefer this rule only applies on critical/blocker fixes, but not applies on minor/trivial issues.
> Just 2 cents.
>
> Thanks,
>
> Junping
>
> From: Vinod Kumar Vavilapalli <vinodkv@apache.org <ma...@apache.org>>
> Sent: Thursday, December 24, 2015 12:47 AM
> To: Junping Du
> Cc: mapreduce-dev@hadoop.apache.org <ma...@hadoop.apache.org>; yarn-dev@hadoop.apache.org <ma...@hadoop.apache.org>; common-dev@hadoop.apache.org <ma...@hadoop.apache.org>; hdfs-dev@hadoop.apache.org <ma...@hadoop.apache.org>
> Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
>
> I retract my -1. I think we will need to discuss this a bit more.
>
> Beyond those two tickets, there are a bunch more (totaling to 16) that are in 2.6.3 but *not* in 2.7.2. See this: https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0 <https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0>
>
> Two options here, depending on the importance of ‘causality' between 2.6.x and 2.7.x lines.
> - Ship 2.7.2 as we voted on here
> - Pull these 16 tickets into 2.7.2 and roll a new RC
>
> What do people think? Do folks expect “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date (December 16th)”?
>
> Thanks
> +Vinod
>
>> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vinodkv@apache.org <ma...@apache.org>> wrote:
>>
>> Sigh. Missed this.
>>
>> To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in.
>>
>> Reverting my +1, and casting -1 for the RC myself.
>>
>> Will spin a new RC, this voting thread is marked dead.
>>
>> Thanks
>> +Vinod
>>
>>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com <ma...@hortonworks.com>> wrote:
>>>
>>> However, when I look at our commit log and CHANGES.txt, I found something we are missing:
>>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
>>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>>
>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
Thanks for the comments Tsuyoshi / Andrew / Varun / Junping / Akira.
I agree that where possible we should serialize releases and make them incremental w.r.t fixes.
Will roll a new RC for 2.7.2 after the backports.
If there are more thoughts on releases, which I’m sure we will all do have, let’s fork the thread off from this voting conversation.
Thanks
+Vinod
> On Dec 29, 2015, at 6:50 AM, Junping Du <jd...@hortonworks.com> wrote:
>
> I am +1 with pulling all of these tickets into 2.7.2.
> - For “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date”
> Shall we conclude this as a general rule - "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that get out after 2.x.y release date"? I am generally fine with this, but just feel it sounds to set too strong restrictions among branches. Some fixes could be trivial (test case fix, etc.) enough to deserve more flexibility. I would prefer this rule only applies on critical/blocker fixes, but not applies on minor/trivial issues.
> Just 2 cents.
>
> Thanks,
>
> Junping
>
> From: Vinod Kumar Vavilapalli <vinodkv@apache.org <ma...@apache.org>>
> Sent: Thursday, December 24, 2015 12:47 AM
> To: Junping Du
> Cc: mapreduce-dev@hadoop.apache.org <ma...@hadoop.apache.org>; yarn-dev@hadoop.apache.org <ma...@hadoop.apache.org>; common-dev@hadoop.apache.org <ma...@hadoop.apache.org>; hdfs-dev@hadoop.apache.org <ma...@hadoop.apache.org>
> Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
>
> I retract my -1. I think we will need to discuss this a bit more.
>
> Beyond those two tickets, there are a bunch more (totaling to 16) that are in 2.6.3 but *not* in 2.7.2. See this: https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0 <https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0>
>
> Two options here, depending on the importance of ‘causality' between 2.6.x and 2.7.x lines.
> - Ship 2.7.2 as we voted on here
> - Pull these 16 tickets into 2.7.2 and roll a new RC
>
> What do people think? Do folks expect “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date (December 16th)”?
>
> Thanks
> +Vinod
>
>> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vinodkv@apache.org <ma...@apache.org>> wrote:
>>
>> Sigh. Missed this.
>>
>> To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in.
>>
>> Reverting my +1, and casting -1 for the RC myself.
>>
>> Will spin a new RC, this voting thread is marked dead.
>>
>> Thanks
>> +Vinod
>>
>>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com <ma...@hortonworks.com>> wrote:
>>>
>>> However, when I look at our commit log and CHANGES.txt, I found something we are missing:
>>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
>>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>>
>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Akira AJISAKA <aj...@oss.nttdata.co.jp>.
The general rule sounds good to me.
> "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that
get out after 2.x.y release date"
+1
> I would prefer this rule only applies on critical/blocker fixes, but
not applies on minor/trivial issues.
+1
Thanks,
Akira
On 12/29/15 23:50, Junping Du wrote:
> I am +1 with pulling all of these tickets into 2.7.2.
>
> - For “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date”
>
> Shall we conclude this as a general rule - "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that get out after 2.x.y release date"? I am generally fine with this, but just feel it sounds to set too strong restrictions among branches. Some fixes could be trivial (test case fix, etc.) enough to deserve more flexibility. I would prefer this rule only applies on critical/blocker fixes, but not applies on minor/trivial issues.
>
> Just 2 cents.
>
>
> Thanks,
>
>
> Junping
>
>
> ________________________________
> From: Vinod Kumar Vavilapalli <vi...@apache.org>
> Sent: Thursday, December 24, 2015 12:47 AM
> To: Junping Du
> Cc: mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org
> Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
>
> I retract my -1. I think we will need to discuss this a bit more.
>
> Beyond those two tickets, there are a bunch more (totaling to 16) that are in 2.6.3 but *not* in 2.7.2. See this: https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0<https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0>
>
> Two options here, depending on the importance of ‘causality' between 2.6.x and 2.7.x lines.
> - Ship 2.7.2 as we voted on here
> - Pull these 16 tickets into 2.7.2 and roll a new RC
>
> What do people think? Do folks expect “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date (December 16th)”?
>
> Thanks
> +Vinod
>
> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vi...@apache.org>> wrote:
>
> Sigh. Missed this.
>
> To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in.
>
> Reverting my +1, and casting -1 for the RC myself.
>
> Will spin a new RC, this voting thread is marked dead.
>
> Thanks
> +Vinod
>
> On Dec 22, 2015, at 8:24 AM, Junping Du <jd...@hortonworks.com>> wrote:
>
> However, when I look at our commit log and CHANGES.txt, I found something we are missing:
> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Junping Du <jd...@hortonworks.com>.
I am +1 with pulling all of these tickets into 2.7.2.
- For “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date”
Shall we conclude this as a general rule - "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that get out after 2.x.y release date"? I am generally fine with this, but just feel it sounds to set too strong restrictions among branches. Some fixes could be trivial (test case fix, etc.) enough to deserve more flexibility. I would prefer this rule only applies on critical/blocker fixes, but not applies on minor/trivial issues.
Just 2 cents.
Thanks,
Junping
________________________________
From: Vinod Kumar Vavilapalli <vi...@apache.org>
Sent: Thursday, December 24, 2015 12:47 AM
To: Junping Du
Cc: mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org
Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
I retract my -1. I think we will need to discuss this a bit more.
Beyond those two tickets, there are a bunch more (totaling to 16) that are in 2.6.3 but *not* in 2.7.2. See this: https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0<https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0>
Two options here, depending on the importance of ‘causality' between 2.6.x and 2.7.x lines.
- Ship 2.7.2 as we voted on here
- Pull these 16 tickets into 2.7.2 and roll a new RC
What do people think? Do folks expect “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date (December 16th)”?
Thanks
+Vinod
On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vi...@apache.org>> wrote:
Sigh. Missed this.
To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in.
Reverting my +1, and casting -1 for the RC myself.
Will spin a new RC, this voting thread is marked dead.
Thanks
+Vinod
On Dec 22, 2015, at 8:24 AM, Junping Du <jd...@hortonworks.com>> wrote:
However, when I look at our commit log and CHANGES.txt, I found something we are missing:
1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Varun Vasudev <vv...@apache.org>.
+1 on cherry-picking the fixes into 2.7.2.
-Varun
On 12/25/15, 9:08 AM, "Akira AJISAKA" <aj...@oss.nttdata.co.jp> wrote:
>Thanks Vinod for starting the discussion.
>I'm +1 for cherry-picking these issues to 2.7.2.
>
>As Andrew said, when users upgrade Hadoop from 2.6.3 to 2.7.2,
>they can hit the issues.
>I'm thinking we should reduce the regressions as possible.
>
>Regards,
>Akira
>
>On 12/25/15 01:56, Andrew Wang wrote:
>> My 2c is that we should have monotonicity in releases. That way no
>> "upgrade" is a regression.
>>
>> On Wed, Dec 23, 2015 at 10:00 PM, Tsuyoshi Ozawa <oz...@apache.org> wrote:
>>
>>> Hi Vinod,
>>>
>>> thank you for the clarification.
>>>
>>>> - Pull these 16 tickets into 2.7.2 and roll a new RC
>>>>> What do people think? Do folks expect “any fix in 2.6.3 to be there in
>>> all releases that get out after 2.6.3 release date (December 16th)”?
>>>
>>> I personally prefer to pull these tickets into 2.7.2 since it's
>>> intuitive for me. I can help to cherrypick these tickets into 2.7.2
>>> once we decide to do so.
>>>
>>> This conflicts happened since the the timings of cutting branches and
>>> actual release are crossed. We can face these situations usually in
>>> the future since we have 2 or more branches for stable releases.
>>> Hence, it's a good time to decide basic policy now.
>>>
>>> BTW, should we start to discuss on new thread or continue to discuss here?
>>>
>>> Thanks,
>>> - Tsuyoshi
>>>
>>> On Thu, Dec 24, 2015 at 9:47 AM, Vinod Kumar Vavilapalli
>>> <vi...@apache.org> wrote:
>>>> I retract my -1. I think we will need to discuss this a bit more.
>>>>
>>>> Beyond those two tickets, there are a bunch more (totaling to 16) that
>>> are in 2.6.3 but *not* in 2.7.2. See this:
>>> https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0
>>> <
>>> https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0
>>>>
>>>>
>>>> Two options here, depending on the importance of ‘causality' between
>>> 2.6.x and 2.7.x lines.
>>>> - Ship 2.7.2 as we voted on here
>>>> - Pull these 16 tickets into 2.7.2 and roll a new RC
>>>>
>>>> What do people think? Do folks expect “any fix in 2.6.3 to be there in
>>> all releases that get out after 2.6.3 release date (December 16th)”?
>>>>
>>>> Thanks
>>>> +Vinod
>>>>
>>>>> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <
>>> vinodkv@apache.org> wrote:
>>>>>
>>>>> Sigh. Missed this.
>>>>>
>>>>> To retain causality ("any fix in 2.6.3 will be there in all releases
>>> that got out after 2.6.3”), I’ll get these patches in.
>>>>>
>>>>> Reverting my +1, and casting -1 for the RC myself.
>>>>>
>>>>> Will spin a new RC, this voting thread is marked dead.
>>>>>
>>>>> Thanks
>>>>> +Vinod
>>>>>
>>>>>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com <mailto:
>>> jdu@hortonworks.com>> wrote:
>>>>>>
>>>>>> However, when I look at our commit log and CHANGES.txt, I found
>>> something we are missing:
>>>>>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1
>>> tag.
>>>>>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>>>>>
>>>>
>>>
>>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Varun Vasudev <vv...@apache.org>.
+1 on cherry-picking the fixes into 2.7.2.
-Varun
On 12/25/15, 9:08 AM, "Akira AJISAKA" <aj...@oss.nttdata.co.jp> wrote:
>Thanks Vinod for starting the discussion.
>I'm +1 for cherry-picking these issues to 2.7.2.
>
>As Andrew said, when users upgrade Hadoop from 2.6.3 to 2.7.2,
>they can hit the issues.
>I'm thinking we should reduce the regressions as possible.
>
>Regards,
>Akira
>
>On 12/25/15 01:56, Andrew Wang wrote:
>> My 2c is that we should have monotonicity in releases. That way no
>> "upgrade" is a regression.
>>
>> On Wed, Dec 23, 2015 at 10:00 PM, Tsuyoshi Ozawa <oz...@apache.org> wrote:
>>
>>> Hi Vinod,
>>>
>>> thank you for the clarification.
>>>
>>>> - Pull these 16 tickets into 2.7.2 and roll a new RC
>>>>> What do people think? Do folks expect “any fix in 2.6.3 to be there in
>>> all releases that get out after 2.6.3 release date (December 16th)”?
>>>
>>> I personally prefer to pull these tickets into 2.7.2 since it's
>>> intuitive for me. I can help to cherrypick these tickets into 2.7.2
>>> once we decide to do so.
>>>
>>> This conflicts happened since the the timings of cutting branches and
>>> actual release are crossed. We can face these situations usually in
>>> the future since we have 2 or more branches for stable releases.
>>> Hence, it's a good time to decide basic policy now.
>>>
>>> BTW, should we start to discuss on new thread or continue to discuss here?
>>>
>>> Thanks,
>>> - Tsuyoshi
>>>
>>> On Thu, Dec 24, 2015 at 9:47 AM, Vinod Kumar Vavilapalli
>>> <vi...@apache.org> wrote:
>>>> I retract my -1. I think we will need to discuss this a bit more.
>>>>
>>>> Beyond those two tickets, there are a bunch more (totaling to 16) that
>>> are in 2.6.3 but *not* in 2.7.2. See this:
>>> https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0
>>> <
>>> https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0
>>>>
>>>>
>>>> Two options here, depending on the importance of ‘causality' between
>>> 2.6.x and 2.7.x lines.
>>>> - Ship 2.7.2 as we voted on here
>>>> - Pull these 16 tickets into 2.7.2 and roll a new RC
>>>>
>>>> What do people think? Do folks expect “any fix in 2.6.3 to be there in
>>> all releases that get out after 2.6.3 release date (December 16th)”?
>>>>
>>>> Thanks
>>>> +Vinod
>>>>
>>>>> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <
>>> vinodkv@apache.org> wrote:
>>>>>
>>>>> Sigh. Missed this.
>>>>>
>>>>> To retain causality ("any fix in 2.6.3 will be there in all releases
>>> that got out after 2.6.3”), I’ll get these patches in.
>>>>>
>>>>> Reverting my +1, and casting -1 for the RC myself.
>>>>>
>>>>> Will spin a new RC, this voting thread is marked dead.
>>>>>
>>>>> Thanks
>>>>> +Vinod
>>>>>
>>>>>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com <mailto:
>>> jdu@hortonworks.com>> wrote:
>>>>>>
>>>>>> However, when I look at our commit log and CHANGES.txt, I found
>>> something we are missing:
>>>>>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1
>>> tag.
>>>>>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>>>>>
>>>>
>>>
>>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Varun Vasudev <vv...@apache.org>.
+1 on cherry-picking the fixes into 2.7.2.
-Varun
On 12/25/15, 9:08 AM, "Akira AJISAKA" <aj...@oss.nttdata.co.jp> wrote:
>Thanks Vinod for starting the discussion.
>I'm +1 for cherry-picking these issues to 2.7.2.
>
>As Andrew said, when users upgrade Hadoop from 2.6.3 to 2.7.2,
>they can hit the issues.
>I'm thinking we should reduce the regressions as possible.
>
>Regards,
>Akira
>
>On 12/25/15 01:56, Andrew Wang wrote:
>> My 2c is that we should have monotonicity in releases. That way no
>> "upgrade" is a regression.
>>
>> On Wed, Dec 23, 2015 at 10:00 PM, Tsuyoshi Ozawa <oz...@apache.org> wrote:
>>
>>> Hi Vinod,
>>>
>>> thank you for the clarification.
>>>
>>>> - Pull these 16 tickets into 2.7.2 and roll a new RC
>>>>> What do people think? Do folks expect “any fix in 2.6.3 to be there in
>>> all releases that get out after 2.6.3 release date (December 16th)”?
>>>
>>> I personally prefer to pull these tickets into 2.7.2 since it's
>>> intuitive for me. I can help to cherrypick these tickets into 2.7.2
>>> once we decide to do so.
>>>
>>> This conflicts happened since the the timings of cutting branches and
>>> actual release are crossed. We can face these situations usually in
>>> the future since we have 2 or more branches for stable releases.
>>> Hence, it's a good time to decide basic policy now.
>>>
>>> BTW, should we start to discuss on new thread or continue to discuss here?
>>>
>>> Thanks,
>>> - Tsuyoshi
>>>
>>> On Thu, Dec 24, 2015 at 9:47 AM, Vinod Kumar Vavilapalli
>>> <vi...@apache.org> wrote:
>>>> I retract my -1. I think we will need to discuss this a bit more.
>>>>
>>>> Beyond those two tickets, there are a bunch more (totaling to 16) that
>>> are in 2.6.3 but *not* in 2.7.2. See this:
>>> https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0
>>> <
>>> https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0
>>>>
>>>>
>>>> Two options here, depending on the importance of ‘causality' between
>>> 2.6.x and 2.7.x lines.
>>>> - Ship 2.7.2 as we voted on here
>>>> - Pull these 16 tickets into 2.7.2 and roll a new RC
>>>>
>>>> What do people think? Do folks expect “any fix in 2.6.3 to be there in
>>> all releases that get out after 2.6.3 release date (December 16th)”?
>>>>
>>>> Thanks
>>>> +Vinod
>>>>
>>>>> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <
>>> vinodkv@apache.org> wrote:
>>>>>
>>>>> Sigh. Missed this.
>>>>>
>>>>> To retain causality ("any fix in 2.6.3 will be there in all releases
>>> that got out after 2.6.3”), I’ll get these patches in.
>>>>>
>>>>> Reverting my +1, and casting -1 for the RC myself.
>>>>>
>>>>> Will spin a new RC, this voting thread is marked dead.
>>>>>
>>>>> Thanks
>>>>> +Vinod
>>>>>
>>>>>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com <mailto:
>>> jdu@hortonworks.com>> wrote:
>>>>>>
>>>>>> However, when I look at our commit log and CHANGES.txt, I found
>>> something we are missing:
>>>>>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1
>>> tag.
>>>>>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>>>>>
>>>>
>>>
>>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Varun Vasudev <vv...@apache.org>.
+1 on cherry-picking the fixes into 2.7.2.
-Varun
On 12/25/15, 9:08 AM, "Akira AJISAKA" <aj...@oss.nttdata.co.jp> wrote:
>Thanks Vinod for starting the discussion.
>I'm +1 for cherry-picking these issues to 2.7.2.
>
>As Andrew said, when users upgrade Hadoop from 2.6.3 to 2.7.2,
>they can hit the issues.
>I'm thinking we should reduce the regressions as possible.
>
>Regards,
>Akira
>
>On 12/25/15 01:56, Andrew Wang wrote:
>> My 2c is that we should have monotonicity in releases. That way no
>> "upgrade" is a regression.
>>
>> On Wed, Dec 23, 2015 at 10:00 PM, Tsuyoshi Ozawa <oz...@apache.org> wrote:
>>
>>> Hi Vinod,
>>>
>>> thank you for the clarification.
>>>
>>>> - Pull these 16 tickets into 2.7.2 and roll a new RC
>>>>> What do people think? Do folks expect “any fix in 2.6.3 to be there in
>>> all releases that get out after 2.6.3 release date (December 16th)”?
>>>
>>> I personally prefer to pull these tickets into 2.7.2 since it's
>>> intuitive for me. I can help to cherrypick these tickets into 2.7.2
>>> once we decide to do so.
>>>
>>> This conflicts happened since the the timings of cutting branches and
>>> actual release are crossed. We can face these situations usually in
>>> the future since we have 2 or more branches for stable releases.
>>> Hence, it's a good time to decide basic policy now.
>>>
>>> BTW, should we start to discuss on new thread or continue to discuss here?
>>>
>>> Thanks,
>>> - Tsuyoshi
>>>
>>> On Thu, Dec 24, 2015 at 9:47 AM, Vinod Kumar Vavilapalli
>>> <vi...@apache.org> wrote:
>>>> I retract my -1. I think we will need to discuss this a bit more.
>>>>
>>>> Beyond those two tickets, there are a bunch more (totaling to 16) that
>>> are in 2.6.3 but *not* in 2.7.2. See this:
>>> https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0
>>> <
>>> https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0
>>>>
>>>>
>>>> Two options here, depending on the importance of ‘causality' between
>>> 2.6.x and 2.7.x lines.
>>>> - Ship 2.7.2 as we voted on here
>>>> - Pull these 16 tickets into 2.7.2 and roll a new RC
>>>>
>>>> What do people think? Do folks expect “any fix in 2.6.3 to be there in
>>> all releases that get out after 2.6.3 release date (December 16th)”?
>>>>
>>>> Thanks
>>>> +Vinod
>>>>
>>>>> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <
>>> vinodkv@apache.org> wrote:
>>>>>
>>>>> Sigh. Missed this.
>>>>>
>>>>> To retain causality ("any fix in 2.6.3 will be there in all releases
>>> that got out after 2.6.3”), I’ll get these patches in.
>>>>>
>>>>> Reverting my +1, and casting -1 for the RC myself.
>>>>>
>>>>> Will spin a new RC, this voting thread is marked dead.
>>>>>
>>>>> Thanks
>>>>> +Vinod
>>>>>
>>>>>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com <mailto:
>>> jdu@hortonworks.com>> wrote:
>>>>>>
>>>>>> However, when I look at our commit log and CHANGES.txt, I found
>>> something we are missing:
>>>>>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1
>>> tag.
>>>>>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>>>>>
>>>>
>>>
>>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Akira AJISAKA <aj...@oss.nttdata.co.jp>.
Thanks Vinod for starting the discussion.
I'm +1 for cherry-picking these issues to 2.7.2.
As Andrew said, when users upgrade Hadoop from 2.6.3 to 2.7.2,
they can hit the issues.
I'm thinking we should reduce the regressions as possible.
Regards,
Akira
On 12/25/15 01:56, Andrew Wang wrote:
> My 2c is that we should have monotonicity in releases. That way no
> "upgrade" is a regression.
>
> On Wed, Dec 23, 2015 at 10:00 PM, Tsuyoshi Ozawa <oz...@apache.org> wrote:
>
>> Hi Vinod,
>>
>> thank you for the clarification.
>>
>>> - Pull these 16 tickets into 2.7.2 and roll a new RC
>>>> What do people think? Do folks expect “any fix in 2.6.3 to be there in
>> all releases that get out after 2.6.3 release date (December 16th)”?
>>
>> I personally prefer to pull these tickets into 2.7.2 since it's
>> intuitive for me. I can help to cherrypick these tickets into 2.7.2
>> once we decide to do so.
>>
>> This conflicts happened since the the timings of cutting branches and
>> actual release are crossed. We can face these situations usually in
>> the future since we have 2 or more branches for stable releases.
>> Hence, it's a good time to decide basic policy now.
>>
>> BTW, should we start to discuss on new thread or continue to discuss here?
>>
>> Thanks,
>> - Tsuyoshi
>>
>> On Thu, Dec 24, 2015 at 9:47 AM, Vinod Kumar Vavilapalli
>> <vi...@apache.org> wrote:
>>> I retract my -1. I think we will need to discuss this a bit more.
>>>
>>> Beyond those two tickets, there are a bunch more (totaling to 16) that
>> are in 2.6.3 but *not* in 2.7.2. See this:
>> https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0
>> <
>> https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0
>>>
>>>
>>> Two options here, depending on the importance of ‘causality' between
>> 2.6.x and 2.7.x lines.
>>> - Ship 2.7.2 as we voted on here
>>> - Pull these 16 tickets into 2.7.2 and roll a new RC
>>>
>>> What do people think? Do folks expect “any fix in 2.6.3 to be there in
>> all releases that get out after 2.6.3 release date (December 16th)”?
>>>
>>> Thanks
>>> +Vinod
>>>
>>>> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <
>> vinodkv@apache.org> wrote:
>>>>
>>>> Sigh. Missed this.
>>>>
>>>> To retain causality ("any fix in 2.6.3 will be there in all releases
>> that got out after 2.6.3”), I’ll get these patches in.
>>>>
>>>> Reverting my +1, and casting -1 for the RC myself.
>>>>
>>>> Will spin a new RC, this voting thread is marked dead.
>>>>
>>>> Thanks
>>>> +Vinod
>>>>
>>>>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com <mailto:
>> jdu@hortonworks.com>> wrote:
>>>>>
>>>>> However, when I look at our commit log and CHANGES.txt, I found
>> something we are missing:
>>>>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1
>> tag.
>>>>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>>>>
>>>
>>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Akira AJISAKA <aj...@oss.nttdata.co.jp>.
Thanks Vinod for starting the discussion.
I'm +1 for cherry-picking these issues to 2.7.2.
As Andrew said, when users upgrade Hadoop from 2.6.3 to 2.7.2,
they can hit the issues.
I'm thinking we should reduce the regressions as possible.
Regards,
Akira
On 12/25/15 01:56, Andrew Wang wrote:
> My 2c is that we should have monotonicity in releases. That way no
> "upgrade" is a regression.
>
> On Wed, Dec 23, 2015 at 10:00 PM, Tsuyoshi Ozawa <oz...@apache.org> wrote:
>
>> Hi Vinod,
>>
>> thank you for the clarification.
>>
>>> - Pull these 16 tickets into 2.7.2 and roll a new RC
>>>> What do people think? Do folks expect “any fix in 2.6.3 to be there in
>> all releases that get out after 2.6.3 release date (December 16th)”?
>>
>> I personally prefer to pull these tickets into 2.7.2 since it's
>> intuitive for me. I can help to cherrypick these tickets into 2.7.2
>> once we decide to do so.
>>
>> This conflicts happened since the the timings of cutting branches and
>> actual release are crossed. We can face these situations usually in
>> the future since we have 2 or more branches for stable releases.
>> Hence, it's a good time to decide basic policy now.
>>
>> BTW, should we start to discuss on new thread or continue to discuss here?
>>
>> Thanks,
>> - Tsuyoshi
>>
>> On Thu, Dec 24, 2015 at 9:47 AM, Vinod Kumar Vavilapalli
>> <vi...@apache.org> wrote:
>>> I retract my -1. I think we will need to discuss this a bit more.
>>>
>>> Beyond those two tickets, there are a bunch more (totaling to 16) that
>> are in 2.6.3 but *not* in 2.7.2. See this:
>> https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0
>> <
>> https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0
>>>
>>>
>>> Two options here, depending on the importance of ‘causality' between
>> 2.6.x and 2.7.x lines.
>>> - Ship 2.7.2 as we voted on here
>>> - Pull these 16 tickets into 2.7.2 and roll a new RC
>>>
>>> What do people think? Do folks expect “any fix in 2.6.3 to be there in
>> all releases that get out after 2.6.3 release date (December 16th)”?
>>>
>>> Thanks
>>> +Vinod
>>>
>>>> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <
>> vinodkv@apache.org> wrote:
>>>>
>>>> Sigh. Missed this.
>>>>
>>>> To retain causality ("any fix in 2.6.3 will be there in all releases
>> that got out after 2.6.3”), I’ll get these patches in.
>>>>
>>>> Reverting my +1, and casting -1 for the RC myself.
>>>>
>>>> Will spin a new RC, this voting thread is marked dead.
>>>>
>>>> Thanks
>>>> +Vinod
>>>>
>>>>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com <mailto:
>> jdu@hortonworks.com>> wrote:
>>>>>
>>>>> However, when I look at our commit log and CHANGES.txt, I found
>> something we are missing:
>>>>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1
>> tag.
>>>>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>>>>
>>>
>>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Akira AJISAKA <aj...@oss.nttdata.co.jp>.
Thanks Vinod for starting the discussion.
I'm +1 for cherry-picking these issues to 2.7.2.
As Andrew said, when users upgrade Hadoop from 2.6.3 to 2.7.2,
they can hit the issues.
I'm thinking we should reduce the regressions as possible.
Regards,
Akira
On 12/25/15 01:56, Andrew Wang wrote:
> My 2c is that we should have monotonicity in releases. That way no
> "upgrade" is a regression.
>
> On Wed, Dec 23, 2015 at 10:00 PM, Tsuyoshi Ozawa <oz...@apache.org> wrote:
>
>> Hi Vinod,
>>
>> thank you for the clarification.
>>
>>> - Pull these 16 tickets into 2.7.2 and roll a new RC
>>>> What do people think? Do folks expect “any fix in 2.6.3 to be there in
>> all releases that get out after 2.6.3 release date (December 16th)”?
>>
>> I personally prefer to pull these tickets into 2.7.2 since it's
>> intuitive for me. I can help to cherrypick these tickets into 2.7.2
>> once we decide to do so.
>>
>> This conflicts happened since the the timings of cutting branches and
>> actual release are crossed. We can face these situations usually in
>> the future since we have 2 or more branches for stable releases.
>> Hence, it's a good time to decide basic policy now.
>>
>> BTW, should we start to discuss on new thread or continue to discuss here?
>>
>> Thanks,
>> - Tsuyoshi
>>
>> On Thu, Dec 24, 2015 at 9:47 AM, Vinod Kumar Vavilapalli
>> <vi...@apache.org> wrote:
>>> I retract my -1. I think we will need to discuss this a bit more.
>>>
>>> Beyond those two tickets, there are a bunch more (totaling to 16) that
>> are in 2.6.3 but *not* in 2.7.2. See this:
>> https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0
>> <
>> https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0
>>>
>>>
>>> Two options here, depending on the importance of ‘causality' between
>> 2.6.x and 2.7.x lines.
>>> - Ship 2.7.2 as we voted on here
>>> - Pull these 16 tickets into 2.7.2 and roll a new RC
>>>
>>> What do people think? Do folks expect “any fix in 2.6.3 to be there in
>> all releases that get out after 2.6.3 release date (December 16th)”?
>>>
>>> Thanks
>>> +Vinod
>>>
>>>> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <
>> vinodkv@apache.org> wrote:
>>>>
>>>> Sigh. Missed this.
>>>>
>>>> To retain causality ("any fix in 2.6.3 will be there in all releases
>> that got out after 2.6.3”), I’ll get these patches in.
>>>>
>>>> Reverting my +1, and casting -1 for the RC myself.
>>>>
>>>> Will spin a new RC, this voting thread is marked dead.
>>>>
>>>> Thanks
>>>> +Vinod
>>>>
>>>>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com <mailto:
>> jdu@hortonworks.com>> wrote:
>>>>>
>>>>> However, when I look at our commit log and CHANGES.txt, I found
>> something we are missing:
>>>>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1
>> tag.
>>>>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>>>>
>>>
>>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Akira AJISAKA <aj...@oss.nttdata.co.jp>.
Thanks Vinod for starting the discussion.
I'm +1 for cherry-picking these issues to 2.7.2.
As Andrew said, when users upgrade Hadoop from 2.6.3 to 2.7.2,
they can hit the issues.
I'm thinking we should reduce the regressions as possible.
Regards,
Akira
On 12/25/15 01:56, Andrew Wang wrote:
> My 2c is that we should have monotonicity in releases. That way no
> "upgrade" is a regression.
>
> On Wed, Dec 23, 2015 at 10:00 PM, Tsuyoshi Ozawa <oz...@apache.org> wrote:
>
>> Hi Vinod,
>>
>> thank you for the clarification.
>>
>>> - Pull these 16 tickets into 2.7.2 and roll a new RC
>>>> What do people think? Do folks expect “any fix in 2.6.3 to be there in
>> all releases that get out after 2.6.3 release date (December 16th)”?
>>
>> I personally prefer to pull these tickets into 2.7.2 since it's
>> intuitive for me. I can help to cherrypick these tickets into 2.7.2
>> once we decide to do so.
>>
>> This conflicts happened since the the timings of cutting branches and
>> actual release are crossed. We can face these situations usually in
>> the future since we have 2 or more branches for stable releases.
>> Hence, it's a good time to decide basic policy now.
>>
>> BTW, should we start to discuss on new thread or continue to discuss here?
>>
>> Thanks,
>> - Tsuyoshi
>>
>> On Thu, Dec 24, 2015 at 9:47 AM, Vinod Kumar Vavilapalli
>> <vi...@apache.org> wrote:
>>> I retract my -1. I think we will need to discuss this a bit more.
>>>
>>> Beyond those two tickets, there are a bunch more (totaling to 16) that
>> are in 2.6.3 but *not* in 2.7.2. See this:
>> https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0
>> <
>> https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0
>>>
>>>
>>> Two options here, depending on the importance of ‘causality' between
>> 2.6.x and 2.7.x lines.
>>> - Ship 2.7.2 as we voted on here
>>> - Pull these 16 tickets into 2.7.2 and roll a new RC
>>>
>>> What do people think? Do folks expect “any fix in 2.6.3 to be there in
>> all releases that get out after 2.6.3 release date (December 16th)”?
>>>
>>> Thanks
>>> +Vinod
>>>
>>>> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <
>> vinodkv@apache.org> wrote:
>>>>
>>>> Sigh. Missed this.
>>>>
>>>> To retain causality ("any fix in 2.6.3 will be there in all releases
>> that got out after 2.6.3”), I’ll get these patches in.
>>>>
>>>> Reverting my +1, and casting -1 for the RC myself.
>>>>
>>>> Will spin a new RC, this voting thread is marked dead.
>>>>
>>>> Thanks
>>>> +Vinod
>>>>
>>>>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com <mailto:
>> jdu@hortonworks.com>> wrote:
>>>>>
>>>>> However, when I look at our commit log and CHANGES.txt, I found
>> something we are missing:
>>>>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1
>> tag.
>>>>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>>>>
>>>
>>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Andrew Wang <an...@cloudera.com>.
My 2c is that we should have monotonicity in releases. That way no
"upgrade" is a regression.
On Wed, Dec 23, 2015 at 10:00 PM, Tsuyoshi Ozawa <oz...@apache.org> wrote:
> Hi Vinod,
>
> thank you for the clarification.
>
> > - Pull these 16 tickets into 2.7.2 and roll a new RC
> > > What do people think? Do folks expect “any fix in 2.6.3 to be there in
> all releases that get out after 2.6.3 release date (December 16th)”?
>
> I personally prefer to pull these tickets into 2.7.2 since it's
> intuitive for me. I can help to cherrypick these tickets into 2.7.2
> once we decide to do so.
>
> This conflicts happened since the the timings of cutting branches and
> actual release are crossed. We can face these situations usually in
> the future since we have 2 or more branches for stable releases.
> Hence, it's a good time to decide basic policy now.
>
> BTW, should we start to discuss on new thread or continue to discuss here?
>
> Thanks,
> - Tsuyoshi
>
> On Thu, Dec 24, 2015 at 9:47 AM, Vinod Kumar Vavilapalli
> <vi...@apache.org> wrote:
> > I retract my -1. I think we will need to discuss this a bit more.
> >
> > Beyond those two tickets, there are a bunch more (totaling to 16) that
> are in 2.6.3 but *not* in 2.7.2. See this:
> https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0
> <
> https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0
> >
> >
> > Two options here, depending on the importance of ‘causality' between
> 2.6.x and 2.7.x lines.
> > - Ship 2.7.2 as we voted on here
> > - Pull these 16 tickets into 2.7.2 and roll a new RC
> >
> > What do people think? Do folks expect “any fix in 2.6.3 to be there in
> all releases that get out after 2.6.3 release date (December 16th)”?
> >
> > Thanks
> > +Vinod
> >
> >> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <
> vinodkv@apache.org> wrote:
> >>
> >> Sigh. Missed this.
> >>
> >> To retain causality ("any fix in 2.6.3 will be there in all releases
> that got out after 2.6.3”), I’ll get these patches in.
> >>
> >> Reverting my +1, and casting -1 for the RC myself.
> >>
> >> Will spin a new RC, this voting thread is marked dead.
> >>
> >> Thanks
> >> +Vinod
> >>
> >>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com <mailto:
> jdu@hortonworks.com>> wrote:
> >>>
> >>> However, when I look at our commit log and CHANGES.txt, I found
> something we are missing:
> >>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1
> tag.
> >>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
> >>
> >
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Andrew Wang <an...@cloudera.com>.
My 2c is that we should have monotonicity in releases. That way no
"upgrade" is a regression.
On Wed, Dec 23, 2015 at 10:00 PM, Tsuyoshi Ozawa <oz...@apache.org> wrote:
> Hi Vinod,
>
> thank you for the clarification.
>
> > - Pull these 16 tickets into 2.7.2 and roll a new RC
> > > What do people think? Do folks expect “any fix in 2.6.3 to be there in
> all releases that get out after 2.6.3 release date (December 16th)”?
>
> I personally prefer to pull these tickets into 2.7.2 since it's
> intuitive for me. I can help to cherrypick these tickets into 2.7.2
> once we decide to do so.
>
> This conflicts happened since the the timings of cutting branches and
> actual release are crossed. We can face these situations usually in
> the future since we have 2 or more branches for stable releases.
> Hence, it's a good time to decide basic policy now.
>
> BTW, should we start to discuss on new thread or continue to discuss here?
>
> Thanks,
> - Tsuyoshi
>
> On Thu, Dec 24, 2015 at 9:47 AM, Vinod Kumar Vavilapalli
> <vi...@apache.org> wrote:
> > I retract my -1. I think we will need to discuss this a bit more.
> >
> > Beyond those two tickets, there are a bunch more (totaling to 16) that
> are in 2.6.3 but *not* in 2.7.2. See this:
> https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0
> <
> https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0
> >
> >
> > Two options here, depending on the importance of ‘causality' between
> 2.6.x and 2.7.x lines.
> > - Ship 2.7.2 as we voted on here
> > - Pull these 16 tickets into 2.7.2 and roll a new RC
> >
> > What do people think? Do folks expect “any fix in 2.6.3 to be there in
> all releases that get out after 2.6.3 release date (December 16th)”?
> >
> > Thanks
> > +Vinod
> >
> >> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <
> vinodkv@apache.org> wrote:
> >>
> >> Sigh. Missed this.
> >>
> >> To retain causality ("any fix in 2.6.3 will be there in all releases
> that got out after 2.6.3”), I’ll get these patches in.
> >>
> >> Reverting my +1, and casting -1 for the RC myself.
> >>
> >> Will spin a new RC, this voting thread is marked dead.
> >>
> >> Thanks
> >> +Vinod
> >>
> >>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com <mailto:
> jdu@hortonworks.com>> wrote:
> >>>
> >>> However, when I look at our commit log and CHANGES.txt, I found
> something we are missing:
> >>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1
> tag.
> >>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
> >>
> >
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Andrew Wang <an...@cloudera.com>.
My 2c is that we should have monotonicity in releases. That way no
"upgrade" is a regression.
On Wed, Dec 23, 2015 at 10:00 PM, Tsuyoshi Ozawa <oz...@apache.org> wrote:
> Hi Vinod,
>
> thank you for the clarification.
>
> > - Pull these 16 tickets into 2.7.2 and roll a new RC
> > > What do people think? Do folks expect “any fix in 2.6.3 to be there in
> all releases that get out after 2.6.3 release date (December 16th)”?
>
> I personally prefer to pull these tickets into 2.7.2 since it's
> intuitive for me. I can help to cherrypick these tickets into 2.7.2
> once we decide to do so.
>
> This conflicts happened since the the timings of cutting branches and
> actual release are crossed. We can face these situations usually in
> the future since we have 2 or more branches for stable releases.
> Hence, it's a good time to decide basic policy now.
>
> BTW, should we start to discuss on new thread or continue to discuss here?
>
> Thanks,
> - Tsuyoshi
>
> On Thu, Dec 24, 2015 at 9:47 AM, Vinod Kumar Vavilapalli
> <vi...@apache.org> wrote:
> > I retract my -1. I think we will need to discuss this a bit more.
> >
> > Beyond those two tickets, there are a bunch more (totaling to 16) that
> are in 2.6.3 but *not* in 2.7.2. See this:
> https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0
> <
> https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0
> >
> >
> > Two options here, depending on the importance of ‘causality' between
> 2.6.x and 2.7.x lines.
> > - Ship 2.7.2 as we voted on here
> > - Pull these 16 tickets into 2.7.2 and roll a new RC
> >
> > What do people think? Do folks expect “any fix in 2.6.3 to be there in
> all releases that get out after 2.6.3 release date (December 16th)”?
> >
> > Thanks
> > +Vinod
> >
> >> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <
> vinodkv@apache.org> wrote:
> >>
> >> Sigh. Missed this.
> >>
> >> To retain causality ("any fix in 2.6.3 will be there in all releases
> that got out after 2.6.3”), I’ll get these patches in.
> >>
> >> Reverting my +1, and casting -1 for the RC myself.
> >>
> >> Will spin a new RC, this voting thread is marked dead.
> >>
> >> Thanks
> >> +Vinod
> >>
> >>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com <mailto:
> jdu@hortonworks.com>> wrote:
> >>>
> >>> However, when I look at our commit log and CHANGES.txt, I found
> something we are missing:
> >>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1
> tag.
> >>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
> >>
> >
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Andrew Wang <an...@cloudera.com>.
My 2c is that we should have monotonicity in releases. That way no
"upgrade" is a regression.
On Wed, Dec 23, 2015 at 10:00 PM, Tsuyoshi Ozawa <oz...@apache.org> wrote:
> Hi Vinod,
>
> thank you for the clarification.
>
> > - Pull these 16 tickets into 2.7.2 and roll a new RC
> > > What do people think? Do folks expect “any fix in 2.6.3 to be there in
> all releases that get out after 2.6.3 release date (December 16th)”?
>
> I personally prefer to pull these tickets into 2.7.2 since it's
> intuitive for me. I can help to cherrypick these tickets into 2.7.2
> once we decide to do so.
>
> This conflicts happened since the the timings of cutting branches and
> actual release are crossed. We can face these situations usually in
> the future since we have 2 or more branches for stable releases.
> Hence, it's a good time to decide basic policy now.
>
> BTW, should we start to discuss on new thread or continue to discuss here?
>
> Thanks,
> - Tsuyoshi
>
> On Thu, Dec 24, 2015 at 9:47 AM, Vinod Kumar Vavilapalli
> <vi...@apache.org> wrote:
> > I retract my -1. I think we will need to discuss this a bit more.
> >
> > Beyond those two tickets, there are a bunch more (totaling to 16) that
> are in 2.6.3 but *not* in 2.7.2. See this:
> https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0
> <
> https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0
> >
> >
> > Two options here, depending on the importance of ‘causality' between
> 2.6.x and 2.7.x lines.
> > - Ship 2.7.2 as we voted on here
> > - Pull these 16 tickets into 2.7.2 and roll a new RC
> >
> > What do people think? Do folks expect “any fix in 2.6.3 to be there in
> all releases that get out after 2.6.3 release date (December 16th)”?
> >
> > Thanks
> > +Vinod
> >
> >> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <
> vinodkv@apache.org> wrote:
> >>
> >> Sigh. Missed this.
> >>
> >> To retain causality ("any fix in 2.6.3 will be there in all releases
> that got out after 2.6.3”), I’ll get these patches in.
> >>
> >> Reverting my +1, and casting -1 for the RC myself.
> >>
> >> Will spin a new RC, this voting thread is marked dead.
> >>
> >> Thanks
> >> +Vinod
> >>
> >>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com <mailto:
> jdu@hortonworks.com>> wrote:
> >>>
> >>> However, when I look at our commit log and CHANGES.txt, I found
> something we are missing:
> >>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1
> tag.
> >>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
> >>
> >
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Tsuyoshi Ozawa <oz...@apache.org>.
Hi Vinod,
thank you for the clarification.
> - Pull these 16 tickets into 2.7.2 and roll a new RC
> > What do people think? Do folks expect “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date (December 16th)”?
I personally prefer to pull these tickets into 2.7.2 since it's
intuitive for me. I can help to cherrypick these tickets into 2.7.2
once we decide to do so.
This conflicts happened since the the timings of cutting branches and
actual release are crossed. We can face these situations usually in
the future since we have 2 or more branches for stable releases.
Hence, it's a good time to decide basic policy now.
BTW, should we start to discuss on new thread or continue to discuss here?
Thanks,
- Tsuyoshi
On Thu, Dec 24, 2015 at 9:47 AM, Vinod Kumar Vavilapalli
<vi...@apache.org> wrote:
> I retract my -1. I think we will need to discuss this a bit more.
>
> Beyond those two tickets, there are a bunch more (totaling to 16) that are in 2.6.3 but *not* in 2.7.2. See this: https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0 <https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0>
>
> Two options here, depending on the importance of ‘causality' between 2.6.x and 2.7.x lines.
> - Ship 2.7.2 as we voted on here
> - Pull these 16 tickets into 2.7.2 and roll a new RC
>
> What do people think? Do folks expect “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date (December 16th)”?
>
> Thanks
> +Vinod
>
>> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vi...@apache.org> wrote:
>>
>> Sigh. Missed this.
>>
>> To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in.
>>
>> Reverting my +1, and casting -1 for the RC myself.
>>
>> Will spin a new RC, this voting thread is marked dead.
>>
>> Thanks
>> +Vinod
>>
>>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com <ma...@hortonworks.com>> wrote:
>>>
>>> However, when I look at our commit log and CHANGES.txt, I found something we are missing:
>>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
>>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Tsuyoshi Ozawa <oz...@apache.org>.
Hi Vinod,
thank you for the clarification.
> - Pull these 16 tickets into 2.7.2 and roll a new RC
> > What do people think? Do folks expect “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date (December 16th)”?
I personally prefer to pull these tickets into 2.7.2 since it's
intuitive for me. I can help to cherrypick these tickets into 2.7.2
once we decide to do so.
This conflicts happened since the the timings of cutting branches and
actual release are crossed. We can face these situations usually in
the future since we have 2 or more branches for stable releases.
Hence, it's a good time to decide basic policy now.
BTW, should we start to discuss on new thread or continue to discuss here?
Thanks,
- Tsuyoshi
On Thu, Dec 24, 2015 at 9:47 AM, Vinod Kumar Vavilapalli
<vi...@apache.org> wrote:
> I retract my -1. I think we will need to discuss this a bit more.
>
> Beyond those two tickets, there are a bunch more (totaling to 16) that are in 2.6.3 but *not* in 2.7.2. See this: https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0 <https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0>
>
> Two options here, depending on the importance of ‘causality' between 2.6.x and 2.7.x lines.
> - Ship 2.7.2 as we voted on here
> - Pull these 16 tickets into 2.7.2 and roll a new RC
>
> What do people think? Do folks expect “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date (December 16th)”?
>
> Thanks
> +Vinod
>
>> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vi...@apache.org> wrote:
>>
>> Sigh. Missed this.
>>
>> To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in.
>>
>> Reverting my +1, and casting -1 for the RC myself.
>>
>> Will spin a new RC, this voting thread is marked dead.
>>
>> Thanks
>> +Vinod
>>
>>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com <ma...@hortonworks.com>> wrote:
>>>
>>> However, when I look at our commit log and CHANGES.txt, I found something we are missing:
>>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
>>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Tsuyoshi Ozawa <oz...@apache.org>.
Hi Vinod,
thank you for the clarification.
> - Pull these 16 tickets into 2.7.2 and roll a new RC
> > What do people think? Do folks expect “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date (December 16th)”?
I personally prefer to pull these tickets into 2.7.2 since it's
intuitive for me. I can help to cherrypick these tickets into 2.7.2
once we decide to do so.
This conflicts happened since the the timings of cutting branches and
actual release are crossed. We can face these situations usually in
the future since we have 2 or more branches for stable releases.
Hence, it's a good time to decide basic policy now.
BTW, should we start to discuss on new thread or continue to discuss here?
Thanks,
- Tsuyoshi
On Thu, Dec 24, 2015 at 9:47 AM, Vinod Kumar Vavilapalli
<vi...@apache.org> wrote:
> I retract my -1. I think we will need to discuss this a bit more.
>
> Beyond those two tickets, there are a bunch more (totaling to 16) that are in 2.6.3 but *not* in 2.7.2. See this: https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0 <https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0>
>
> Two options here, depending on the importance of ‘causality' between 2.6.x and 2.7.x lines.
> - Ship 2.7.2 as we voted on here
> - Pull these 16 tickets into 2.7.2 and roll a new RC
>
> What do people think? Do folks expect “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date (December 16th)”?
>
> Thanks
> +Vinod
>
>> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vi...@apache.org> wrote:
>>
>> Sigh. Missed this.
>>
>> To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in.
>>
>> Reverting my +1, and casting -1 for the RC myself.
>>
>> Will spin a new RC, this voting thread is marked dead.
>>
>> Thanks
>> +Vinod
>>
>>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com <ma...@hortonworks.com>> wrote:
>>>
>>> However, when I look at our commit log and CHANGES.txt, I found something we are missing:
>>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
>>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Tsuyoshi Ozawa <oz...@apache.org>.
Hi Vinod,
thank you for the clarification.
> - Pull these 16 tickets into 2.7.2 and roll a new RC
> > What do people think? Do folks expect “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date (December 16th)”?
I personally prefer to pull these tickets into 2.7.2 since it's
intuitive for me. I can help to cherrypick these tickets into 2.7.2
once we decide to do so.
This conflicts happened since the the timings of cutting branches and
actual release are crossed. We can face these situations usually in
the future since we have 2 or more branches for stable releases.
Hence, it's a good time to decide basic policy now.
BTW, should we start to discuss on new thread or continue to discuss here?
Thanks,
- Tsuyoshi
On Thu, Dec 24, 2015 at 9:47 AM, Vinod Kumar Vavilapalli
<vi...@apache.org> wrote:
> I retract my -1. I think we will need to discuss this a bit more.
>
> Beyond those two tickets, there are a bunch more (totaling to 16) that are in 2.6.3 but *not* in 2.7.2. See this: https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0 <https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0>
>
> Two options here, depending on the importance of ‘causality' between 2.6.x and 2.7.x lines.
> - Ship 2.7.2 as we voted on here
> - Pull these 16 tickets into 2.7.2 and roll a new RC
>
> What do people think? Do folks expect “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date (December 16th)”?
>
> Thanks
> +Vinod
>
>> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vi...@apache.org> wrote:
>>
>> Sigh. Missed this.
>>
>> To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in.
>>
>> Reverting my +1, and casting -1 for the RC myself.
>>
>> Will spin a new RC, this voting thread is marked dead.
>>
>> Thanks
>> +Vinod
>>
>>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com <ma...@hortonworks.com>> wrote:
>>>
>>> However, when I look at our commit log and CHANGES.txt, I found something we are missing:
>>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
>>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Junping Du <jd...@hortonworks.com>.
I am +1 with pulling all of these tickets into 2.7.2.
- For “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date”
Shall we conclude this as a general rule - "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that get out after 2.x.y release date"? I am generally fine with this, but just feel it sounds to set too strong restrictions among branches. Some fixes could be trivial (test case fix, etc.) enough to deserve more flexibility. I would prefer this rule only applies on critical/blocker fixes, but not applies on minor/trivial issues.
Just 2 cents.
Thanks,
Junping
________________________________
From: Vinod Kumar Vavilapalli <vi...@apache.org>
Sent: Thursday, December 24, 2015 12:47 AM
To: Junping Du
Cc: mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org
Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
I retract my -1. I think we will need to discuss this a bit more.
Beyond those two tickets, there are a bunch more (totaling to 16) that are in 2.6.3 but *not* in 2.7.2. See this: https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0<https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0>
Two options here, depending on the importance of ‘causality' between 2.6.x and 2.7.x lines.
- Ship 2.7.2 as we voted on here
- Pull these 16 tickets into 2.7.2 and roll a new RC
What do people think? Do folks expect “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date (December 16th)”?
Thanks
+Vinod
On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vi...@apache.org>> wrote:
Sigh. Missed this.
To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in.
Reverting my +1, and casting -1 for the RC myself.
Will spin a new RC, this voting thread is marked dead.
Thanks
+Vinod
On Dec 22, 2015, at 8:24 AM, Junping Du <jd...@hortonworks.com>> wrote:
However, when I look at our commit log and CHANGES.txt, I found something we are missing:
1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Junping Du <jd...@hortonworks.com>.
I am +1 with pulling all of these tickets into 2.7.2.
- For “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date”
Shall we conclude this as a general rule - "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that get out after 2.x.y release date"? I am generally fine with this, but just feel it sounds to set too strong restrictions among branches. Some fixes could be trivial (test case fix, etc.) enough to deserve more flexibility. I would prefer this rule only applies on critical/blocker fixes, but not applies on minor/trivial issues.
Just 2 cents.
Thanks,
Junping
________________________________
From: Vinod Kumar Vavilapalli <vi...@apache.org>
Sent: Thursday, December 24, 2015 12:47 AM
To: Junping Du
Cc: mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org
Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
I retract my -1. I think we will need to discuss this a bit more.
Beyond those two tickets, there are a bunch more (totaling to 16) that are in 2.6.3 but *not* in 2.7.2. See this: https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0<https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0>
Two options here, depending on the importance of ‘causality' between 2.6.x and 2.7.x lines.
- Ship 2.7.2 as we voted on here
- Pull these 16 tickets into 2.7.2 and roll a new RC
What do people think? Do folks expect “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date (December 16th)”?
Thanks
+Vinod
On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vi...@apache.org>> wrote:
Sigh. Missed this.
To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in.
Reverting my +1, and casting -1 for the RC myself.
Will spin a new RC, this voting thread is marked dead.
Thanks
+Vinod
On Dec 22, 2015, at 8:24 AM, Junping Du <jd...@hortonworks.com>> wrote:
However, when I look at our commit log and CHANGES.txt, I found something we are missing:
1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Junping Du <jd...@hortonworks.com>.
I am +1 with pulling all of these tickets into 2.7.2.
- For “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date”
Shall we conclude this as a general rule - "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that get out after 2.x.y release date"? I am generally fine with this, but just feel it sounds to set too strong restrictions among branches. Some fixes could be trivial (test case fix, etc.) enough to deserve more flexibility. I would prefer this rule only applies on critical/blocker fixes, but not applies on minor/trivial issues.
Just 2 cents.
Thanks,
Junping
________________________________
From: Vinod Kumar Vavilapalli <vi...@apache.org>
Sent: Thursday, December 24, 2015 12:47 AM
To: Junping Du
Cc: mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org
Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
I retract my -1. I think we will need to discuss this a bit more.
Beyond those two tickets, there are a bunch more (totaling to 16) that are in 2.6.3 but *not* in 2.7.2. See this: https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0<https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0>
Two options here, depending on the importance of ‘causality' between 2.6.x and 2.7.x lines.
- Ship 2.7.2 as we voted on here
- Pull these 16 tickets into 2.7.2 and roll a new RC
What do people think? Do folks expect “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date (December 16th)”?
Thanks
+Vinod
On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vi...@apache.org>> wrote:
Sigh. Missed this.
To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in.
Reverting my +1, and casting -1 for the RC myself.
Will spin a new RC, this voting thread is marked dead.
Thanks
+Vinod
On Dec 22, 2015, at 8:24 AM, Junping Du <jd...@hortonworks.com>> wrote:
However, when I look at our commit log and CHANGES.txt, I found something we are missing:
1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
I retract my -1. I think we will need to discuss this a bit more.
Beyond those two tickets, there are a bunch more (totaling to 16) that are in 2.6.3 but *not* in 2.7.2. See this: https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0 <https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0>
Two options here, depending on the importance of ‘causality' between 2.6.x and 2.7.x lines.
- Ship 2.7.2 as we voted on here
- Pull these 16 tickets into 2.7.2 and roll a new RC
What do people think? Do folks expect “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date (December 16th)”?
Thanks
+Vinod
> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vi...@apache.org> wrote:
>
> Sigh. Missed this.
>
> To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in.
>
> Reverting my +1, and casting -1 for the RC myself.
>
> Will spin a new RC, this voting thread is marked dead.
>
> Thanks
> +Vinod
>
>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com <ma...@hortonworks.com>> wrote:
>>
>> However, when I look at our commit log and CHANGES.txt, I found something we are missing:
>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
I retract my -1. I think we will need to discuss this a bit more.
Beyond those two tickets, there are a bunch more (totaling to 16) that are in 2.6.3 but *not* in 2.7.2. See this: https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0 <https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0>
Two options here, depending on the importance of ‘causality' between 2.6.x and 2.7.x lines.
- Ship 2.7.2 as we voted on here
- Pull these 16 tickets into 2.7.2 and roll a new RC
What do people think? Do folks expect “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date (December 16th)”?
Thanks
+Vinod
> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vi...@apache.org> wrote:
>
> Sigh. Missed this.
>
> To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in.
>
> Reverting my +1, and casting -1 for the RC myself.
>
> Will spin a new RC, this voting thread is marked dead.
>
> Thanks
> +Vinod
>
>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com <ma...@hortonworks.com>> wrote:
>>
>> However, when I look at our commit log and CHANGES.txt, I found something we are missing:
>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
I retract my -1. I think we will need to discuss this a bit more.
Beyond those two tickets, there are a bunch more (totaling to 16) that are in 2.6.3 but *not* in 2.7.2. See this: https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0 <https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0>
Two options here, depending on the importance of ‘causality' between 2.6.x and 2.7.x lines.
- Ship 2.7.2 as we voted on here
- Pull these 16 tickets into 2.7.2 and roll a new RC
What do people think? Do folks expect “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date (December 16th)”?
Thanks
+Vinod
> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vi...@apache.org> wrote:
>
> Sigh. Missed this.
>
> To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in.
>
> Reverting my +1, and casting -1 for the RC myself.
>
> Will spin a new RC, this voting thread is marked dead.
>
> Thanks
> +Vinod
>
>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com <ma...@hortonworks.com>> wrote:
>>
>> However, when I look at our commit log and CHANGES.txt, I found something we are missing:
>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
I retract my -1. I think we will need to discuss this a bit more.
Beyond those two tickets, there are a bunch more (totaling to 16) that are in 2.6.3 but *not* in 2.7.2. See this: https://issues.apache.org/jira/issues/?jql=key%20in%20%28HADOOP-12526%2CHADOOP-12413%2CHADOOP-11267%2CHADOOP-10668%2CHADOOP-10134%2CYARN-4434%2CYARN-4365%2CYARN-4348%2CYARN-4344%2CYARN-4326%2CYARN-4241%2CYARN-2859%2CMAPREDUCE-6549%2CMAPREDUCE-6540%2CMAPREDUCE-6377%2CMAPREDUCE-5883%2CHDFS-9431%2CHDFS-9289%2CHDFS-8615%29%20and%20fixVersion%20!%3D%202.7.0 <https://issues.apache.org/jira/issues/?jql=key%20in%20(HADOOP-12526,HADOOP-12413,HADOOP-11267,HADOOP-10668,HADOOP-10134,YARN-4434,YARN-4365,YARN-4348,YARN-4344,YARN-4326,YARN-4241,YARN-2859,MAPREDUCE-6549,MAPREDUCE-6540,MAPREDUCE-6377,MAPREDUCE-5883,HDFS-9431,HDFS-9289,HDFS-8615)%20and%20fixVersion%20!=%202.7.0>
Two options here, depending on the importance of ‘causality' between 2.6.x and 2.7.x lines.
- Ship 2.7.2 as we voted on here
- Pull these 16 tickets into 2.7.2 and roll a new RC
What do people think? Do folks expect “any fix in 2.6.3 to be there in all releases that get out after 2.6.3 release date (December 16th)”?
Thanks
+Vinod
> On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vi...@apache.org> wrote:
>
> Sigh. Missed this.
>
> To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in.
>
> Reverting my +1, and casting -1 for the RC myself.
>
> Will spin a new RC, this voting thread is marked dead.
>
> Thanks
> +Vinod
>
>> On Dec 22, 2015, at 8:24 AM, Junping Du <jdu@hortonworks.com <ma...@hortonworks.com>> wrote:
>>
>> However, when I look at our commit log and CHANGES.txt, I found something we are missing:
>> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
>> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
Sigh. Missed this.
To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in.
Reverting my +1, and casting -1 for the RC myself.
Will spin a new RC, this voting thread is marked dead.
Thanks
+Vinod
> On Dec 22, 2015, at 8:24 AM, Junping Du <jd...@hortonworks.com> wrote:
>
> However, when I look at our commit log and CHANGES.txt, I found something we are missing:
> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
Sigh. Missed this.
To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in.
Reverting my +1, and casting -1 for the RC myself.
Will spin a new RC, this voting thread is marked dead.
Thanks
+Vinod
> On Dec 22, 2015, at 8:24 AM, Junping Du <jd...@hortonworks.com> wrote:
>
> However, when I look at our commit log and CHANGES.txt, I found something we are missing:
> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
Sigh. Missed this.
To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in.
Reverting my +1, and casting -1 for the RC myself.
Will spin a new RC, this voting thread is marked dead.
Thanks
+Vinod
> On Dec 22, 2015, at 8:24 AM, Junping Du <jd...@hortonworks.com> wrote:
>
> However, when I look at our commit log and CHANGES.txt, I found something we are missing:
> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
Sigh. Missed this.
To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in.
Reverting my +1, and casting -1 for the RC myself.
Will spin a new RC, this voting thread is marked dead.
Thanks
+Vinod
> On Dec 22, 2015, at 8:24 AM, Junping Du <jd...@hortonworks.com> wrote:
>
> However, when I look at our commit log and CHANGES.txt, I found something we are missing:
> 1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
> 2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Junping Du <jd...@hortonworks.com>.
Checked 2.7.2-RC1 tag which match exactly with 2.7.2 branch.
Downloaded the release bit and deploy a single node cluster which works fine with running some example jobs.
Built from src and check signatures, all looks good.
Checked release note which has 138 commits (HADOOP:22, HDFS:42, MAPREDUCE:17, YARN:57) match exactly with JIRA fixed list in 2.7.2.
However, when I look at our commit log and CHANGES.txt, I found something we are missing:
1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
For 2, I think we can fix in creating the final tag. For 1, I will let release manager to decide if HDFS-9470 & YARN-4424 has to go to 2.7.2. If not, I will +1 and we can fix release notes later.
Thanks,
Junping
________________________________________
From: Chang Li <li...@gmail.com>
Sent: Tuesday, December 22, 2015 2:35 PM
To: mapreduce-dev@hadoop.apache.org
Cc: common-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org; Vinod Kumar Vavilapalli
Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
+1 (non binding)
Downloaed src and built on single node cluster.
Ran some MR jobs successfully.
Verified signature.
Thanks,
Chang
On Mon, Dec 21, 2015 at 9:34 PM, Tsuyoshi Ozawa <oz...@apache.org> wrote:
> +1
>
> - downloaded src and bin tar balls and verified signatures.
> - built Tez and Spark with 2.7.2 artifacts and JDK7.
> - ran tests of Tez with 2.7.2 artifacts, it passed.
>
> FYI: YARN-4348, reported by Jian, is one of critical issues of 2.7.2
> release.It's better to release 2.7.3 as soon as possible after this
> release.
>
> Thanks,
> - Tsuyoshi
>
> On Tue, Dec 22, 2015 at 4:51 AM, Wangda Tan <wh...@gmail.com> wrote:
> > +1 (binding)
> >
> > - Build & deploy single-node Hadoop from source code
> > - Add/Remove node labels to queues/nodes
> > - Run distributed shell commanding using default/specified node labels
> >
> > Thanks,
> > Wangda
> >
> >
> > On Mon, Dec 21, 2015 at 9:58 AM, Masatake Iwasaki <
> > iwasakims@oss.nttdata.co.jp> wrote:
> >
> >> +1(non-binding)
> >>
> >> - verified mds and signature of source and binary tarball
> >> - started 3 node cluster and ran example jobs such as wordcount and
> >> terasort
> >> - built from source tarball with -Pnative on CentOS 7 and OpenJDK 7
> >> - built site documentation and skimmed the contents
> >>
> >> Thanks,
> >> Masatake Iwasaki
> >>
> >>
> >>
> >> On 12/17/15 11:49, Vinod Kumar Vavilapalli wrote:
> >>
> >>> Hi all,
> >>>
> >>> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
> >>>
> >>> As discussed before, this is the next maintenance release to follow up
> >>> 2.7.1.
> >>>
> >>> The RC is available for validation at:
> >>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <
> >>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
> >>>
> >>> The RC tag in git is: release-2.7.2-RC1
> >>>
> >>> The maven artifacts are available via repository.apache.org <
> >>> http://repository.apache.org/> at
> >>>
> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
> >>> <
> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
> >>> >
> >>>
> >>> The release-notes are inside the tar-balls at location
> >>> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I
> >>> hosted this at
> >>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html
> for
> >>> quick perusal.
> >>>
> >>> As you may have noted,
> >>> - The RC0 related voting thread got halted due to some critical
> issues.
> >>> It took a while again for getting all those blockers out of the way.
> See
> >>> the previous voting thread [3] for details.
> >>> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by
> >>> quite a bit. This release's related discussion threads are linked
> below:
> >>> [1] and [2].
> >>>
> >>> Please try the release and vote; the vote will run for the usual 5
> days.
> >>>
> >>> Thanks,
> >>> Vinod
> >>>
> >>> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes
> <
> >>> http://markmail.org/message/oozq3gvd4nhzsaes>
> >>> [2]: Planning Apache Hadoop 2.7.2
> >>> http://markmail.org/message/iktqss2qdeykgpqk <
> >>> http://markmail.org/message/iktqss2qdeykgpqk>
> >>> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
> >>> http://markmail.org/message/5txhvr2qdiqglrwc
> >>>
> >>>
> >>>
> >>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Junping Du <jd...@hortonworks.com>.
Checked 2.7.2-RC1 tag which match exactly with 2.7.2 branch.
Downloaded the release bit and deploy a single node cluster which works fine with running some example jobs.
Built from src and check signatures, all looks good.
Checked release note which has 138 commits (HADOOP:22, HDFS:42, MAPREDUCE:17, YARN:57) match exactly with JIRA fixed list in 2.7.2.
However, when I look at our commit log and CHANGES.txt, I found something we are missing:
1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
For 2, I think we can fix in creating the final tag. For 1, I will let release manager to decide if HDFS-9470 & YARN-4424 has to go to 2.7.2. If not, I will +1 and we can fix release notes later.
Thanks,
Junping
________________________________________
From: Chang Li <li...@gmail.com>
Sent: Tuesday, December 22, 2015 2:35 PM
To: mapreduce-dev@hadoop.apache.org
Cc: common-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org; Vinod Kumar Vavilapalli
Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
+1 (non binding)
Downloaed src and built on single node cluster.
Ran some MR jobs successfully.
Verified signature.
Thanks,
Chang
On Mon, Dec 21, 2015 at 9:34 PM, Tsuyoshi Ozawa <oz...@apache.org> wrote:
> +1
>
> - downloaded src and bin tar balls and verified signatures.
> - built Tez and Spark with 2.7.2 artifacts and JDK7.
> - ran tests of Tez with 2.7.2 artifacts, it passed.
>
> FYI: YARN-4348, reported by Jian, is one of critical issues of 2.7.2
> release.It's better to release 2.7.3 as soon as possible after this
> release.
>
> Thanks,
> - Tsuyoshi
>
> On Tue, Dec 22, 2015 at 4:51 AM, Wangda Tan <wh...@gmail.com> wrote:
> > +1 (binding)
> >
> > - Build & deploy single-node Hadoop from source code
> > - Add/Remove node labels to queues/nodes
> > - Run distributed shell commanding using default/specified node labels
> >
> > Thanks,
> > Wangda
> >
> >
> > On Mon, Dec 21, 2015 at 9:58 AM, Masatake Iwasaki <
> > iwasakims@oss.nttdata.co.jp> wrote:
> >
> >> +1(non-binding)
> >>
> >> - verified mds and signature of source and binary tarball
> >> - started 3 node cluster and ran example jobs such as wordcount and
> >> terasort
> >> - built from source tarball with -Pnative on CentOS 7 and OpenJDK 7
> >> - built site documentation and skimmed the contents
> >>
> >> Thanks,
> >> Masatake Iwasaki
> >>
> >>
> >>
> >> On 12/17/15 11:49, Vinod Kumar Vavilapalli wrote:
> >>
> >>> Hi all,
> >>>
> >>> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
> >>>
> >>> As discussed before, this is the next maintenance release to follow up
> >>> 2.7.1.
> >>>
> >>> The RC is available for validation at:
> >>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <
> >>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
> >>>
> >>> The RC tag in git is: release-2.7.2-RC1
> >>>
> >>> The maven artifacts are available via repository.apache.org <
> >>> http://repository.apache.org/> at
> >>>
> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
> >>> <
> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
> >>> >
> >>>
> >>> The release-notes are inside the tar-balls at location
> >>> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I
> >>> hosted this at
> >>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html
> for
> >>> quick perusal.
> >>>
> >>> As you may have noted,
> >>> - The RC0 related voting thread got halted due to some critical
> issues.
> >>> It took a while again for getting all those blockers out of the way.
> See
> >>> the previous voting thread [3] for details.
> >>> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by
> >>> quite a bit. This release's related discussion threads are linked
> below:
> >>> [1] and [2].
> >>>
> >>> Please try the release and vote; the vote will run for the usual 5
> days.
> >>>
> >>> Thanks,
> >>> Vinod
> >>>
> >>> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes
> <
> >>> http://markmail.org/message/oozq3gvd4nhzsaes>
> >>> [2]: Planning Apache Hadoop 2.7.2
> >>> http://markmail.org/message/iktqss2qdeykgpqk <
> >>> http://markmail.org/message/iktqss2qdeykgpqk>
> >>> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
> >>> http://markmail.org/message/5txhvr2qdiqglrwc
> >>>
> >>>
> >>>
> >>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Junping Du <jd...@hortonworks.com>.
Checked 2.7.2-RC1 tag which match exactly with 2.7.2 branch.
Downloaded the release bit and deploy a single node cluster which works fine with running some example jobs.
Built from src and check signatures, all looks good.
Checked release note which has 138 commits (HADOOP:22, HDFS:42, MAPREDUCE:17, YARN:57) match exactly with JIRA fixed list in 2.7.2.
However, when I look at our commit log and CHANGES.txt, I found something we are missing:
1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
For 2, I think we can fix in creating the final tag. For 1, I will let release manager to decide if HDFS-9470 & YARN-4424 has to go to 2.7.2. If not, I will +1 and we can fix release notes later.
Thanks,
Junping
________________________________________
From: Chang Li <li...@gmail.com>
Sent: Tuesday, December 22, 2015 2:35 PM
To: mapreduce-dev@hadoop.apache.org
Cc: common-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org; Vinod Kumar Vavilapalli
Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
+1 (non binding)
Downloaed src and built on single node cluster.
Ran some MR jobs successfully.
Verified signature.
Thanks,
Chang
On Mon, Dec 21, 2015 at 9:34 PM, Tsuyoshi Ozawa <oz...@apache.org> wrote:
> +1
>
> - downloaded src and bin tar balls and verified signatures.
> - built Tez and Spark with 2.7.2 artifacts and JDK7.
> - ran tests of Tez with 2.7.2 artifacts, it passed.
>
> FYI: YARN-4348, reported by Jian, is one of critical issues of 2.7.2
> release.It's better to release 2.7.3 as soon as possible after this
> release.
>
> Thanks,
> - Tsuyoshi
>
> On Tue, Dec 22, 2015 at 4:51 AM, Wangda Tan <wh...@gmail.com> wrote:
> > +1 (binding)
> >
> > - Build & deploy single-node Hadoop from source code
> > - Add/Remove node labels to queues/nodes
> > - Run distributed shell commanding using default/specified node labels
> >
> > Thanks,
> > Wangda
> >
> >
> > On Mon, Dec 21, 2015 at 9:58 AM, Masatake Iwasaki <
> > iwasakims@oss.nttdata.co.jp> wrote:
> >
> >> +1(non-binding)
> >>
> >> - verified mds and signature of source and binary tarball
> >> - started 3 node cluster and ran example jobs such as wordcount and
> >> terasort
> >> - built from source tarball with -Pnative on CentOS 7 and OpenJDK 7
> >> - built site documentation and skimmed the contents
> >>
> >> Thanks,
> >> Masatake Iwasaki
> >>
> >>
> >>
> >> On 12/17/15 11:49, Vinod Kumar Vavilapalli wrote:
> >>
> >>> Hi all,
> >>>
> >>> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
> >>>
> >>> As discussed before, this is the next maintenance release to follow up
> >>> 2.7.1.
> >>>
> >>> The RC is available for validation at:
> >>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <
> >>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
> >>>
> >>> The RC tag in git is: release-2.7.2-RC1
> >>>
> >>> The maven artifacts are available via repository.apache.org <
> >>> http://repository.apache.org/> at
> >>>
> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
> >>> <
> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
> >>> >
> >>>
> >>> The release-notes are inside the tar-balls at location
> >>> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I
> >>> hosted this at
> >>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html
> for
> >>> quick perusal.
> >>>
> >>> As you may have noted,
> >>> - The RC0 related voting thread got halted due to some critical
> issues.
> >>> It took a while again for getting all those blockers out of the way.
> See
> >>> the previous voting thread [3] for details.
> >>> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by
> >>> quite a bit. This release's related discussion threads are linked
> below:
> >>> [1] and [2].
> >>>
> >>> Please try the release and vote; the vote will run for the usual 5
> days.
> >>>
> >>> Thanks,
> >>> Vinod
> >>>
> >>> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes
> <
> >>> http://markmail.org/message/oozq3gvd4nhzsaes>
> >>> [2]: Planning Apache Hadoop 2.7.2
> >>> http://markmail.org/message/iktqss2qdeykgpqk <
> >>> http://markmail.org/message/iktqss2qdeykgpqk>
> >>> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
> >>> http://markmail.org/message/5txhvr2qdiqglrwc
> >>>
> >>>
> >>>
> >>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Junping Du <jd...@hortonworks.com>.
Checked 2.7.2-RC1 tag which match exactly with 2.7.2 branch.
Downloaded the release bit and deploy a single node cluster which works fine with running some example jobs.
Built from src and check signatures, all looks good.
Checked release note which has 138 commits (HADOOP:22, HDFS:42, MAPREDUCE:17, YARN:57) match exactly with JIRA fixed list in 2.7.2.
However, when I look at our commit log and CHANGES.txt, I found something we are missing:
1. HDFS-9470 and YARN-4424 are missing from the 2.7.2 branch and RC1 tag.
2. HADOOP-5323, HDFS-8767 are missing in CHANGE.txt
For 2, I think we can fix in creating the final tag. For 1, I will let release manager to decide if HDFS-9470 & YARN-4424 has to go to 2.7.2. If not, I will +1 and we can fix release notes later.
Thanks,
Junping
________________________________________
From: Chang Li <li...@gmail.com>
Sent: Tuesday, December 22, 2015 2:35 PM
To: mapreduce-dev@hadoop.apache.org
Cc: common-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org; Vinod Kumar Vavilapalli
Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
+1 (non binding)
Downloaed src and built on single node cluster.
Ran some MR jobs successfully.
Verified signature.
Thanks,
Chang
On Mon, Dec 21, 2015 at 9:34 PM, Tsuyoshi Ozawa <oz...@apache.org> wrote:
> +1
>
> - downloaded src and bin tar balls and verified signatures.
> - built Tez and Spark with 2.7.2 artifacts and JDK7.
> - ran tests of Tez with 2.7.2 artifacts, it passed.
>
> FYI: YARN-4348, reported by Jian, is one of critical issues of 2.7.2
> release.It's better to release 2.7.3 as soon as possible after this
> release.
>
> Thanks,
> - Tsuyoshi
>
> On Tue, Dec 22, 2015 at 4:51 AM, Wangda Tan <wh...@gmail.com> wrote:
> > +1 (binding)
> >
> > - Build & deploy single-node Hadoop from source code
> > - Add/Remove node labels to queues/nodes
> > - Run distributed shell commanding using default/specified node labels
> >
> > Thanks,
> > Wangda
> >
> >
> > On Mon, Dec 21, 2015 at 9:58 AM, Masatake Iwasaki <
> > iwasakims@oss.nttdata.co.jp> wrote:
> >
> >> +1(non-binding)
> >>
> >> - verified mds and signature of source and binary tarball
> >> - started 3 node cluster and ran example jobs such as wordcount and
> >> terasort
> >> - built from source tarball with -Pnative on CentOS 7 and OpenJDK 7
> >> - built site documentation and skimmed the contents
> >>
> >> Thanks,
> >> Masatake Iwasaki
> >>
> >>
> >>
> >> On 12/17/15 11:49, Vinod Kumar Vavilapalli wrote:
> >>
> >>> Hi all,
> >>>
> >>> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
> >>>
> >>> As discussed before, this is the next maintenance release to follow up
> >>> 2.7.1.
> >>>
> >>> The RC is available for validation at:
> >>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <
> >>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
> >>>
> >>> The RC tag in git is: release-2.7.2-RC1
> >>>
> >>> The maven artifacts are available via repository.apache.org <
> >>> http://repository.apache.org/> at
> >>>
> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
> >>> <
> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
> >>> >
> >>>
> >>> The release-notes are inside the tar-balls at location
> >>> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I
> >>> hosted this at
> >>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html
> for
> >>> quick perusal.
> >>>
> >>> As you may have noted,
> >>> - The RC0 related voting thread got halted due to some critical
> issues.
> >>> It took a while again for getting all those blockers out of the way.
> See
> >>> the previous voting thread [3] for details.
> >>> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by
> >>> quite a bit. This release's related discussion threads are linked
> below:
> >>> [1] and [2].
> >>>
> >>> Please try the release and vote; the vote will run for the usual 5
> days.
> >>>
> >>> Thanks,
> >>> Vinod
> >>>
> >>> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes
> <
> >>> http://markmail.org/message/oozq3gvd4nhzsaes>
> >>> [2]: Planning Apache Hadoop 2.7.2
> >>> http://markmail.org/message/iktqss2qdeykgpqk <
> >>> http://markmail.org/message/iktqss2qdeykgpqk>
> >>> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
> >>> http://markmail.org/message/5txhvr2qdiqglrwc
> >>>
> >>>
> >>>
> >>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Chang Li <li...@gmail.com>.
+1 (non binding)
Downloaed src and built on single node cluster.
Ran some MR jobs successfully.
Verified signature.
Thanks,
Chang
On Mon, Dec 21, 2015 at 9:34 PM, Tsuyoshi Ozawa <oz...@apache.org> wrote:
> +1
>
> - downloaded src and bin tar balls and verified signatures.
> - built Tez and Spark with 2.7.2 artifacts and JDK7.
> - ran tests of Tez with 2.7.2 artifacts, it passed.
>
> FYI: YARN-4348, reported by Jian, is one of critical issues of 2.7.2
> release.It's better to release 2.7.3 as soon as possible after this
> release.
>
> Thanks,
> - Tsuyoshi
>
> On Tue, Dec 22, 2015 at 4:51 AM, Wangda Tan <wh...@gmail.com> wrote:
> > +1 (binding)
> >
> > - Build & deploy single-node Hadoop from source code
> > - Add/Remove node labels to queues/nodes
> > - Run distributed shell commanding using default/specified node labels
> >
> > Thanks,
> > Wangda
> >
> >
> > On Mon, Dec 21, 2015 at 9:58 AM, Masatake Iwasaki <
> > iwasakims@oss.nttdata.co.jp> wrote:
> >
> >> +1(non-binding)
> >>
> >> - verified mds and signature of source and binary tarball
> >> - started 3 node cluster and ran example jobs such as wordcount and
> >> terasort
> >> - built from source tarball with -Pnative on CentOS 7 and OpenJDK 7
> >> - built site documentation and skimmed the contents
> >>
> >> Thanks,
> >> Masatake Iwasaki
> >>
> >>
> >>
> >> On 12/17/15 11:49, Vinod Kumar Vavilapalli wrote:
> >>
> >>> Hi all,
> >>>
> >>> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
> >>>
> >>> As discussed before, this is the next maintenance release to follow up
> >>> 2.7.1.
> >>>
> >>> The RC is available for validation at:
> >>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <
> >>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
> >>>
> >>> The RC tag in git is: release-2.7.2-RC1
> >>>
> >>> The maven artifacts are available via repository.apache.org <
> >>> http://repository.apache.org/> at
> >>>
> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
> >>> <
> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
> >>> >
> >>>
> >>> The release-notes are inside the tar-balls at location
> >>> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I
> >>> hosted this at
> >>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html
> for
> >>> quick perusal.
> >>>
> >>> As you may have noted,
> >>> - The RC0 related voting thread got halted due to some critical
> issues.
> >>> It took a while again for getting all those blockers out of the way.
> See
> >>> the previous voting thread [3] for details.
> >>> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by
> >>> quite a bit. This release's related discussion threads are linked
> below:
> >>> [1] and [2].
> >>>
> >>> Please try the release and vote; the vote will run for the usual 5
> days.
> >>>
> >>> Thanks,
> >>> Vinod
> >>>
> >>> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes
> <
> >>> http://markmail.org/message/oozq3gvd4nhzsaes>
> >>> [2]: Planning Apache Hadoop 2.7.2
> >>> http://markmail.org/message/iktqss2qdeykgpqk <
> >>> http://markmail.org/message/iktqss2qdeykgpqk>
> >>> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
> >>> http://markmail.org/message/5txhvr2qdiqglrwc
> >>>
> >>>
> >>>
> >>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Chang Li <li...@gmail.com>.
+1 (non binding)
Downloaed src and built on single node cluster.
Ran some MR jobs successfully.
Verified signature.
Thanks,
Chang
On Mon, Dec 21, 2015 at 9:34 PM, Tsuyoshi Ozawa <oz...@apache.org> wrote:
> +1
>
> - downloaded src and bin tar balls and verified signatures.
> - built Tez and Spark with 2.7.2 artifacts and JDK7.
> - ran tests of Tez with 2.7.2 artifacts, it passed.
>
> FYI: YARN-4348, reported by Jian, is one of critical issues of 2.7.2
> release.It's better to release 2.7.3 as soon as possible after this
> release.
>
> Thanks,
> - Tsuyoshi
>
> On Tue, Dec 22, 2015 at 4:51 AM, Wangda Tan <wh...@gmail.com> wrote:
> > +1 (binding)
> >
> > - Build & deploy single-node Hadoop from source code
> > - Add/Remove node labels to queues/nodes
> > - Run distributed shell commanding using default/specified node labels
> >
> > Thanks,
> > Wangda
> >
> >
> > On Mon, Dec 21, 2015 at 9:58 AM, Masatake Iwasaki <
> > iwasakims@oss.nttdata.co.jp> wrote:
> >
> >> +1(non-binding)
> >>
> >> - verified mds and signature of source and binary tarball
> >> - started 3 node cluster and ran example jobs such as wordcount and
> >> terasort
> >> - built from source tarball with -Pnative on CentOS 7 and OpenJDK 7
> >> - built site documentation and skimmed the contents
> >>
> >> Thanks,
> >> Masatake Iwasaki
> >>
> >>
> >>
> >> On 12/17/15 11:49, Vinod Kumar Vavilapalli wrote:
> >>
> >>> Hi all,
> >>>
> >>> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
> >>>
> >>> As discussed before, this is the next maintenance release to follow up
> >>> 2.7.1.
> >>>
> >>> The RC is available for validation at:
> >>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <
> >>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
> >>>
> >>> The RC tag in git is: release-2.7.2-RC1
> >>>
> >>> The maven artifacts are available via repository.apache.org <
> >>> http://repository.apache.org/> at
> >>>
> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
> >>> <
> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
> >>> >
> >>>
> >>> The release-notes are inside the tar-balls at location
> >>> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I
> >>> hosted this at
> >>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html
> for
> >>> quick perusal.
> >>>
> >>> As you may have noted,
> >>> - The RC0 related voting thread got halted due to some critical
> issues.
> >>> It took a while again for getting all those blockers out of the way.
> See
> >>> the previous voting thread [3] for details.
> >>> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by
> >>> quite a bit. This release's related discussion threads are linked
> below:
> >>> [1] and [2].
> >>>
> >>> Please try the release and vote; the vote will run for the usual 5
> days.
> >>>
> >>> Thanks,
> >>> Vinod
> >>>
> >>> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes
> <
> >>> http://markmail.org/message/oozq3gvd4nhzsaes>
> >>> [2]: Planning Apache Hadoop 2.7.2
> >>> http://markmail.org/message/iktqss2qdeykgpqk <
> >>> http://markmail.org/message/iktqss2qdeykgpqk>
> >>> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
> >>> http://markmail.org/message/5txhvr2qdiqglrwc
> >>>
> >>>
> >>>
> >>
>
RE: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Rohith Sharma K S <ro...@huawei.com>.
+1(non-binding)
-Built from source and deployed in 3 node cluster
-Tested with combination of RMRestart/RM HA/RM work preserving restart/NM work preserving restart modes.
-Ran MR and distributed shell sample applications.
-Verified signature and md5 of binary
Thanks & Regards
Rohith Sharma K S
-----Original Message-----
From: Tsuyoshi Ozawa [mailto:ozawa@apache.org]
Sent: 22 December 2015 09:04
To: common-dev@hadoop.apache.org
Cc: yarn-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org; Vinod Kumar Vavilapalli
Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
+1
- downloaded src and bin tar balls and verified signatures.
- built Tez and Spark with 2.7.2 artifacts and JDK7.
- ran tests of Tez with 2.7.2 artifacts, it passed.
FYI: YARN-4348, reported by Jian, is one of critical issues of 2.7.2 release.It's better to release 2.7.3 as soon as possible after this release.
Thanks,
- Tsuyoshi
On Tue, Dec 22, 2015 at 4:51 AM, Wangda Tan <wh...@gmail.com> wrote:
> +1 (binding)
>
> - Build & deploy single-node Hadoop from source code
> - Add/Remove node labels to queues/nodes
> - Run distributed shell commanding using default/specified node labels
>
> Thanks,
> Wangda
>
>
> On Mon, Dec 21, 2015 at 9:58 AM, Masatake Iwasaki <
> iwasakims@oss.nttdata.co.jp> wrote:
>
>> +1(non-binding)
>>
>> - verified mds and signature of source and binary tarball
>> - started 3 node cluster and ran example jobs such as wordcount and
>> terasort
>> - built from source tarball with -Pnative on CentOS 7 and OpenJDK 7
>> - built site documentation and skimmed the contents
>>
>> Thanks,
>> Masatake Iwasaki
>>
>>
>>
>> On 12/17/15 11:49, Vinod Kumar Vavilapalli wrote:
>>
>>> Hi all,
>>>
>>> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>>>
>>> As discussed before, this is the next maintenance release to follow
>>> up 2.7.1.
>>>
>>> The RC is available for validation at:
>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <
>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>>>
>>> The RC tag in git is: release-2.7.2-RC1
>>>
>>> The maven artifacts are available via repository.apache.org <
>>> http://repository.apache.org/> at
>>> https://repository.apache.org/content/repositories/orgapachehadoop-1
>>> 026/
>>> <https://repository.apache.org/content/repositories/orgapachehadoop-
>>> 1026/
>>> >
>>>
>>> The release-notes are inside the tar-balls at location
>>> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html.
>>> I hosted this at
>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html
>>> for quick perusal.
>>>
>>> As you may have noted,
>>> - The RC0 related voting thread got halted due to some critical issues.
>>> It took a while again for getting all those blockers out of the way.
>>> See the previous voting thread [3] for details.
>>> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip
>>> by quite a bit. This release's related discussion threads are linked below:
>>> [1] and [2].
>>>
>>> Please try the release and vote; the vote will run for the usual 5 days.
>>>
>>> Thanks,
>>> Vinod
>>>
>>> [1]: 2.7.2 release plan:
>>> http://markmail.org/message/oozq3gvd4nhzsaes <
>>> http://markmail.org/message/oozq3gvd4nhzsaes>
>>> [2]: Planning Apache Hadoop 2.7.2
>>> http://markmail.org/message/iktqss2qdeykgpqk <
>>> http://markmail.org/message/iktqss2qdeykgpqk>
>>> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
>>> http://markmail.org/message/5txhvr2qdiqglrwc
>>>
>>>
>>>
>>
RE: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Rohith Sharma K S <ro...@huawei.com>.
+1(non-binding)
-Built from source and deployed in 3 node cluster
-Tested with combination of RMRestart/RM HA/RM work preserving restart/NM work preserving restart modes.
-Ran MR and distributed shell sample applications.
-Verified signature and md5 of binary
Thanks & Regards
Rohith Sharma K S
-----Original Message-----
From: Tsuyoshi Ozawa [mailto:ozawa@apache.org]
Sent: 22 December 2015 09:04
To: common-dev@hadoop.apache.org
Cc: yarn-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org; Vinod Kumar Vavilapalli
Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
+1
- downloaded src and bin tar balls and verified signatures.
- built Tez and Spark with 2.7.2 artifacts and JDK7.
- ran tests of Tez with 2.7.2 artifacts, it passed.
FYI: YARN-4348, reported by Jian, is one of critical issues of 2.7.2 release.It's better to release 2.7.3 as soon as possible after this release.
Thanks,
- Tsuyoshi
On Tue, Dec 22, 2015 at 4:51 AM, Wangda Tan <wh...@gmail.com> wrote:
> +1 (binding)
>
> - Build & deploy single-node Hadoop from source code
> - Add/Remove node labels to queues/nodes
> - Run distributed shell commanding using default/specified node labels
>
> Thanks,
> Wangda
>
>
> On Mon, Dec 21, 2015 at 9:58 AM, Masatake Iwasaki <
> iwasakims@oss.nttdata.co.jp> wrote:
>
>> +1(non-binding)
>>
>> - verified mds and signature of source and binary tarball
>> - started 3 node cluster and ran example jobs such as wordcount and
>> terasort
>> - built from source tarball with -Pnative on CentOS 7 and OpenJDK 7
>> - built site documentation and skimmed the contents
>>
>> Thanks,
>> Masatake Iwasaki
>>
>>
>>
>> On 12/17/15 11:49, Vinod Kumar Vavilapalli wrote:
>>
>>> Hi all,
>>>
>>> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>>>
>>> As discussed before, this is the next maintenance release to follow
>>> up 2.7.1.
>>>
>>> The RC is available for validation at:
>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <
>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>>>
>>> The RC tag in git is: release-2.7.2-RC1
>>>
>>> The maven artifacts are available via repository.apache.org <
>>> http://repository.apache.org/> at
>>> https://repository.apache.org/content/repositories/orgapachehadoop-1
>>> 026/
>>> <https://repository.apache.org/content/repositories/orgapachehadoop-
>>> 1026/
>>> >
>>>
>>> The release-notes are inside the tar-balls at location
>>> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html.
>>> I hosted this at
>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html
>>> for quick perusal.
>>>
>>> As you may have noted,
>>> - The RC0 related voting thread got halted due to some critical issues.
>>> It took a while again for getting all those blockers out of the way.
>>> See the previous voting thread [3] for details.
>>> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip
>>> by quite a bit. This release's related discussion threads are linked below:
>>> [1] and [2].
>>>
>>> Please try the release and vote; the vote will run for the usual 5 days.
>>>
>>> Thanks,
>>> Vinod
>>>
>>> [1]: 2.7.2 release plan:
>>> http://markmail.org/message/oozq3gvd4nhzsaes <
>>> http://markmail.org/message/oozq3gvd4nhzsaes>
>>> [2]: Planning Apache Hadoop 2.7.2
>>> http://markmail.org/message/iktqss2qdeykgpqk <
>>> http://markmail.org/message/iktqss2qdeykgpqk>
>>> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
>>> http://markmail.org/message/5txhvr2qdiqglrwc
>>>
>>>
>>>
>>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Chang Li <li...@gmail.com>.
+1 (non binding)
Downloaed src and built on single node cluster.
Ran some MR jobs successfully.
Verified signature.
Thanks,
Chang
On Mon, Dec 21, 2015 at 9:34 PM, Tsuyoshi Ozawa <oz...@apache.org> wrote:
> +1
>
> - downloaded src and bin tar balls and verified signatures.
> - built Tez and Spark with 2.7.2 artifacts and JDK7.
> - ran tests of Tez with 2.7.2 artifacts, it passed.
>
> FYI: YARN-4348, reported by Jian, is one of critical issues of 2.7.2
> release.It's better to release 2.7.3 as soon as possible after this
> release.
>
> Thanks,
> - Tsuyoshi
>
> On Tue, Dec 22, 2015 at 4:51 AM, Wangda Tan <wh...@gmail.com> wrote:
> > +1 (binding)
> >
> > - Build & deploy single-node Hadoop from source code
> > - Add/Remove node labels to queues/nodes
> > - Run distributed shell commanding using default/specified node labels
> >
> > Thanks,
> > Wangda
> >
> >
> > On Mon, Dec 21, 2015 at 9:58 AM, Masatake Iwasaki <
> > iwasakims@oss.nttdata.co.jp> wrote:
> >
> >> +1(non-binding)
> >>
> >> - verified mds and signature of source and binary tarball
> >> - started 3 node cluster and ran example jobs such as wordcount and
> >> terasort
> >> - built from source tarball with -Pnative on CentOS 7 and OpenJDK 7
> >> - built site documentation and skimmed the contents
> >>
> >> Thanks,
> >> Masatake Iwasaki
> >>
> >>
> >>
> >> On 12/17/15 11:49, Vinod Kumar Vavilapalli wrote:
> >>
> >>> Hi all,
> >>>
> >>> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
> >>>
> >>> As discussed before, this is the next maintenance release to follow up
> >>> 2.7.1.
> >>>
> >>> The RC is available for validation at:
> >>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <
> >>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
> >>>
> >>> The RC tag in git is: release-2.7.2-RC1
> >>>
> >>> The maven artifacts are available via repository.apache.org <
> >>> http://repository.apache.org/> at
> >>>
> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
> >>> <
> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
> >>> >
> >>>
> >>> The release-notes are inside the tar-balls at location
> >>> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I
> >>> hosted this at
> >>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html
> for
> >>> quick perusal.
> >>>
> >>> As you may have noted,
> >>> - The RC0 related voting thread got halted due to some critical
> issues.
> >>> It took a while again for getting all those blockers out of the way.
> See
> >>> the previous voting thread [3] for details.
> >>> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by
> >>> quite a bit. This release's related discussion threads are linked
> below:
> >>> [1] and [2].
> >>>
> >>> Please try the release and vote; the vote will run for the usual 5
> days.
> >>>
> >>> Thanks,
> >>> Vinod
> >>>
> >>> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes
> <
> >>> http://markmail.org/message/oozq3gvd4nhzsaes>
> >>> [2]: Planning Apache Hadoop 2.7.2
> >>> http://markmail.org/message/iktqss2qdeykgpqk <
> >>> http://markmail.org/message/iktqss2qdeykgpqk>
> >>> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
> >>> http://markmail.org/message/5txhvr2qdiqglrwc
> >>>
> >>>
> >>>
> >>
>
RE: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Rohith Sharma K S <ro...@huawei.com>.
+1(non-binding)
-Built from source and deployed in 3 node cluster
-Tested with combination of RMRestart/RM HA/RM work preserving restart/NM work preserving restart modes.
-Ran MR and distributed shell sample applications.
-Verified signature and md5 of binary
Thanks & Regards
Rohith Sharma K S
-----Original Message-----
From: Tsuyoshi Ozawa [mailto:ozawa@apache.org]
Sent: 22 December 2015 09:04
To: common-dev@hadoop.apache.org
Cc: yarn-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org; Vinod Kumar Vavilapalli
Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
+1
- downloaded src and bin tar balls and verified signatures.
- built Tez and Spark with 2.7.2 artifacts and JDK7.
- ran tests of Tez with 2.7.2 artifacts, it passed.
FYI: YARN-4348, reported by Jian, is one of critical issues of 2.7.2 release.It's better to release 2.7.3 as soon as possible after this release.
Thanks,
- Tsuyoshi
On Tue, Dec 22, 2015 at 4:51 AM, Wangda Tan <wh...@gmail.com> wrote:
> +1 (binding)
>
> - Build & deploy single-node Hadoop from source code
> - Add/Remove node labels to queues/nodes
> - Run distributed shell commanding using default/specified node labels
>
> Thanks,
> Wangda
>
>
> On Mon, Dec 21, 2015 at 9:58 AM, Masatake Iwasaki <
> iwasakims@oss.nttdata.co.jp> wrote:
>
>> +1(non-binding)
>>
>> - verified mds and signature of source and binary tarball
>> - started 3 node cluster and ran example jobs such as wordcount and
>> terasort
>> - built from source tarball with -Pnative on CentOS 7 and OpenJDK 7
>> - built site documentation and skimmed the contents
>>
>> Thanks,
>> Masatake Iwasaki
>>
>>
>>
>> On 12/17/15 11:49, Vinod Kumar Vavilapalli wrote:
>>
>>> Hi all,
>>>
>>> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>>>
>>> As discussed before, this is the next maintenance release to follow
>>> up 2.7.1.
>>>
>>> The RC is available for validation at:
>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <
>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>>>
>>> The RC tag in git is: release-2.7.2-RC1
>>>
>>> The maven artifacts are available via repository.apache.org <
>>> http://repository.apache.org/> at
>>> https://repository.apache.org/content/repositories/orgapachehadoop-1
>>> 026/
>>> <https://repository.apache.org/content/repositories/orgapachehadoop-
>>> 1026/
>>> >
>>>
>>> The release-notes are inside the tar-balls at location
>>> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html.
>>> I hosted this at
>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html
>>> for quick perusal.
>>>
>>> As you may have noted,
>>> - The RC0 related voting thread got halted due to some critical issues.
>>> It took a while again for getting all those blockers out of the way.
>>> See the previous voting thread [3] for details.
>>> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip
>>> by quite a bit. This release's related discussion threads are linked below:
>>> [1] and [2].
>>>
>>> Please try the release and vote; the vote will run for the usual 5 days.
>>>
>>> Thanks,
>>> Vinod
>>>
>>> [1]: 2.7.2 release plan:
>>> http://markmail.org/message/oozq3gvd4nhzsaes <
>>> http://markmail.org/message/oozq3gvd4nhzsaes>
>>> [2]: Planning Apache Hadoop 2.7.2
>>> http://markmail.org/message/iktqss2qdeykgpqk <
>>> http://markmail.org/message/iktqss2qdeykgpqk>
>>> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
>>> http://markmail.org/message/5txhvr2qdiqglrwc
>>>
>>>
>>>
>>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Chang Li <li...@gmail.com>.
+1 (non binding)
Downloaed src and built on single node cluster.
Ran some MR jobs successfully.
Verified signature.
Thanks,
Chang
On Mon, Dec 21, 2015 at 9:34 PM, Tsuyoshi Ozawa <oz...@apache.org> wrote:
> +1
>
> - downloaded src and bin tar balls and verified signatures.
> - built Tez and Spark with 2.7.2 artifacts and JDK7.
> - ran tests of Tez with 2.7.2 artifacts, it passed.
>
> FYI: YARN-4348, reported by Jian, is one of critical issues of 2.7.2
> release.It's better to release 2.7.3 as soon as possible after this
> release.
>
> Thanks,
> - Tsuyoshi
>
> On Tue, Dec 22, 2015 at 4:51 AM, Wangda Tan <wh...@gmail.com> wrote:
> > +1 (binding)
> >
> > - Build & deploy single-node Hadoop from source code
> > - Add/Remove node labels to queues/nodes
> > - Run distributed shell commanding using default/specified node labels
> >
> > Thanks,
> > Wangda
> >
> >
> > On Mon, Dec 21, 2015 at 9:58 AM, Masatake Iwasaki <
> > iwasakims@oss.nttdata.co.jp> wrote:
> >
> >> +1(non-binding)
> >>
> >> - verified mds and signature of source and binary tarball
> >> - started 3 node cluster and ran example jobs such as wordcount and
> >> terasort
> >> - built from source tarball with -Pnative on CentOS 7 and OpenJDK 7
> >> - built site documentation and skimmed the contents
> >>
> >> Thanks,
> >> Masatake Iwasaki
> >>
> >>
> >>
> >> On 12/17/15 11:49, Vinod Kumar Vavilapalli wrote:
> >>
> >>> Hi all,
> >>>
> >>> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
> >>>
> >>> As discussed before, this is the next maintenance release to follow up
> >>> 2.7.1.
> >>>
> >>> The RC is available for validation at:
> >>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <
> >>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
> >>>
> >>> The RC tag in git is: release-2.7.2-RC1
> >>>
> >>> The maven artifacts are available via repository.apache.org <
> >>> http://repository.apache.org/> at
> >>>
> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
> >>> <
> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
> >>> >
> >>>
> >>> The release-notes are inside the tar-balls at location
> >>> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I
> >>> hosted this at
> >>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html
> for
> >>> quick perusal.
> >>>
> >>> As you may have noted,
> >>> - The RC0 related voting thread got halted due to some critical
> issues.
> >>> It took a while again for getting all those blockers out of the way.
> See
> >>> the previous voting thread [3] for details.
> >>> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by
> >>> quite a bit. This release's related discussion threads are linked
> below:
> >>> [1] and [2].
> >>>
> >>> Please try the release and vote; the vote will run for the usual 5
> days.
> >>>
> >>> Thanks,
> >>> Vinod
> >>>
> >>> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes
> <
> >>> http://markmail.org/message/oozq3gvd4nhzsaes>
> >>> [2]: Planning Apache Hadoop 2.7.2
> >>> http://markmail.org/message/iktqss2qdeykgpqk <
> >>> http://markmail.org/message/iktqss2qdeykgpqk>
> >>> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
> >>> http://markmail.org/message/5txhvr2qdiqglrwc
> >>>
> >>>
> >>>
> >>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Tsuyoshi Ozawa <oz...@apache.org>.
+1
- downloaded src and bin tar balls and verified signatures.
- built Tez and Spark with 2.7.2 artifacts and JDK7.
- ran tests of Tez with 2.7.2 artifacts, it passed.
FYI: YARN-4348, reported by Jian, is one of critical issues of 2.7.2
release.It's better to release 2.7.3 as soon as possible after this
release.
Thanks,
- Tsuyoshi
On Tue, Dec 22, 2015 at 4:51 AM, Wangda Tan <wh...@gmail.com> wrote:
> +1 (binding)
>
> - Build & deploy single-node Hadoop from source code
> - Add/Remove node labels to queues/nodes
> - Run distributed shell commanding using default/specified node labels
>
> Thanks,
> Wangda
>
>
> On Mon, Dec 21, 2015 at 9:58 AM, Masatake Iwasaki <
> iwasakims@oss.nttdata.co.jp> wrote:
>
>> +1(non-binding)
>>
>> - verified mds and signature of source and binary tarball
>> - started 3 node cluster and ran example jobs such as wordcount and
>> terasort
>> - built from source tarball with -Pnative on CentOS 7 and OpenJDK 7
>> - built site documentation and skimmed the contents
>>
>> Thanks,
>> Masatake Iwasaki
>>
>>
>>
>> On 12/17/15 11:49, Vinod Kumar Vavilapalli wrote:
>>
>>> Hi all,
>>>
>>> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>>>
>>> As discussed before, this is the next maintenance release to follow up
>>> 2.7.1.
>>>
>>> The RC is available for validation at:
>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <
>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>>>
>>> The RC tag in git is: release-2.7.2-RC1
>>>
>>> The maven artifacts are available via repository.apache.org <
>>> http://repository.apache.org/> at
>>> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
>>> <https://repository.apache.org/content/repositories/orgapachehadoop-1026/
>>> >
>>>
>>> The release-notes are inside the tar-balls at location
>>> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I
>>> hosted this at
>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for
>>> quick perusal.
>>>
>>> As you may have noted,
>>> - The RC0 related voting thread got halted due to some critical issues.
>>> It took a while again for getting all those blockers out of the way. See
>>> the previous voting thread [3] for details.
>>> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by
>>> quite a bit. This release's related discussion threads are linked below:
>>> [1] and [2].
>>>
>>> Please try the release and vote; the vote will run for the usual 5 days.
>>>
>>> Thanks,
>>> Vinod
>>>
>>> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <
>>> http://markmail.org/message/oozq3gvd4nhzsaes>
>>> [2]: Planning Apache Hadoop 2.7.2
>>> http://markmail.org/message/iktqss2qdeykgpqk <
>>> http://markmail.org/message/iktqss2qdeykgpqk>
>>> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
>>> http://markmail.org/message/5txhvr2qdiqglrwc
>>>
>>>
>>>
>>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Tsuyoshi Ozawa <oz...@apache.org>.
+1
- downloaded src and bin tar balls and verified signatures.
- built Tez and Spark with 2.7.2 artifacts and JDK7.
- ran tests of Tez with 2.7.2 artifacts, it passed.
FYI: YARN-4348, reported by Jian, is one of critical issues of 2.7.2
release.It's better to release 2.7.3 as soon as possible after this
release.
Thanks,
- Tsuyoshi
On Tue, Dec 22, 2015 at 4:51 AM, Wangda Tan <wh...@gmail.com> wrote:
> +1 (binding)
>
> - Build & deploy single-node Hadoop from source code
> - Add/Remove node labels to queues/nodes
> - Run distributed shell commanding using default/specified node labels
>
> Thanks,
> Wangda
>
>
> On Mon, Dec 21, 2015 at 9:58 AM, Masatake Iwasaki <
> iwasakims@oss.nttdata.co.jp> wrote:
>
>> +1(non-binding)
>>
>> - verified mds and signature of source and binary tarball
>> - started 3 node cluster and ran example jobs such as wordcount and
>> terasort
>> - built from source tarball with -Pnative on CentOS 7 and OpenJDK 7
>> - built site documentation and skimmed the contents
>>
>> Thanks,
>> Masatake Iwasaki
>>
>>
>>
>> On 12/17/15 11:49, Vinod Kumar Vavilapalli wrote:
>>
>>> Hi all,
>>>
>>> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>>>
>>> As discussed before, this is the next maintenance release to follow up
>>> 2.7.1.
>>>
>>> The RC is available for validation at:
>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <
>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>>>
>>> The RC tag in git is: release-2.7.2-RC1
>>>
>>> The maven artifacts are available via repository.apache.org <
>>> http://repository.apache.org/> at
>>> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
>>> <https://repository.apache.org/content/repositories/orgapachehadoop-1026/
>>> >
>>>
>>> The release-notes are inside the tar-balls at location
>>> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I
>>> hosted this at
>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for
>>> quick perusal.
>>>
>>> As you may have noted,
>>> - The RC0 related voting thread got halted due to some critical issues.
>>> It took a while again for getting all those blockers out of the way. See
>>> the previous voting thread [3] for details.
>>> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by
>>> quite a bit. This release's related discussion threads are linked below:
>>> [1] and [2].
>>>
>>> Please try the release and vote; the vote will run for the usual 5 days.
>>>
>>> Thanks,
>>> Vinod
>>>
>>> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <
>>> http://markmail.org/message/oozq3gvd4nhzsaes>
>>> [2]: Planning Apache Hadoop 2.7.2
>>> http://markmail.org/message/iktqss2qdeykgpqk <
>>> http://markmail.org/message/iktqss2qdeykgpqk>
>>> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
>>> http://markmail.org/message/5txhvr2qdiqglrwc
>>>
>>>
>>>
>>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Tsuyoshi Ozawa <oz...@apache.org>.
+1
- downloaded src and bin tar balls and verified signatures.
- built Tez and Spark with 2.7.2 artifacts and JDK7.
- ran tests of Tez with 2.7.2 artifacts, it passed.
FYI: YARN-4348, reported by Jian, is one of critical issues of 2.7.2
release.It's better to release 2.7.3 as soon as possible after this
release.
Thanks,
- Tsuyoshi
On Tue, Dec 22, 2015 at 4:51 AM, Wangda Tan <wh...@gmail.com> wrote:
> +1 (binding)
>
> - Build & deploy single-node Hadoop from source code
> - Add/Remove node labels to queues/nodes
> - Run distributed shell commanding using default/specified node labels
>
> Thanks,
> Wangda
>
>
> On Mon, Dec 21, 2015 at 9:58 AM, Masatake Iwasaki <
> iwasakims@oss.nttdata.co.jp> wrote:
>
>> +1(non-binding)
>>
>> - verified mds and signature of source and binary tarball
>> - started 3 node cluster and ran example jobs such as wordcount and
>> terasort
>> - built from source tarball with -Pnative on CentOS 7 and OpenJDK 7
>> - built site documentation and skimmed the contents
>>
>> Thanks,
>> Masatake Iwasaki
>>
>>
>>
>> On 12/17/15 11:49, Vinod Kumar Vavilapalli wrote:
>>
>>> Hi all,
>>>
>>> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>>>
>>> As discussed before, this is the next maintenance release to follow up
>>> 2.7.1.
>>>
>>> The RC is available for validation at:
>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <
>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>>>
>>> The RC tag in git is: release-2.7.2-RC1
>>>
>>> The maven artifacts are available via repository.apache.org <
>>> http://repository.apache.org/> at
>>> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
>>> <https://repository.apache.org/content/repositories/orgapachehadoop-1026/
>>> >
>>>
>>> The release-notes are inside the tar-balls at location
>>> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I
>>> hosted this at
>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for
>>> quick perusal.
>>>
>>> As you may have noted,
>>> - The RC0 related voting thread got halted due to some critical issues.
>>> It took a while again for getting all those blockers out of the way. See
>>> the previous voting thread [3] for details.
>>> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by
>>> quite a bit. This release's related discussion threads are linked below:
>>> [1] and [2].
>>>
>>> Please try the release and vote; the vote will run for the usual 5 days.
>>>
>>> Thanks,
>>> Vinod
>>>
>>> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <
>>> http://markmail.org/message/oozq3gvd4nhzsaes>
>>> [2]: Planning Apache Hadoop 2.7.2
>>> http://markmail.org/message/iktqss2qdeykgpqk <
>>> http://markmail.org/message/iktqss2qdeykgpqk>
>>> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
>>> http://markmail.org/message/5txhvr2qdiqglrwc
>>>
>>>
>>>
>>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Xuan Gong <xg...@hortonworks.com>.
+1 (binding)
Thanks
Xuan Gong
> On Dec 21, 2015, at 4:25 PM, Chen He <ai...@gmail.com> wrote:
>
> +1 (non-binding)
>
> deploy to a 2-node cluster
> run loadgen and wc without problem
>
>
> Kindly ask a silly question, why we separate 2.6.x from 2.7.x?
>
> On Mon, Dec 21, 2015 at 11:51 AM, Wangda Tan <wh...@gmail.com> wrote:
>
>> +1 (binding)
>>
>> - Build & deploy single-node Hadoop from source code
>> - Add/Remove node labels to queues/nodes
>> - Run distributed shell commanding using default/specified node labels
>>
>> Thanks,
>> Wangda
>>
>>
>> On Mon, Dec 21, 2015 at 9:58 AM, Masatake Iwasaki <
>> iwasakims@oss.nttdata.co.jp> wrote:
>>
>>> +1(non-binding)
>>>
>>> - verified mds and signature of source and binary tarball
>>> - started 3 node cluster and ran example jobs such as wordcount and
>>> terasort
>>> - built from source tarball with -Pnative on CentOS 7 and OpenJDK 7
>>> - built site documentation and skimmed the contents
>>>
>>> Thanks,
>>> Masatake Iwasaki
>>>
>>>
>>>
>>> On 12/17/15 11:49, Vinod Kumar Vavilapalli wrote:
>>>
>>>> Hi all,
>>>>
>>>> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>>>>
>>>> As discussed before, this is the next maintenance release to follow up
>>>> 2.7.1.
>>>>
>>>> The RC is available for validation at:
>>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <
>>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>>>>
>>>> The RC tag in git is: release-2.7.2-RC1
>>>>
>>>> The maven artifacts are available via repository.apache.org <
>>>> http://repository.apache.org/> at
>>>>
>> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
>>>> <
>> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
>>>>>
>>>>
>>>> The release-notes are inside the tar-balls at location
>>>> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I
>>>> hosted this at
>>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html
>> for
>>>> quick perusal.
>>>>
>>>> As you may have noted,
>>>> - The RC0 related voting thread got halted due to some critical
>> issues.
>>>> It took a while again for getting all those blockers out of the way. See
>>>> the previous voting thread [3] for details.
>>>> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by
>>>> quite a bit. This release's related discussion threads are linked below:
>>>> [1] and [2].
>>>>
>>>> Please try the release and vote; the vote will run for the usual 5 days.
>>>>
>>>> Thanks,
>>>> Vinod
>>>>
>>>> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <
>>>> http://markmail.org/message/oozq3gvd4nhzsaes>
>>>> [2]: Planning Apache Hadoop 2.7.2
>>>> http://markmail.org/message/iktqss2qdeykgpqk <
>>>> http://markmail.org/message/iktqss2qdeykgpqk>
>>>> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
>>>> http://markmail.org/message/5txhvr2qdiqglrwc
>>>>
>>>>
>>>>
>>>
>>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Xuan Gong <xg...@hortonworks.com>.
+1 (binding)
Thanks
Xuan Gong
> On Dec 21, 2015, at 4:25 PM, Chen He <ai...@gmail.com> wrote:
>
> +1 (non-binding)
>
> deploy to a 2-node cluster
> run loadgen and wc without problem
>
>
> Kindly ask a silly question, why we separate 2.6.x from 2.7.x?
>
> On Mon, Dec 21, 2015 at 11:51 AM, Wangda Tan <wh...@gmail.com> wrote:
>
>> +1 (binding)
>>
>> - Build & deploy single-node Hadoop from source code
>> - Add/Remove node labels to queues/nodes
>> - Run distributed shell commanding using default/specified node labels
>>
>> Thanks,
>> Wangda
>>
>>
>> On Mon, Dec 21, 2015 at 9:58 AM, Masatake Iwasaki <
>> iwasakims@oss.nttdata.co.jp> wrote:
>>
>>> +1(non-binding)
>>>
>>> - verified mds and signature of source and binary tarball
>>> - started 3 node cluster and ran example jobs such as wordcount and
>>> terasort
>>> - built from source tarball with -Pnative on CentOS 7 and OpenJDK 7
>>> - built site documentation and skimmed the contents
>>>
>>> Thanks,
>>> Masatake Iwasaki
>>>
>>>
>>>
>>> On 12/17/15 11:49, Vinod Kumar Vavilapalli wrote:
>>>
>>>> Hi all,
>>>>
>>>> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>>>>
>>>> As discussed before, this is the next maintenance release to follow up
>>>> 2.7.1.
>>>>
>>>> The RC is available for validation at:
>>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <
>>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>>>>
>>>> The RC tag in git is: release-2.7.2-RC1
>>>>
>>>> The maven artifacts are available via repository.apache.org <
>>>> http://repository.apache.org/> at
>>>>
>> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
>>>> <
>> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
>>>>>
>>>>
>>>> The release-notes are inside the tar-balls at location
>>>> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I
>>>> hosted this at
>>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html
>> for
>>>> quick perusal.
>>>>
>>>> As you may have noted,
>>>> - The RC0 related voting thread got halted due to some critical
>> issues.
>>>> It took a while again for getting all those blockers out of the way. See
>>>> the previous voting thread [3] for details.
>>>> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by
>>>> quite a bit. This release's related discussion threads are linked below:
>>>> [1] and [2].
>>>>
>>>> Please try the release and vote; the vote will run for the usual 5 days.
>>>>
>>>> Thanks,
>>>> Vinod
>>>>
>>>> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <
>>>> http://markmail.org/message/oozq3gvd4nhzsaes>
>>>> [2]: Planning Apache Hadoop 2.7.2
>>>> http://markmail.org/message/iktqss2qdeykgpqk <
>>>> http://markmail.org/message/iktqss2qdeykgpqk>
>>>> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
>>>> http://markmail.org/message/5txhvr2qdiqglrwc
>>>>
>>>>
>>>>
>>>
>>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Xuan Gong <xg...@hortonworks.com>.
+1 (binding)
Thanks
Xuan Gong
> On Dec 21, 2015, at 4:25 PM, Chen He <ai...@gmail.com> wrote:
>
> +1 (non-binding)
>
> deploy to a 2-node cluster
> run loadgen and wc without problem
>
>
> Kindly ask a silly question, why we separate 2.6.x from 2.7.x?
>
> On Mon, Dec 21, 2015 at 11:51 AM, Wangda Tan <wh...@gmail.com> wrote:
>
>> +1 (binding)
>>
>> - Build & deploy single-node Hadoop from source code
>> - Add/Remove node labels to queues/nodes
>> - Run distributed shell commanding using default/specified node labels
>>
>> Thanks,
>> Wangda
>>
>>
>> On Mon, Dec 21, 2015 at 9:58 AM, Masatake Iwasaki <
>> iwasakims@oss.nttdata.co.jp> wrote:
>>
>>> +1(non-binding)
>>>
>>> - verified mds and signature of source and binary tarball
>>> - started 3 node cluster and ran example jobs such as wordcount and
>>> terasort
>>> - built from source tarball with -Pnative on CentOS 7 and OpenJDK 7
>>> - built site documentation and skimmed the contents
>>>
>>> Thanks,
>>> Masatake Iwasaki
>>>
>>>
>>>
>>> On 12/17/15 11:49, Vinod Kumar Vavilapalli wrote:
>>>
>>>> Hi all,
>>>>
>>>> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>>>>
>>>> As discussed before, this is the next maintenance release to follow up
>>>> 2.7.1.
>>>>
>>>> The RC is available for validation at:
>>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <
>>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>>>>
>>>> The RC tag in git is: release-2.7.2-RC1
>>>>
>>>> The maven artifacts are available via repository.apache.org <
>>>> http://repository.apache.org/> at
>>>>
>> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
>>>> <
>> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
>>>>>
>>>>
>>>> The release-notes are inside the tar-balls at location
>>>> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I
>>>> hosted this at
>>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html
>> for
>>>> quick perusal.
>>>>
>>>> As you may have noted,
>>>> - The RC0 related voting thread got halted due to some critical
>> issues.
>>>> It took a while again for getting all those blockers out of the way. See
>>>> the previous voting thread [3] for details.
>>>> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by
>>>> quite a bit. This release's related discussion threads are linked below:
>>>> [1] and [2].
>>>>
>>>> Please try the release and vote; the vote will run for the usual 5 days.
>>>>
>>>> Thanks,
>>>> Vinod
>>>>
>>>> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <
>>>> http://markmail.org/message/oozq3gvd4nhzsaes>
>>>> [2]: Planning Apache Hadoop 2.7.2
>>>> http://markmail.org/message/iktqss2qdeykgpqk <
>>>> http://markmail.org/message/iktqss2qdeykgpqk>
>>>> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
>>>> http://markmail.org/message/5txhvr2qdiqglrwc
>>>>
>>>>
>>>>
>>>
>>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Xuan Gong <xg...@hortonworks.com>.
+1 (binding)
Thanks
Xuan Gong
> On Dec 21, 2015, at 4:25 PM, Chen He <ai...@gmail.com> wrote:
>
> +1 (non-binding)
>
> deploy to a 2-node cluster
> run loadgen and wc without problem
>
>
> Kindly ask a silly question, why we separate 2.6.x from 2.7.x?
>
> On Mon, Dec 21, 2015 at 11:51 AM, Wangda Tan <wh...@gmail.com> wrote:
>
>> +1 (binding)
>>
>> - Build & deploy single-node Hadoop from source code
>> - Add/Remove node labels to queues/nodes
>> - Run distributed shell commanding using default/specified node labels
>>
>> Thanks,
>> Wangda
>>
>>
>> On Mon, Dec 21, 2015 at 9:58 AM, Masatake Iwasaki <
>> iwasakims@oss.nttdata.co.jp> wrote:
>>
>>> +1(non-binding)
>>>
>>> - verified mds and signature of source and binary tarball
>>> - started 3 node cluster and ran example jobs such as wordcount and
>>> terasort
>>> - built from source tarball with -Pnative on CentOS 7 and OpenJDK 7
>>> - built site documentation and skimmed the contents
>>>
>>> Thanks,
>>> Masatake Iwasaki
>>>
>>>
>>>
>>> On 12/17/15 11:49, Vinod Kumar Vavilapalli wrote:
>>>
>>>> Hi all,
>>>>
>>>> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>>>>
>>>> As discussed before, this is the next maintenance release to follow up
>>>> 2.7.1.
>>>>
>>>> The RC is available for validation at:
>>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <
>>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>>>>
>>>> The RC tag in git is: release-2.7.2-RC1
>>>>
>>>> The maven artifacts are available via repository.apache.org <
>>>> http://repository.apache.org/> at
>>>>
>> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
>>>> <
>> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
>>>>>
>>>>
>>>> The release-notes are inside the tar-balls at location
>>>> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I
>>>> hosted this at
>>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html
>> for
>>>> quick perusal.
>>>>
>>>> As you may have noted,
>>>> - The RC0 related voting thread got halted due to some critical
>> issues.
>>>> It took a while again for getting all those blockers out of the way. See
>>>> the previous voting thread [3] for details.
>>>> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by
>>>> quite a bit. This release's related discussion threads are linked below:
>>>> [1] and [2].
>>>>
>>>> Please try the release and vote; the vote will run for the usual 5 days.
>>>>
>>>> Thanks,
>>>> Vinod
>>>>
>>>> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <
>>>> http://markmail.org/message/oozq3gvd4nhzsaes>
>>>> [2]: Planning Apache Hadoop 2.7.2
>>>> http://markmail.org/message/iktqss2qdeykgpqk <
>>>> http://markmail.org/message/iktqss2qdeykgpqk>
>>>> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
>>>> http://markmail.org/message/5txhvr2qdiqglrwc
>>>>
>>>>
>>>>
>>>
>>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Chen He <ai...@gmail.com>.
I see, thank you for the reply, Mr. Tsuyoshi Ozawa
Regards
Chen
Chen He@Oracle from Samsung Mega
On Dec 21, 2015 7:35 PM, "Tsuyoshi Ozawa" <oz...@apache.org> wrote:
> Hi Chen,
>
> > Kindly ask a silly question, why we separate 2.6.x from 2.7.x?
>
> 2.6.x is the last release which supports JDK6.
>
> Thanks,
> - Tsuyoshi
>
> On Tue, Dec 22, 2015 at 9:25 AM, Chen He <ai...@gmail.com> wrote:
> > +1 (non-binding)
> >
> > deploy to a 2-node cluster
> > run loadgen and wc without problem
> >
> >
> > Kindly ask a silly question, why we separate 2.6.x from 2.7.x?
> >
> > On Mon, Dec 21, 2015 at 11:51 AM, Wangda Tan <wh...@gmail.com>
> wrote:
> >
> >> +1 (binding)
> >>
> >> - Build & deploy single-node Hadoop from source code
> >> - Add/Remove node labels to queues/nodes
> >> - Run distributed shell commanding using default/specified node labels
> >>
> >> Thanks,
> >> Wangda
> >>
> >>
> >> On Mon, Dec 21, 2015 at 9:58 AM, Masatake Iwasaki <
> >> iwasakims@oss.nttdata.co.jp> wrote:
> >>
> >> > +1(non-binding)
> >> >
> >> > - verified mds and signature of source and binary tarball
> >> > - started 3 node cluster and ran example jobs such as wordcount and
> >> > terasort
> >> > - built from source tarball with -Pnative on CentOS 7 and OpenJDK 7
> >> > - built site documentation and skimmed the contents
> >> >
> >> > Thanks,
> >> > Masatake Iwasaki
> >> >
> >> >
> >> >
> >> > On 12/17/15 11:49, Vinod Kumar Vavilapalli wrote:
> >> >
> >> >> Hi all,
> >> >>
> >> >> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
> >> >>
> >> >> As discussed before, this is the next maintenance release to follow
> up
> >> >> 2.7.1.
> >> >>
> >> >> The RC is available for validation at:
> >> >> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <
> >> >> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
> >> >>
> >> >> The RC tag in git is: release-2.7.2-RC1
> >> >>
> >> >> The maven artifacts are available via repository.apache.org <
> >> >> http://repository.apache.org/> at
> >> >>
> >>
> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
> >> >> <
> >>
> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
> >> >> >
> >> >>
> >> >> The release-notes are inside the tar-balls at location
> >> >> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html.
> I
> >> >> hosted this at
> >> >> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html
> >> for
> >> >> quick perusal.
> >> >>
> >> >> As you may have noted,
> >> >> - The RC0 related voting thread got halted due to some critical
> >> issues.
> >> >> It took a while again for getting all those blockers out of the way.
> See
> >> >> the previous voting thread [3] for details.
> >> >> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip
> by
> >> >> quite a bit. This release's related discussion threads are linked
> below:
> >> >> [1] and [2].
> >> >>
> >> >> Please try the release and vote; the vote will run for the usual 5
> days.
> >> >>
> >> >> Thanks,
> >> >> Vinod
> >> >>
> >> >> [1]: 2.7.2 release plan:
> http://markmail.org/message/oozq3gvd4nhzsaes <
> >> >> http://markmail.org/message/oozq3gvd4nhzsaes>
> >> >> [2]: Planning Apache Hadoop 2.7.2
> >> >> http://markmail.org/message/iktqss2qdeykgpqk <
> >> >> http://markmail.org/message/iktqss2qdeykgpqk>
> >> >> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
> >> >> http://markmail.org/message/5txhvr2qdiqglrwc
> >> >>
> >> >>
> >> >>
> >> >
> >>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Tsuyoshi Ozawa <oz...@apache.org>.
Hi Chen,
> Kindly ask a silly question, why we separate 2.6.x from 2.7.x?
2.6.x is the last release which supports JDK6.
Thanks,
- Tsuyoshi
On Tue, Dec 22, 2015 at 9:25 AM, Chen He <ai...@gmail.com> wrote:
> +1 (non-binding)
>
> deploy to a 2-node cluster
> run loadgen and wc without problem
>
>
> Kindly ask a silly question, why we separate 2.6.x from 2.7.x?
>
> On Mon, Dec 21, 2015 at 11:51 AM, Wangda Tan <wh...@gmail.com> wrote:
>
>> +1 (binding)
>>
>> - Build & deploy single-node Hadoop from source code
>> - Add/Remove node labels to queues/nodes
>> - Run distributed shell commanding using default/specified node labels
>>
>> Thanks,
>> Wangda
>>
>>
>> On Mon, Dec 21, 2015 at 9:58 AM, Masatake Iwasaki <
>> iwasakims@oss.nttdata.co.jp> wrote:
>>
>> > +1(non-binding)
>> >
>> > - verified mds and signature of source and binary tarball
>> > - started 3 node cluster and ran example jobs such as wordcount and
>> > terasort
>> > - built from source tarball with -Pnative on CentOS 7 and OpenJDK 7
>> > - built site documentation and skimmed the contents
>> >
>> > Thanks,
>> > Masatake Iwasaki
>> >
>> >
>> >
>> > On 12/17/15 11:49, Vinod Kumar Vavilapalli wrote:
>> >
>> >> Hi all,
>> >>
>> >> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>> >>
>> >> As discussed before, this is the next maintenance release to follow up
>> >> 2.7.1.
>> >>
>> >> The RC is available for validation at:
>> >> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <
>> >> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>> >>
>> >> The RC tag in git is: release-2.7.2-RC1
>> >>
>> >> The maven artifacts are available via repository.apache.org <
>> >> http://repository.apache.org/> at
>> >>
>> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
>> >> <
>> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
>> >> >
>> >>
>> >> The release-notes are inside the tar-balls at location
>> >> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I
>> >> hosted this at
>> >> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html
>> for
>> >> quick perusal.
>> >>
>> >> As you may have noted,
>> >> - The RC0 related voting thread got halted due to some critical
>> issues.
>> >> It took a while again for getting all those blockers out of the way. See
>> >> the previous voting thread [3] for details.
>> >> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by
>> >> quite a bit. This release's related discussion threads are linked below:
>> >> [1] and [2].
>> >>
>> >> Please try the release and vote; the vote will run for the usual 5 days.
>> >>
>> >> Thanks,
>> >> Vinod
>> >>
>> >> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <
>> >> http://markmail.org/message/oozq3gvd4nhzsaes>
>> >> [2]: Planning Apache Hadoop 2.7.2
>> >> http://markmail.org/message/iktqss2qdeykgpqk <
>> >> http://markmail.org/message/iktqss2qdeykgpqk>
>> >> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
>> >> http://markmail.org/message/5txhvr2qdiqglrwc
>> >>
>> >>
>> >>
>> >
>>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Chen He <ai...@gmail.com>.
+1 (non-binding)
deploy to a 2-node cluster
run loadgen and wc without problem
Kindly ask a silly question, why we separate 2.6.x from 2.7.x?
On Mon, Dec 21, 2015 at 11:51 AM, Wangda Tan <wh...@gmail.com> wrote:
> +1 (binding)
>
> - Build & deploy single-node Hadoop from source code
> - Add/Remove node labels to queues/nodes
> - Run distributed shell commanding using default/specified node labels
>
> Thanks,
> Wangda
>
>
> On Mon, Dec 21, 2015 at 9:58 AM, Masatake Iwasaki <
> iwasakims@oss.nttdata.co.jp> wrote:
>
> > +1(non-binding)
> >
> > - verified mds and signature of source and binary tarball
> > - started 3 node cluster and ran example jobs such as wordcount and
> > terasort
> > - built from source tarball with -Pnative on CentOS 7 and OpenJDK 7
> > - built site documentation and skimmed the contents
> >
> > Thanks,
> > Masatake Iwasaki
> >
> >
> >
> > On 12/17/15 11:49, Vinod Kumar Vavilapalli wrote:
> >
> >> Hi all,
> >>
> >> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
> >>
> >> As discussed before, this is the next maintenance release to follow up
> >> 2.7.1.
> >>
> >> The RC is available for validation at:
> >> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <
> >> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
> >>
> >> The RC tag in git is: release-2.7.2-RC1
> >>
> >> The maven artifacts are available via repository.apache.org <
> >> http://repository.apache.org/> at
> >>
> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
> >> <
> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
> >> >
> >>
> >> The release-notes are inside the tar-balls at location
> >> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I
> >> hosted this at
> >> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html
> for
> >> quick perusal.
> >>
> >> As you may have noted,
> >> - The RC0 related voting thread got halted due to some critical
> issues.
> >> It took a while again for getting all those blockers out of the way. See
> >> the previous voting thread [3] for details.
> >> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by
> >> quite a bit. This release's related discussion threads are linked below:
> >> [1] and [2].
> >>
> >> Please try the release and vote; the vote will run for the usual 5 days.
> >>
> >> Thanks,
> >> Vinod
> >>
> >> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <
> >> http://markmail.org/message/oozq3gvd4nhzsaes>
> >> [2]: Planning Apache Hadoop 2.7.2
> >> http://markmail.org/message/iktqss2qdeykgpqk <
> >> http://markmail.org/message/iktqss2qdeykgpqk>
> >> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
> >> http://markmail.org/message/5txhvr2qdiqglrwc
> >>
> >>
> >>
> >
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Tsuyoshi Ozawa <oz...@apache.org>.
+1
- downloaded src and bin tar balls and verified signatures.
- built Tez and Spark with 2.7.2 artifacts and JDK7.
- ran tests of Tez with 2.7.2 artifacts, it passed.
FYI: YARN-4348, reported by Jian, is one of critical issues of 2.7.2
release.It's better to release 2.7.3 as soon as possible after this
release.
Thanks,
- Tsuyoshi
On Tue, Dec 22, 2015 at 4:51 AM, Wangda Tan <wh...@gmail.com> wrote:
> +1 (binding)
>
> - Build & deploy single-node Hadoop from source code
> - Add/Remove node labels to queues/nodes
> - Run distributed shell commanding using default/specified node labels
>
> Thanks,
> Wangda
>
>
> On Mon, Dec 21, 2015 at 9:58 AM, Masatake Iwasaki <
> iwasakims@oss.nttdata.co.jp> wrote:
>
>> +1(non-binding)
>>
>> - verified mds and signature of source and binary tarball
>> - started 3 node cluster and ran example jobs such as wordcount and
>> terasort
>> - built from source tarball with -Pnative on CentOS 7 and OpenJDK 7
>> - built site documentation and skimmed the contents
>>
>> Thanks,
>> Masatake Iwasaki
>>
>>
>>
>> On 12/17/15 11:49, Vinod Kumar Vavilapalli wrote:
>>
>>> Hi all,
>>>
>>> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>>>
>>> As discussed before, this is the next maintenance release to follow up
>>> 2.7.1.
>>>
>>> The RC is available for validation at:
>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <
>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>>>
>>> The RC tag in git is: release-2.7.2-RC1
>>>
>>> The maven artifacts are available via repository.apache.org <
>>> http://repository.apache.org/> at
>>> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
>>> <https://repository.apache.org/content/repositories/orgapachehadoop-1026/
>>> >
>>>
>>> The release-notes are inside the tar-balls at location
>>> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I
>>> hosted this at
>>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for
>>> quick perusal.
>>>
>>> As you may have noted,
>>> - The RC0 related voting thread got halted due to some critical issues.
>>> It took a while again for getting all those blockers out of the way. See
>>> the previous voting thread [3] for details.
>>> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by
>>> quite a bit. This release's related discussion threads are linked below:
>>> [1] and [2].
>>>
>>> Please try the release and vote; the vote will run for the usual 5 days.
>>>
>>> Thanks,
>>> Vinod
>>>
>>> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <
>>> http://markmail.org/message/oozq3gvd4nhzsaes>
>>> [2]: Planning Apache Hadoop 2.7.2
>>> http://markmail.org/message/iktqss2qdeykgpqk <
>>> http://markmail.org/message/iktqss2qdeykgpqk>
>>> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
>>> http://markmail.org/message/5txhvr2qdiqglrwc
>>>
>>>
>>>
>>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Wangda Tan <wh...@gmail.com>.
+1 (binding)
- Build & deploy single-node Hadoop from source code
- Add/Remove node labels to queues/nodes
- Run distributed shell commanding using default/specified node labels
Thanks,
Wangda
On Mon, Dec 21, 2015 at 9:58 AM, Masatake Iwasaki <
iwasakims@oss.nttdata.co.jp> wrote:
> +1(non-binding)
>
> - verified mds and signature of source and binary tarball
> - started 3 node cluster and ran example jobs such as wordcount and
> terasort
> - built from source tarball with -Pnative on CentOS 7 and OpenJDK 7
> - built site documentation and skimmed the contents
>
> Thanks,
> Masatake Iwasaki
>
>
>
> On 12/17/15 11:49, Vinod Kumar Vavilapalli wrote:
>
>> Hi all,
>>
>> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>>
>> As discussed before, this is the next maintenance release to follow up
>> 2.7.1.
>>
>> The RC is available for validation at:
>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <
>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>>
>> The RC tag in git is: release-2.7.2-RC1
>>
>> The maven artifacts are available via repository.apache.org <
>> http://repository.apache.org/> at
>> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
>> <https://repository.apache.org/content/repositories/orgapachehadoop-1026/
>> >
>>
>> The release-notes are inside the tar-balls at location
>> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I
>> hosted this at
>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for
>> quick perusal.
>>
>> As you may have noted,
>> - The RC0 related voting thread got halted due to some critical issues.
>> It took a while again for getting all those blockers out of the way. See
>> the previous voting thread [3] for details.
>> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by
>> quite a bit. This release's related discussion threads are linked below:
>> [1] and [2].
>>
>> Please try the release and vote; the vote will run for the usual 5 days.
>>
>> Thanks,
>> Vinod
>>
>> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <
>> http://markmail.org/message/oozq3gvd4nhzsaes>
>> [2]: Planning Apache Hadoop 2.7.2
>> http://markmail.org/message/iktqss2qdeykgpqk <
>> http://markmail.org/message/iktqss2qdeykgpqk>
>> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
>> http://markmail.org/message/5txhvr2qdiqglrwc
>>
>>
>>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Wangda Tan <wh...@gmail.com>.
+1 (binding)
- Build & deploy single-node Hadoop from source code
- Add/Remove node labels to queues/nodes
- Run distributed shell commanding using default/specified node labels
Thanks,
Wangda
On Mon, Dec 21, 2015 at 9:58 AM, Masatake Iwasaki <
iwasakims@oss.nttdata.co.jp> wrote:
> +1(non-binding)
>
> - verified mds and signature of source and binary tarball
> - started 3 node cluster and ran example jobs such as wordcount and
> terasort
> - built from source tarball with -Pnative on CentOS 7 and OpenJDK 7
> - built site documentation and skimmed the contents
>
> Thanks,
> Masatake Iwasaki
>
>
>
> On 12/17/15 11:49, Vinod Kumar Vavilapalli wrote:
>
>> Hi all,
>>
>> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>>
>> As discussed before, this is the next maintenance release to follow up
>> 2.7.1.
>>
>> The RC is available for validation at:
>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <
>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>>
>> The RC tag in git is: release-2.7.2-RC1
>>
>> The maven artifacts are available via repository.apache.org <
>> http://repository.apache.org/> at
>> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
>> <https://repository.apache.org/content/repositories/orgapachehadoop-1026/
>> >
>>
>> The release-notes are inside the tar-balls at location
>> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I
>> hosted this at
>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for
>> quick perusal.
>>
>> As you may have noted,
>> - The RC0 related voting thread got halted due to some critical issues.
>> It took a while again for getting all those blockers out of the way. See
>> the previous voting thread [3] for details.
>> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by
>> quite a bit. This release's related discussion threads are linked below:
>> [1] and [2].
>>
>> Please try the release and vote; the vote will run for the usual 5 days.
>>
>> Thanks,
>> Vinod
>>
>> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <
>> http://markmail.org/message/oozq3gvd4nhzsaes>
>> [2]: Planning Apache Hadoop 2.7.2
>> http://markmail.org/message/iktqss2qdeykgpqk <
>> http://markmail.org/message/iktqss2qdeykgpqk>
>> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
>> http://markmail.org/message/5txhvr2qdiqglrwc
>>
>>
>>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Wangda Tan <wh...@gmail.com>.
+1 (binding)
- Build & deploy single-node Hadoop from source code
- Add/Remove node labels to queues/nodes
- Run distributed shell commanding using default/specified node labels
Thanks,
Wangda
On Mon, Dec 21, 2015 at 9:58 AM, Masatake Iwasaki <
iwasakims@oss.nttdata.co.jp> wrote:
> +1(non-binding)
>
> - verified mds and signature of source and binary tarball
> - started 3 node cluster and ran example jobs such as wordcount and
> terasort
> - built from source tarball with -Pnative on CentOS 7 and OpenJDK 7
> - built site documentation and skimmed the contents
>
> Thanks,
> Masatake Iwasaki
>
>
>
> On 12/17/15 11:49, Vinod Kumar Vavilapalli wrote:
>
>> Hi all,
>>
>> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>>
>> As discussed before, this is the next maintenance release to follow up
>> 2.7.1.
>>
>> The RC is available for validation at:
>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <
>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>>
>> The RC tag in git is: release-2.7.2-RC1
>>
>> The maven artifacts are available via repository.apache.org <
>> http://repository.apache.org/> at
>> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
>> <https://repository.apache.org/content/repositories/orgapachehadoop-1026/
>> >
>>
>> The release-notes are inside the tar-balls at location
>> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I
>> hosted this at
>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for
>> quick perusal.
>>
>> As you may have noted,
>> - The RC0 related voting thread got halted due to some critical issues.
>> It took a while again for getting all those blockers out of the way. See
>> the previous voting thread [3] for details.
>> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by
>> quite a bit. This release's related discussion threads are linked below:
>> [1] and [2].
>>
>> Please try the release and vote; the vote will run for the usual 5 days.
>>
>> Thanks,
>> Vinod
>>
>> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <
>> http://markmail.org/message/oozq3gvd4nhzsaes>
>> [2]: Planning Apache Hadoop 2.7.2
>> http://markmail.org/message/iktqss2qdeykgpqk <
>> http://markmail.org/message/iktqss2qdeykgpqk>
>> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
>> http://markmail.org/message/5txhvr2qdiqglrwc
>>
>>
>>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Wangda Tan <wh...@gmail.com>.
+1 (binding)
- Build & deploy single-node Hadoop from source code
- Add/Remove node labels to queues/nodes
- Run distributed shell commanding using default/specified node labels
Thanks,
Wangda
On Mon, Dec 21, 2015 at 9:58 AM, Masatake Iwasaki <
iwasakims@oss.nttdata.co.jp> wrote:
> +1(non-binding)
>
> - verified mds and signature of source and binary tarball
> - started 3 node cluster and ran example jobs such as wordcount and
> terasort
> - built from source tarball with -Pnative on CentOS 7 and OpenJDK 7
> - built site documentation and skimmed the contents
>
> Thanks,
> Masatake Iwasaki
>
>
>
> On 12/17/15 11:49, Vinod Kumar Vavilapalli wrote:
>
>> Hi all,
>>
>> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>>
>> As discussed before, this is the next maintenance release to follow up
>> 2.7.1.
>>
>> The RC is available for validation at:
>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <
>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>>
>> The RC tag in git is: release-2.7.2-RC1
>>
>> The maven artifacts are available via repository.apache.org <
>> http://repository.apache.org/> at
>> https://repository.apache.org/content/repositories/orgapachehadoop-1026/
>> <https://repository.apache.org/content/repositories/orgapachehadoop-1026/
>> >
>>
>> The release-notes are inside the tar-balls at location
>> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I
>> hosted this at
>> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for
>> quick perusal.
>>
>> As you may have noted,
>> - The RC0 related voting thread got halted due to some critical issues.
>> It took a while again for getting all those blockers out of the way. See
>> the previous voting thread [3] for details.
>> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by
>> quite a bit. This release's related discussion threads are linked below:
>> [1] and [2].
>>
>> Please try the release and vote; the vote will run for the usual 5 days.
>>
>> Thanks,
>> Vinod
>>
>> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <
>> http://markmail.org/message/oozq3gvd4nhzsaes>
>> [2]: Planning Apache Hadoop 2.7.2
>> http://markmail.org/message/iktqss2qdeykgpqk <
>> http://markmail.org/message/iktqss2qdeykgpqk>
>> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
>> http://markmail.org/message/5txhvr2qdiqglrwc
>>
>>
>>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Masatake Iwasaki <iw...@oss.nttdata.co.jp>.
+1(non-binding)
- verified mds and signature of source and binary tarball
- started 3 node cluster and ran example jobs such as wordcount and terasort
- built from source tarball with -Pnative on CentOS 7 and OpenJDK 7
- built site documentation and skimmed the contents
Thanks,
Masatake Iwasaki
On 12/17/15 11:49, Vinod Kumar Vavilapalli wrote:
> Hi all,
>
> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>
> As discussed before, this is the next maintenance release to follow up 2.7.1.
>
> The RC is available for validation at: http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>
> The RC tag in git is: release-2.7.2-RC1
>
> The maven artifacts are available via repository.apache.org <http://repository.apache.org/> at https://repository.apache.org/content/repositories/orgapachehadoop-1026/ <https://repository.apache.org/content/repositories/orgapachehadoop-1026/>
>
> The release-notes are inside the tar-balls at location hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I hosted this at http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for quick perusal.
>
> As you may have noted,
> - The RC0 related voting thread got halted due to some critical issues. It took a while again for getting all those blockers out of the way. See the previous voting thread [3] for details.
> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by quite a bit. This release's related discussion threads are linked below: [1] and [2].
>
> Please try the release and vote; the vote will run for the usual 5 days.
>
> Thanks,
> Vinod
>
> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <http://markmail.org/message/oozq3gvd4nhzsaes>
> [2]: Planning Apache Hadoop 2.7.2 http://markmail.org/message/iktqss2qdeykgpqk <http://markmail.org/message/iktqss2qdeykgpqk>
> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0: http://markmail.org/message/5txhvr2qdiqglrwc
>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Arpit Agarwal <aa...@hortonworks.com>.
Thanks for putting together this release Vinod.
+1 (binding)
- Verified signatures
- Started pseudo-cluster with binary distribution, verified git commit ID
- Built sources, deployed pseudo-cluster and ran example map reduce jobs, DistributedShell, HDFS commands.
PS: Extra file hadoop-2.7.2-RC1-src.tar.gz.md5?
On 12/16/15, 6:49 PM, "Vinod Kumar Vavilapalli" <vi...@apache.org> wrote:
>Hi all,
>
>I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>
>As discussed before, this is the next maintenance release to follow up 2.7.1.
>
>The RC is available for validation at: http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>
>The RC tag in git is: release-2.7.2-RC1
>
>The maven artifacts are available via repository.apache.org <http://repository.apache.org/> at https://repository.apache.org/content/repositories/orgapachehadoop-1026/ <https://repository.apache.org/content/repositories/orgapachehadoop-1026/>
>
>The release-notes are inside the tar-balls at location hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I hosted this at http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for quick perusal.
>
>As you may have noted,
> - The RC0 related voting thread got halted due to some critical issues. It took a while again for getting all those blockers out of the way. See the previous voting thread [3] for details.
> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by quite a bit. This release's related discussion threads are linked below: [1] and [2].
>
>Please try the release and vote; the vote will run for the usual 5 days.
>
>Thanks,
>Vinod
>
>[1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <http://markmail.org/message/oozq3gvd4nhzsaes>
>[2]: Planning Apache Hadoop 2.7.2 http://markmail.org/message/iktqss2qdeykgpqk <http://markmail.org/message/iktqss2qdeykgpqk>
>[3]: [VOTE] Release Apache Hadoop 2.7.2 RC0: http://markmail.org/message/5txhvr2qdiqglrwc
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Arpit Agarwal <aa...@hortonworks.com>.
Thanks for putting together this release Vinod.
+1 (binding)
- Verified signatures
- Started pseudo-cluster with binary distribution, verified git commit ID
- Built sources, deployed pseudo-cluster and ran example map reduce jobs, DistributedShell, HDFS commands.
PS: Extra file hadoop-2.7.2-RC1-src.tar.gz.md5?
On 12/16/15, 6:49 PM, "Vinod Kumar Vavilapalli" <vi...@apache.org> wrote:
>Hi all,
>
>I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>
>As discussed before, this is the next maintenance release to follow up 2.7.1.
>
>The RC is available for validation at: http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>
>The RC tag in git is: release-2.7.2-RC1
>
>The maven artifacts are available via repository.apache.org <http://repository.apache.org/> at https://repository.apache.org/content/repositories/orgapachehadoop-1026/ <https://repository.apache.org/content/repositories/orgapachehadoop-1026/>
>
>The release-notes are inside the tar-balls at location hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I hosted this at http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for quick perusal.
>
>As you may have noted,
> - The RC0 related voting thread got halted due to some critical issues. It took a while again for getting all those blockers out of the way. See the previous voting thread [3] for details.
> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by quite a bit. This release's related discussion threads are linked below: [1] and [2].
>
>Please try the release and vote; the vote will run for the usual 5 days.
>
>Thanks,
>Vinod
>
>[1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <http://markmail.org/message/oozq3gvd4nhzsaes>
>[2]: Planning Apache Hadoop 2.7.2 http://markmail.org/message/iktqss2qdeykgpqk <http://markmail.org/message/iktqss2qdeykgpqk>
>[3]: [VOTE] Release Apache Hadoop 2.7.2 RC0: http://markmail.org/message/5txhvr2qdiqglrwc
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Jason Lowe <jl...@yahoo-inc.com.INVALID>.
+1 (binding)
- Verified signatures and digests- Spot checked CHANGES.txt files- Successfully performed a native build from source- Deployed to a single node cluster and ran sample jobs
We have been running with the fix for YARN-4354 on two of our clusters for some time with no issues, so I feel confident that prior blocker is now fixed.
Jason
From: Vinod Kumar Vavilapalli <vi...@apache.org>
To: Hadoop Common <co...@hadoop.apache.org>; hdfs-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org
Cc: Vinod Kumar Vavilapalli <vi...@apache.org>
Sent: Wednesday, December 16, 2015 8:49 PM
Subject: [VOTE] Release Apache Hadoop 2.7.2 RC1
Hi all,
I've created a release candidate RC1 for Apache Hadoop 2.7.2.
As discussed before, this is the next maintenance release to follow up 2.7.1.
The RC is available for validation at: http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
The RC tag in git is: release-2.7.2-RC1
The maven artifacts are available via repository.apache.org <http://repository.apache.org/> at https://repository.apache.org/content/repositories/orgapachehadoop-1026/ <https://repository.apache.org/content/repositories/orgapachehadoop-1026/>
The release-notes are inside the tar-balls at location hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I hosted this at http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for quick perusal.
As you may have noted,
- The RC0 related voting thread got halted due to some critical issues. It took a while again for getting all those blockers out of the way. See the previous voting thread [3] for details.
- Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by quite a bit. This release's related discussion threads are linked below: [1] and [2].
Please try the release and vote; the vote will run for the usual 5 days.
Thanks,
Vinod
[1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <http://markmail.org/message/oozq3gvd4nhzsaes>
[2]: Planning Apache Hadoop 2.7.2 http://markmail.org/message/iktqss2qdeykgpqk <http://markmail.org/message/iktqss2qdeykgpqk>
[3]: [VOTE] Release Apache Hadoop 2.7.2 RC0: http://markmail.org/message/5txhvr2qdiqglrwc
RE: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Brahma Reddy Battula <br...@hotmail.com>.
+1 (Non binding)Downloaded source tarball Verified signatures and checksums Installed pseudo cluster and 3 Node Ha Cluster Done Regression Test blocker Issues.Did some basic filesystem operationsRan a pi, terasort, word count successfully
Thanks And RegardsBrahma Reddy Battula
> Date: Mon, 21 Dec 2015 17:41:42 +0000
> From: kihwal@yahoo-inc.com.INVALID
> To: common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org
> CC: vinodkv@apache.org
> Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
>
> +1 (binding)- Verified the signature/digest.
> - I've built the dist tree with the native support from the source.- Brought up a single node cluster and ran a set of basic tests.
>
>
>
> From: Vinod Kumar Vavilapalli <vi...@apache.org>
> To: Hadoop Common <co...@hadoop.apache.org>; hdfs-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org
> Cc: Vinod Kumar Vavilapalli <vi...@apache.org>
> Sent: Wednesday, December 16, 2015 8:49 PM
> Subject: [VOTE] Release Apache Hadoop 2.7.2 RC1
>
> Hi all,
>
> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>
> As discussed before, this is the next maintenance release to follow up 2.7.1.
>
> The RC is available for validation at: http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>
> The RC tag in git is: release-2.7.2-RC1
>
> The maven artifacts are available via repository.apache.org <http://repository.apache.org/> at https://repository.apache.org/content/repositories/orgapachehadoop-1026/ <https://repository.apache.org/content/repositories/orgapachehadoop-1026/>
>
> The release-notes are inside the tar-balls at location hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I hosted this at http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for quick perusal.
>
> As you may have noted,
> - The RC0 related voting thread got halted due to some critical issues. It took a while again for getting all those blockers out of the way. See the previous voting thread [3] for details.
> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by quite a bit. This release's related discussion threads are linked below: [1] and [2].
>
> Please try the release and vote; the vote will run for the usual 5 days.
>
> Thanks,
> Vinod
>
> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <http://markmail.org/message/oozq3gvd4nhzsaes>
> [2]: Planning Apache Hadoop 2.7.2 http://markmail.org/message/iktqss2qdeykgpqk <http://markmail.org/message/iktqss2qdeykgpqk>
> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0: http://markmail.org/message/5txhvr2qdiqglrwc
>
>
>
RE: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Brahma Reddy Battula <br...@hotmail.com>.
+1 (Non binding)Downloaded source tarball Verified signatures and checksums Installed pseudo cluster and 3 Node Ha Cluster Done Regression Test blocker Issues.Did some basic filesystem operationsRan a pi, terasort, word count successfully
Thanks And RegardsBrahma Reddy Battula
> Date: Mon, 21 Dec 2015 17:41:42 +0000
> From: kihwal@yahoo-inc.com.INVALID
> To: common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org
> CC: vinodkv@apache.org
> Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
>
> +1 (binding)- Verified the signature/digest.
> - I've built the dist tree with the native support from the source.- Brought up a single node cluster and ran a set of basic tests.
>
>
>
> From: Vinod Kumar Vavilapalli <vi...@apache.org>
> To: Hadoop Common <co...@hadoop.apache.org>; hdfs-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org
> Cc: Vinod Kumar Vavilapalli <vi...@apache.org>
> Sent: Wednesday, December 16, 2015 8:49 PM
> Subject: [VOTE] Release Apache Hadoop 2.7.2 RC1
>
> Hi all,
>
> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>
> As discussed before, this is the next maintenance release to follow up 2.7.1.
>
> The RC is available for validation at: http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>
> The RC tag in git is: release-2.7.2-RC1
>
> The maven artifacts are available via repository.apache.org <http://repository.apache.org/> at https://repository.apache.org/content/repositories/orgapachehadoop-1026/ <https://repository.apache.org/content/repositories/orgapachehadoop-1026/>
>
> The release-notes are inside the tar-balls at location hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I hosted this at http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for quick perusal.
>
> As you may have noted,
> - The RC0 related voting thread got halted due to some critical issues. It took a while again for getting all those blockers out of the way. See the previous voting thread [3] for details.
> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by quite a bit. This release's related discussion threads are linked below: [1] and [2].
>
> Please try the release and vote; the vote will run for the usual 5 days.
>
> Thanks,
> Vinod
>
> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <http://markmail.org/message/oozq3gvd4nhzsaes>
> [2]: Planning Apache Hadoop 2.7.2 http://markmail.org/message/iktqss2qdeykgpqk <http://markmail.org/message/iktqss2qdeykgpqk>
> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0: http://markmail.org/message/5txhvr2qdiqglrwc
>
>
>
RE: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Brahma Reddy Battula <br...@hotmail.com>.
+1 (Non binding)Downloaded source tarball Verified signatures and checksums Installed pseudo cluster and 3 Node Ha Cluster Done Regression Test blocker Issues.Did some basic filesystem operationsRan a pi, terasort, word count successfully
Thanks And RegardsBrahma Reddy Battula
> Date: Mon, 21 Dec 2015 17:41:42 +0000
> From: kihwal@yahoo-inc.com.INVALID
> To: common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org
> CC: vinodkv@apache.org
> Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
>
> +1 (binding)- Verified the signature/digest.
> - I've built the dist tree with the native support from the source.- Brought up a single node cluster and ran a set of basic tests.
>
>
>
> From: Vinod Kumar Vavilapalli <vi...@apache.org>
> To: Hadoop Common <co...@hadoop.apache.org>; hdfs-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org
> Cc: Vinod Kumar Vavilapalli <vi...@apache.org>
> Sent: Wednesday, December 16, 2015 8:49 PM
> Subject: [VOTE] Release Apache Hadoop 2.7.2 RC1
>
> Hi all,
>
> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>
> As discussed before, this is the next maintenance release to follow up 2.7.1.
>
> The RC is available for validation at: http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>
> The RC tag in git is: release-2.7.2-RC1
>
> The maven artifacts are available via repository.apache.org <http://repository.apache.org/> at https://repository.apache.org/content/repositories/orgapachehadoop-1026/ <https://repository.apache.org/content/repositories/orgapachehadoop-1026/>
>
> The release-notes are inside the tar-balls at location hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I hosted this at http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for quick perusal.
>
> As you may have noted,
> - The RC0 related voting thread got halted due to some critical issues. It took a while again for getting all those blockers out of the way. See the previous voting thread [3] for details.
> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by quite a bit. This release's related discussion threads are linked below: [1] and [2].
>
> Please try the release and vote; the vote will run for the usual 5 days.
>
> Thanks,
> Vinod
>
> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <http://markmail.org/message/oozq3gvd4nhzsaes>
> [2]: Planning Apache Hadoop 2.7.2 http://markmail.org/message/iktqss2qdeykgpqk <http://markmail.org/message/iktqss2qdeykgpqk>
> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0: http://markmail.org/message/5txhvr2qdiqglrwc
>
>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Kihwal Lee <ki...@yahoo-inc.com.INVALID>.
+1 (binding)- Verified the signature/digest.
- I've built the dist tree with the native support from the source.- Brought up a single node cluster and ran a set of basic tests.
From: Vinod Kumar Vavilapalli <vi...@apache.org>
To: Hadoop Common <co...@hadoop.apache.org>; hdfs-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org
Cc: Vinod Kumar Vavilapalli <vi...@apache.org>
Sent: Wednesday, December 16, 2015 8:49 PM
Subject: [VOTE] Release Apache Hadoop 2.7.2 RC1
Hi all,
I've created a release candidate RC1 for Apache Hadoop 2.7.2.
As discussed before, this is the next maintenance release to follow up 2.7.1.
The RC is available for validation at: http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
The RC tag in git is: release-2.7.2-RC1
The maven artifacts are available via repository.apache.org <http://repository.apache.org/> at https://repository.apache.org/content/repositories/orgapachehadoop-1026/ <https://repository.apache.org/content/repositories/orgapachehadoop-1026/>
The release-notes are inside the tar-balls at location hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I hosted this at http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for quick perusal.
As you may have noted,
- The RC0 related voting thread got halted due to some critical issues. It took a while again for getting all those blockers out of the way. See the previous voting thread [3] for details.
- Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by quite a bit. This release's related discussion threads are linked below: [1] and [2].
Please try the release and vote; the vote will run for the usual 5 days.
Thanks,
Vinod
[1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <http://markmail.org/message/oozq3gvd4nhzsaes>
[2]: Planning Apache Hadoop 2.7.2 http://markmail.org/message/iktqss2qdeykgpqk <http://markmail.org/message/iktqss2qdeykgpqk>
[3]: [VOTE] Release Apache Hadoop 2.7.2 RC0: http://markmail.org/message/5txhvr2qdiqglrwc
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Kihwal Lee <ki...@yahoo-inc.com.INVALID>.
+1 (binding)- Verified the signature/digest.
- I've built the dist tree with the native support from the source.- Brought up a single node cluster and ran a set of basic tests.
From: Vinod Kumar Vavilapalli <vi...@apache.org>
To: Hadoop Common <co...@hadoop.apache.org>; hdfs-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org
Cc: Vinod Kumar Vavilapalli <vi...@apache.org>
Sent: Wednesday, December 16, 2015 8:49 PM
Subject: [VOTE] Release Apache Hadoop 2.7.2 RC1
Hi all,
I've created a release candidate RC1 for Apache Hadoop 2.7.2.
As discussed before, this is the next maintenance release to follow up 2.7.1.
The RC is available for validation at: http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
The RC tag in git is: release-2.7.2-RC1
The maven artifacts are available via repository.apache.org <http://repository.apache.org/> at https://repository.apache.org/content/repositories/orgapachehadoop-1026/ <https://repository.apache.org/content/repositories/orgapachehadoop-1026/>
The release-notes are inside the tar-balls at location hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I hosted this at http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for quick perusal.
As you may have noted,
- The RC0 related voting thread got halted due to some critical issues. It took a while again for getting all those blockers out of the way. See the previous voting thread [3] for details.
- Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by quite a bit. This release's related discussion threads are linked below: [1] and [2].
Please try the release and vote; the vote will run for the usual 5 days.
Thanks,
Vinod
[1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <http://markmail.org/message/oozq3gvd4nhzsaes>
[2]: Planning Apache Hadoop 2.7.2 http://markmail.org/message/iktqss2qdeykgpqk <http://markmail.org/message/iktqss2qdeykgpqk>
[3]: [VOTE] Release Apache Hadoop 2.7.2 RC0: http://markmail.org/message/5txhvr2qdiqglrwc
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Mingliang Liu <ml...@hortonworks.com>.
+1 (non-binding)
1. Download the src tar file and validate the integrity
2. Build and configure the local cluster
3. Operate the HDFS from command line interface
4. Run several example MR jobs
5. Check logs
Thanks.
L
> On Dec 16, 2015, at 6:49 PM, Vinod Kumar Vavilapalli <vi...@apache.org> wrote:
>
> Hi all,
>
> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>
> As discussed before, this is the next maintenance release to follow up 2.7.1.
>
> The RC is available for validation at: http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>
> The RC tag in git is: release-2.7.2-RC1
>
> The maven artifacts are available via repository.apache.org <http://repository.apache.org/> at https://repository.apache.org/content/repositories/orgapachehadoop-1026/ <https://repository.apache.org/content/repositories/orgapachehadoop-1026/>
>
> The release-notes are inside the tar-balls at location hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I hosted this at http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for quick perusal.
>
> As you may have noted,
> - The RC0 related voting thread got halted due to some critical issues. It took a while again for getting all those blockers out of the way. See the previous voting thread [3] for details.
> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by quite a bit. This release's related discussion threads are linked below: [1] and [2].
>
> Please try the release and vote; the vote will run for the usual 5 days.
>
> Thanks,
> Vinod
>
> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <http://markmail.org/message/oozq3gvd4nhzsaes>
> [2]: Planning Apache Hadoop 2.7.2 http://markmail.org/message/iktqss2qdeykgpqk <http://markmail.org/message/iktqss2qdeykgpqk>
> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0: http://markmail.org/message/5txhvr2qdiqglrwc
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Masatake Iwasaki <iw...@oss.nttdata.co.jp>.
+1(non-binding)
- verified mds and signature of source and binary tarball
- started 3 node cluster and ran example jobs such as wordcount and terasort
- built from source tarball with -Pnative on CentOS 7 and OpenJDK 7
- built site documentation and skimmed the contents
Thanks,
Masatake Iwasaki
On 12/17/15 11:49, Vinod Kumar Vavilapalli wrote:
> Hi all,
>
> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>
> As discussed before, this is the next maintenance release to follow up 2.7.1.
>
> The RC is available for validation at: http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>
> The RC tag in git is: release-2.7.2-RC1
>
> The maven artifacts are available via repository.apache.org <http://repository.apache.org/> at https://repository.apache.org/content/repositories/orgapachehadoop-1026/ <https://repository.apache.org/content/repositories/orgapachehadoop-1026/>
>
> The release-notes are inside the tar-balls at location hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I hosted this at http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for quick perusal.
>
> As you may have noted,
> - The RC0 related voting thread got halted due to some critical issues. It took a while again for getting all those blockers out of the way. See the previous voting thread [3] for details.
> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by quite a bit. This release's related discussion threads are linked below: [1] and [2].
>
> Please try the release and vote; the vote will run for the usual 5 days.
>
> Thanks,
> Vinod
>
> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <http://markmail.org/message/oozq3gvd4nhzsaes>
> [2]: Planning Apache Hadoop 2.7.2 http://markmail.org/message/iktqss2qdeykgpqk <http://markmail.org/message/iktqss2qdeykgpqk>
> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0: http://markmail.org/message/5txhvr2qdiqglrwc
>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Ted Yu <yu...@gmail.com>.
Hi,
I have run test suite for tip of hbase 0.98 branch against this RC.
All tests passed.
+1
On Wed, Dec 16, 2015 at 6:49 PM, Vinod Kumar Vavilapalli <vinodkv@apache.org
> wrote:
> Hi all,
>
> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>
> As discussed before, this is the next maintenance release to follow up
> 2.7.1.
>
> The RC is available for validation at:
> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <
> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>
> The RC tag in git is: release-2.7.2-RC1
>
> The maven artifacts are available via repository.apache.org <
> http://repository.apache.org/> at
> https://repository.apache.org/content/repositories/orgapachehadoop-1026/ <
> https://repository.apache.org/content/repositories/orgapachehadoop-1026/>
>
> The release-notes are inside the tar-balls at location
> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I
> hosted this at
> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for
> quick perusal.
>
> As you may have noted,
> - The RC0 related voting thread got halted due to some critical issues.
> It took a while again for getting all those blockers out of the way. See
> the previous voting thread [3] for details.
> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by
> quite a bit. This release's related discussion threads are linked below:
> [1] and [2].
>
> Please try the release and vote; the vote will run for the usual 5 days.
>
> Thanks,
> Vinod
>
> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <
> http://markmail.org/message/oozq3gvd4nhzsaes>
> [2]: Planning Apache Hadoop 2.7.2
> http://markmail.org/message/iktqss2qdeykgpqk <
> http://markmail.org/message/iktqss2qdeykgpqk>
> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
> http://markmail.org/message/5txhvr2qdiqglrwc
>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Mingliang Liu <ml...@hortonworks.com>.
+1 (non-binding)
1. Download the src tar file and validate the integrity
2. Build and configure the local cluster
3. Operate the HDFS from command line interface
4. Run several example MR jobs
5. Check logs
Thanks.
L
> On Dec 16, 2015, at 6:49 PM, Vinod Kumar Vavilapalli <vi...@apache.org> wrote:
>
> Hi all,
>
> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>
> As discussed before, this is the next maintenance release to follow up 2.7.1.
>
> The RC is available for validation at: http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>
> The RC tag in git is: release-2.7.2-RC1
>
> The maven artifacts are available via repository.apache.org <http://repository.apache.org/> at https://repository.apache.org/content/repositories/orgapachehadoop-1026/ <https://repository.apache.org/content/repositories/orgapachehadoop-1026/>
>
> The release-notes are inside the tar-balls at location hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I hosted this at http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for quick perusal.
>
> As you may have noted,
> - The RC0 related voting thread got halted due to some critical issues. It took a while again for getting all those blockers out of the way. See the previous voting thread [3] for details.
> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by quite a bit. This release's related discussion threads are linked below: [1] and [2].
>
> Please try the release and vote; the vote will run for the usual 5 days.
>
> Thanks,
> Vinod
>
> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <http://markmail.org/message/oozq3gvd4nhzsaes>
> [2]: Planning Apache Hadoop 2.7.2 http://markmail.org/message/iktqss2qdeykgpqk <http://markmail.org/message/iktqss2qdeykgpqk>
> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0: http://markmail.org/message/5txhvr2qdiqglrwc
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Jason Lowe <jl...@yahoo-inc.com.INVALID>.
+1 (binding)
- Verified signatures and digests- Spot checked CHANGES.txt files- Successfully performed a native build from source- Deployed to a single node cluster and ran sample jobs
We have been running with the fix for YARN-4354 on two of our clusters for some time with no issues, so I feel confident that prior blocker is now fixed.
Jason
From: Vinod Kumar Vavilapalli <vi...@apache.org>
To: Hadoop Common <co...@hadoop.apache.org>; hdfs-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org
Cc: Vinod Kumar Vavilapalli <vi...@apache.org>
Sent: Wednesday, December 16, 2015 8:49 PM
Subject: [VOTE] Release Apache Hadoop 2.7.2 RC1
Hi all,
I've created a release candidate RC1 for Apache Hadoop 2.7.2.
As discussed before, this is the next maintenance release to follow up 2.7.1.
The RC is available for validation at: http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
The RC tag in git is: release-2.7.2-RC1
The maven artifacts are available via repository.apache.org <http://repository.apache.org/> at https://repository.apache.org/content/repositories/orgapachehadoop-1026/ <https://repository.apache.org/content/repositories/orgapachehadoop-1026/>
The release-notes are inside the tar-balls at location hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I hosted this at http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for quick perusal.
As you may have noted,
- The RC0 related voting thread got halted due to some critical issues. It took a while again for getting all those blockers out of the way. See the previous voting thread [3] for details.
- Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by quite a bit. This release's related discussion threads are linked below: [1] and [2].
Please try the release and vote; the vote will run for the usual 5 days.
Thanks,
Vinod
[1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <http://markmail.org/message/oozq3gvd4nhzsaes>
[2]: Planning Apache Hadoop 2.7.2 http://markmail.org/message/iktqss2qdeykgpqk <http://markmail.org/message/iktqss2qdeykgpqk>
[3]: [VOTE] Release Apache Hadoop 2.7.2 RC0: http://markmail.org/message/5txhvr2qdiqglrwc
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Ted Yu <yu...@gmail.com>.
Hi,
I have run test suite for tip of hbase 0.98 branch against this RC.
All tests passed.
+1
On Wed, Dec 16, 2015 at 6:49 PM, Vinod Kumar Vavilapalli <vinodkv@apache.org
> wrote:
> Hi all,
>
> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>
> As discussed before, this is the next maintenance release to follow up
> 2.7.1.
>
> The RC is available for validation at:
> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <
> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>
> The RC tag in git is: release-2.7.2-RC1
>
> The maven artifacts are available via repository.apache.org <
> http://repository.apache.org/> at
> https://repository.apache.org/content/repositories/orgapachehadoop-1026/ <
> https://repository.apache.org/content/repositories/orgapachehadoop-1026/>
>
> The release-notes are inside the tar-balls at location
> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I
> hosted this at
> http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for
> quick perusal.
>
> As you may have noted,
> - The RC0 related voting thread got halted due to some critical issues.
> It took a while again for getting all those blockers out of the way. See
> the previous voting thread [3] for details.
> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by
> quite a bit. This release's related discussion threads are linked below:
> [1] and [2].
>
> Please try the release and vote; the vote will run for the usual 5 days.
>
> Thanks,
> Vinod
>
> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <
> http://markmail.org/message/oozq3gvd4nhzsaes>
> [2]: Planning Apache Hadoop 2.7.2
> http://markmail.org/message/iktqss2qdeykgpqk <
> http://markmail.org/message/iktqss2qdeykgpqk>
> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0:
> http://markmail.org/message/5txhvr2qdiqglrwc
>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Arpit Agarwal <aa...@hortonworks.com>.
Thanks for putting together this release Vinod.
+1 (binding)
- Verified signatures
- Started pseudo-cluster with binary distribution, verified git commit ID
- Built sources, deployed pseudo-cluster and ran example map reduce jobs, DistributedShell, HDFS commands.
PS: Extra file hadoop-2.7.2-RC1-src.tar.gz.md5?
On 12/16/15, 6:49 PM, "Vinod Kumar Vavilapalli" <vi...@apache.org> wrote:
>Hi all,
>
>I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>
>As discussed before, this is the next maintenance release to follow up 2.7.1.
>
>The RC is available for validation at: http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>
>The RC tag in git is: release-2.7.2-RC1
>
>The maven artifacts are available via repository.apache.org <http://repository.apache.org/> at https://repository.apache.org/content/repositories/orgapachehadoop-1026/ <https://repository.apache.org/content/repositories/orgapachehadoop-1026/>
>
>The release-notes are inside the tar-balls at location hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I hosted this at http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for quick perusal.
>
>As you may have noted,
> - The RC0 related voting thread got halted due to some critical issues. It took a while again for getting all those blockers out of the way. See the previous voting thread [3] for details.
> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by quite a bit. This release's related discussion threads are linked below: [1] and [2].
>
>Please try the release and vote; the vote will run for the usual 5 days.
>
>Thanks,
>Vinod
>
>[1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <http://markmail.org/message/oozq3gvd4nhzsaes>
>[2]: Planning Apache Hadoop 2.7.2 http://markmail.org/message/iktqss2qdeykgpqk <http://markmail.org/message/iktqss2qdeykgpqk>
>[3]: [VOTE] Release Apache Hadoop 2.7.2 RC0: http://markmail.org/message/5txhvr2qdiqglrwc
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Kihwal Lee <ki...@yahoo-inc.com.INVALID>.
+1 (binding)- Verified the signature/digest.
- I've built the dist tree with the native support from the source.- Brought up a single node cluster and ran a set of basic tests.
From: Vinod Kumar Vavilapalli <vi...@apache.org>
To: Hadoop Common <co...@hadoop.apache.org>; hdfs-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org
Cc: Vinod Kumar Vavilapalli <vi...@apache.org>
Sent: Wednesday, December 16, 2015 8:49 PM
Subject: [VOTE] Release Apache Hadoop 2.7.2 RC1
Hi all,
I've created a release candidate RC1 for Apache Hadoop 2.7.2.
As discussed before, this is the next maintenance release to follow up 2.7.1.
The RC is available for validation at: http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
The RC tag in git is: release-2.7.2-RC1
The maven artifacts are available via repository.apache.org <http://repository.apache.org/> at https://repository.apache.org/content/repositories/orgapachehadoop-1026/ <https://repository.apache.org/content/repositories/orgapachehadoop-1026/>
The release-notes are inside the tar-balls at location hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I hosted this at http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for quick perusal.
As you may have noted,
- The RC0 related voting thread got halted due to some critical issues. It took a while again for getting all those blockers out of the way. See the previous voting thread [3] for details.
- Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by quite a bit. This release's related discussion threads are linked below: [1] and [2].
Please try the release and vote; the vote will run for the usual 5 days.
Thanks,
Vinod
[1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <http://markmail.org/message/oozq3gvd4nhzsaes>
[2]: Planning Apache Hadoop 2.7.2 http://markmail.org/message/iktqss2qdeykgpqk <http://markmail.org/message/iktqss2qdeykgpqk>
[3]: [VOTE] Release Apache Hadoop 2.7.2 RC0: http://markmail.org/message/5txhvr2qdiqglrwc
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Masatake Iwasaki <iw...@oss.nttdata.co.jp>.
+1(non-binding)
- verified mds and signature of source and binary tarball
- started 3 node cluster and ran example jobs such as wordcount and terasort
- built from source tarball with -Pnative on CentOS 7 and OpenJDK 7
- built site documentation and skimmed the contents
Thanks,
Masatake Iwasaki
On 12/17/15 11:49, Vinod Kumar Vavilapalli wrote:
> Hi all,
>
> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>
> As discussed before, this is the next maintenance release to follow up 2.7.1.
>
> The RC is available for validation at: http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>
> The RC tag in git is: release-2.7.2-RC1
>
> The maven artifacts are available via repository.apache.org <http://repository.apache.org/> at https://repository.apache.org/content/repositories/orgapachehadoop-1026/ <https://repository.apache.org/content/repositories/orgapachehadoop-1026/>
>
> The release-notes are inside the tar-balls at location hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I hosted this at http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for quick perusal.
>
> As you may have noted,
> - The RC0 related voting thread got halted due to some critical issues. It took a while again for getting all those blockers out of the way. See the previous voting thread [3] for details.
> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by quite a bit. This release's related discussion threads are linked below: [1] and [2].
>
> Please try the release and vote; the vote will run for the usual 5 days.
>
> Thanks,
> Vinod
>
> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <http://markmail.org/message/oozq3gvd4nhzsaes>
> [2]: Planning Apache Hadoop 2.7.2 http://markmail.org/message/iktqss2qdeykgpqk <http://markmail.org/message/iktqss2qdeykgpqk>
> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0: http://markmail.org/message/5txhvr2qdiqglrwc
>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Masatake Iwasaki <iw...@oss.nttdata.co.jp>.
+1(non-binding)
- verified mds and signature of source and binary tarball
- started 3 node cluster and ran example jobs such as wordcount and terasort
- built from source tarball with -Pnative on CentOS 7 and OpenJDK 7
- built site documentation and skimmed the contents
Thanks,
Masatake Iwasaki
On 12/17/15 11:49, Vinod Kumar Vavilapalli wrote:
> Hi all,
>
> I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>
> As discussed before, this is the next maintenance release to follow up 2.7.1.
>
> The RC is available for validation at: http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>
> The RC tag in git is: release-2.7.2-RC1
>
> The maven artifacts are available via repository.apache.org <http://repository.apache.org/> at https://repository.apache.org/content/repositories/orgapachehadoop-1026/ <https://repository.apache.org/content/repositories/orgapachehadoop-1026/>
>
> The release-notes are inside the tar-balls at location hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I hosted this at http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for quick perusal.
>
> As you may have noted,
> - The RC0 related voting thread got halted due to some critical issues. It took a while again for getting all those blockers out of the way. See the previous voting thread [3] for details.
> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by quite a bit. This release's related discussion threads are linked below: [1] and [2].
>
> Please try the release and vote; the vote will run for the usual 5 days.
>
> Thanks,
> Vinod
>
> [1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <http://markmail.org/message/oozq3gvd4nhzsaes>
> [2]: Planning Apache Hadoop 2.7.2 http://markmail.org/message/iktqss2qdeykgpqk <http://markmail.org/message/iktqss2qdeykgpqk>
> [3]: [VOTE] Release Apache Hadoop 2.7.2 RC0: http://markmail.org/message/5txhvr2qdiqglrwc
>
>
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Kihwal Lee <ki...@yahoo-inc.com.INVALID>.
+1 (binding)- Verified the signature/digest.
- I've built the dist tree with the native support from the source.- Brought up a single node cluster and ran a set of basic tests.
From: Vinod Kumar Vavilapalli <vi...@apache.org>
To: Hadoop Common <co...@hadoop.apache.org>; hdfs-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org
Cc: Vinod Kumar Vavilapalli <vi...@apache.org>
Sent: Wednesday, December 16, 2015 8:49 PM
Subject: [VOTE] Release Apache Hadoop 2.7.2 RC1
Hi all,
I've created a release candidate RC1 for Apache Hadoop 2.7.2.
As discussed before, this is the next maintenance release to follow up 2.7.1.
The RC is available for validation at: http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
The RC tag in git is: release-2.7.2-RC1
The maven artifacts are available via repository.apache.org <http://repository.apache.org/> at https://repository.apache.org/content/repositories/orgapachehadoop-1026/ <https://repository.apache.org/content/repositories/orgapachehadoop-1026/>
The release-notes are inside the tar-balls at location hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I hosted this at http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for quick perusal.
As you may have noted,
- The RC0 related voting thread got halted due to some critical issues. It took a while again for getting all those blockers out of the way. See the previous voting thread [3] for details.
- Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by quite a bit. This release's related discussion threads are linked below: [1] and [2].
Please try the release and vote; the vote will run for the usual 5 days.
Thanks,
Vinod
[1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <http://markmail.org/message/oozq3gvd4nhzsaes>
[2]: Planning Apache Hadoop 2.7.2 http://markmail.org/message/iktqss2qdeykgpqk <http://markmail.org/message/iktqss2qdeykgpqk>
[3]: [VOTE] Release Apache Hadoop 2.7.2 RC0: http://markmail.org/message/5txhvr2qdiqglrwc
Re: [VOTE] Release Apache Hadoop 2.7.2 RC1
Posted by Arpit Agarwal <aa...@hortonworks.com>.
Thanks for putting together this release Vinod.
+1 (binding)
- Verified signatures
- Started pseudo-cluster with binary distribution, verified git commit ID
- Built sources, deployed pseudo-cluster and ran example map reduce jobs, DistributedShell, HDFS commands.
PS: Extra file hadoop-2.7.2-RC1-src.tar.gz.md5?
On 12/16/15, 6:49 PM, "Vinod Kumar Vavilapalli" <vi...@apache.org> wrote:
>Hi all,
>
>I've created a release candidate RC1 for Apache Hadoop 2.7.2.
>
>As discussed before, this is the next maintenance release to follow up 2.7.1.
>
>The RC is available for validation at: http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/ <http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/>
>
>The RC tag in git is: release-2.7.2-RC1
>
>The maven artifacts are available via repository.apache.org <http://repository.apache.org/> at https://repository.apache.org/content/repositories/orgapachehadoop-1026/ <https://repository.apache.org/content/repositories/orgapachehadoop-1026/>
>
>The release-notes are inside the tar-balls at location hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html. I hosted this at http://people.apache.org/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html for quick perusal.
>
>As you may have noted,
> - The RC0 related voting thread got halted due to some critical issues. It took a while again for getting all those blockers out of the way. See the previous voting thread [3] for details.
> - Before RC0, an unusually long 2.6.3 release caused 2.7.2 to slip by quite a bit. This release's related discussion threads are linked below: [1] and [2].
>
>Please try the release and vote; the vote will run for the usual 5 days.
>
>Thanks,
>Vinod
>
>[1]: 2.7.2 release plan: http://markmail.org/message/oozq3gvd4nhzsaes <http://markmail.org/message/oozq3gvd4nhzsaes>
>[2]: Planning Apache Hadoop 2.7.2 http://markmail.org/message/iktqss2qdeykgpqk <http://markmail.org/message/iktqss2qdeykgpqk>
>[3]: [VOTE] Release Apache Hadoop 2.7.2 RC0: http://markmail.org/message/5txhvr2qdiqglrwc
>