Re: [Update] Apache Hadoop 2.8.2 Release Status
A quick update: the last patch (YARN-7230) for docker container support in 2.8 just get committed yesterday. Now there is no left blocker/critical issues for 2.8.2 and I checked all landed commits are matching with JIRA's fix version. With kicking off a new RC build, I will publish RC bits for vote once the build process get finished. In the mean time, please hold on any commits to branch-2.8.2 unless it really belongs to a blocker and please ping me ahead. Thanks all for your patience! Thanks, Junping From: Junping Du <j...@hortonworks.com> Sent: Friday, September 22, 2017 5:57 PM To: common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org Cc: Shane Kumpf; Miklos Szegedi; Varun Vasudev Subject: [Update] Apache Hadoop 2.8.2 Release Status Hi folks, I would like to give you a quick update on 2.8.2 release status: - First release candidate (RC0) is published over the last weekend, but several docker container blockers (bugs, documents, etc.) are reported so we decided to cancel the RC0 for vote. - New coming release blockers (for docker container support) are YARN-7034 (just committed), YARN-6623, YARN-6930 and YARN-7230. Shane, Miklos and Varun are actively working on this. Appreciate the effort here! - I will kick off new release candidate (RC1) once these blockers are resolved. To all committers, branch-2.8.2 is still open for blocker/critical issues landing, but for major/minor/trivial issues, please commit to branch-2.8 and marked the fixed version as 2.8.3. Thanks all for heads up. Have a good weekend! Thanks, Junping From: Junping Du <j...@hortonworks.com> Sent: Tuesday, September 5, 2017 2:57 PM To: larry mccay; Steve Loughran Cc: common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org Subject: Re: Apache Hadoop 2.8.2 Release Plan I assume the quiet over the holiday means we agreed to move forward without taking HADOOP-14439 into 2.8.2. There is a new release building (docker based) issue could be related to HADOOP-14474 where we removed oracle java 7 installer due to recent download address/contract change by Oracle. The build refuse to work - report as JAVA_HOME issue, but hard coded my local java home in create-release or Dockerfile doesn't help so we may need to add java 7 installation back (no matter Oracle JDK 7 or openJDK 7). Filed HADOOP-14842 with more details to track as blocker for 2.8.2. Thanks, Junping From: Junping Du <j...@hortonworks.com> Sent: Friday, September 1, 2017 12:37 PM To: larry mccay; Steve Loughran Cc: common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org Subject: Re: Apache Hadoop 2.8.2 Release Plan This issue (HADOOP-14439) is out of my radar given it is marked as Minor priority. If my understanding is correct, here is a trade-off between security and backward compatibility. IMO, priority of security is generally higher than backward compatibility especially 2.8.0 is still non-production release. I think we should skip this for 2.8.2 in case it doesn't break compatibility from 2.7.x. Thoughts? Thanks, Junping From: larry mccay <lmc...@apache.org> Sent: Friday, September 1, 2017 10:55 AM To: Steve Loughran Cc: common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org Subject: Re: Apache Hadoop 2.8.2 Release Plan If we do "fix" this in 2.8.2 we should seriously consider not doing so in 3.0. This is a very poor practice. I can see an argument for backward compatibility in 2.8.x line though. On Fri, Sep 1, 2017 at 1:41 PM, Steve Loughran <ste...@hortonworks.com> wrote: > One thing we need to consider is > > HADOOP-14439: regression: secret stripping from S3x URIs breaks some > downstream code > > Hadoop 2.8 has a best-effort attempt to strip out secrets from the > toString() value of an s3a or s3n path where someone has embedded them in > the URI; this has caused problems in some uses, specifically: when people > use secrets this way (bad) and assume that you can round trip paths to > string and back > > Should we fix this? If so, Hadoop 2.8.2 is the time to do it > > > > On 1 Sep 2017, at 11:14, Junping Du <j...@hortonworks.com> wrote: > > > > HADOOP-14814 get committed and HADOOP-9747 get push out to 2.8.3, so we > are clean on blocker/critical issues now. > > I finish practice of going through JACC report and no more incompatible > public API changes get found between 2.8.2 and 2.7.4. Also I check commit > history and fixed 10+ commits which are missing from branch-2.8.2 for s
[Update] Apache Hadoop 2.8.2 Release Status
Hi folks, I would like to give you a quick update on 2.8.2 release status: - First release candidate (RC0) is published over the last weekend, but several docker container blockers (bugs, documents, etc.) are reported so we decided to cancel the RC0 for vote. - New coming release blockers (for docker container support) are YARN-7034 (just committed), YARN-6623, YARN-6930 and YARN-7230. Shane, Miklos and Varun are actively working on this. Appreciate the effort here! - I will kick off new release candidate (RC1) once these blockers are resolved. To all committers, branch-2.8.2 is still open for blocker/critical issues landing, but for major/minor/trivial issues, please commit to branch-2.8 and marked the fixed version as 2.8.3. Thanks all for heads up. Have a good weekend! Thanks, Junping From: Junping DuSent: Tuesday, September 5, 2017 2:57 PM To: larry mccay; Steve Loughran Cc: common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org Subject: Re: Apache Hadoop 2.8.2 Release Plan I assume the quiet over the holiday means we agreed to move forward without taking HADOOP-14439 into 2.8.2. There is a new release building (docker based) issue could be related to HADOOP-14474 where we removed oracle java 7 installer due to recent download address/contract change by Oracle. The build refuse to work - report as JAVA_HOME issue, but hard coded my local java home in create-release or Dockerfile doesn't help so we may need to add java 7 installation back (no matter Oracle JDK 7 or openJDK 7). Filed HADOOP-14842 with more details to track as blocker for 2.8.2. Thanks, Junping From: Junping Du Sent: Friday, September 1, 2017 12:37 PM To: larry mccay; Steve Loughran Cc: common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org Subject: Re: Apache Hadoop 2.8.2 Release Plan This issue (HADOOP-14439) is out of my radar given it is marked as Minor priority. If my understanding is correct, here is a trade-off between security and backward compatibility. IMO, priority of security is generally higher than backward compatibility especially 2.8.0 is still non-production release. I think we should skip this for 2.8.2 in case it doesn't break compatibility from 2.7.x. Thoughts? Thanks, Junping From: larry mccay Sent: Friday, September 1, 2017 10:55 AM To: Steve Loughran Cc: common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org Subject: Re: Apache Hadoop 2.8.2 Release Plan If we do "fix" this in 2.8.2 we should seriously consider not doing so in 3.0. This is a very poor practice. I can see an argument for backward compatibility in 2.8.x line though. On Fri, Sep 1, 2017 at 1:41 PM, Steve Loughran wrote: > One thing we need to consider is > > HADOOP-14439: regression: secret stripping from S3x URIs breaks some > downstream code > > Hadoop 2.8 has a best-effort attempt to strip out secrets from the > toString() value of an s3a or s3n path where someone has embedded them in > the URI; this has caused problems in some uses, specifically: when people > use secrets this way (bad) and assume that you can round trip paths to > string and back > > Should we fix this? If so, Hadoop 2.8.2 is the time to do it > > > > On 1 Sep 2017, at 11:14, Junping Du wrote: > > > > HADOOP-14814 get committed and HADOOP-9747 get push out to 2.8.3, so we > are clean on blocker/critical issues now. > > I finish practice of going through JACC report and no more incompatible > public API changes get found between 2.8.2 and 2.7.4. Also I check commit > history and fixed 10+ commits which are missing from branch-2.8.2 for some > reason. So, the current branch-2.8.2 should be good to go for RC stage, and > I will kick off our first RC tomorrow. > > In the meanwhile, please don't land any commits to branch-2.8.2 since > now. If some issues really belong to blocker, please ping me on the JIRA > before doing any commits. branch-2.8 is still open for landing. Thanks for > your cooperation! > > > > > > Thanks, > > > > Junping > > > > > > From: Junping Du > > Sent: Wednesday, August 30, 2017 12:35 AM > > To: Brahma Reddy Battula; common-dev@hadoop.apache.org; > hdfs-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org; > yarn-...@hadoop.apache.org > > Subject: Re: Apache Hadoop 2.8.2 Release Plan > > > > Thanks Brahma for comment on this thread. To be clear, I always update > branch version just before RC kicking off. > > > > For 2.8.2 release, I don't have plan to involve big top or other > third-party test tools. As always, we will rely on