hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Wangda Tan <wheele...@gmail.com>
Subject [DISCUSS] Looking to Apache Hadoop 3.1 release
Date Wed, 06 Sep 2017 18:13:59 GMT
Hi all,

As we discussed on [1], there were proposals from Steve / Vinod etc to have
a faster cadence of releases and to start thinking of a Hadoop 3.1 release
earlier than March 2018 as is currently proposed.

I think this is a good idea. I'd like to start the process sooner, and
establish timeline etc so that we can be ready when 3.0.0 GA is out. With
this we can also establish faster cadence for future Hadoop 3.x releases.

To this end, I propose to target Hadoop 3.1.0 for a release by mid Jan
2018. (About 4.5 months from now and 2.5 months after 3.0-GA, instead of
6.5 months from now).

I'd also want to take this opportunity to come up with a more elaborate
release plan to avoid some of the confusion we had with 3.0 beta. General
proposal for the timeline (per this other proposal [2])
 - Feature freeze date - all features should be merged by Dec 15, 2017.
 - Code freeze date - blockers/critical only, no more improvements and non
blocker/critical bug-fixes: Jan 1, 2018.
 - Release date: Jan 15, 2018

Following is a list of features on my radar which could be candidates for a
3.1 release:
- YARN-5734, Dynamic scheduler queue configuration. (Owner: Jonathan Hung)
- YARN-5881, Add absolute resource configuration to CapacityScheduler.
(Owner: Sunil)
- YARN-5673, Container-executor rewrite for better security, extensibility
and portability. (Owner Varun Vasudev)
- YARN-6223, GPU isolation. (Owner: Wangda)

And from email [3] mentioned by Andrew, there’re several other HDFS
features want to be released with 3.1 as well, assuming they fit the
- Storage Policy Satisfier
- HDFS tiered storage

Please let me know if I missed any features targeted to 3.1 per this

And I want to volunteer myself as release manager of 3.1.0 release. Please
let me know if you have any suggestions/concerns.

Wangda Tan

[1] http://markmail.org/message/hwar5f5ap654ck5o?q=
[2] http://markmail.org/message/hwar5f5ap654ck5o?q=Branch+
[3] http://markmail.org/message/h35obzqrh3ag6dgn?q=Branch+merge

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message