Thank for restarting this, Arun! The following are the efforts that I am involved in directly or indirectly and shepherding from YARN's point of view: rolling-upgrades (YARN-666), work-preserving RM restart (YARN-556), minimal long-running services support (YARN-896), including service-registry (YARN-913), timeline-service stability/security (some sub-tasks of YARN-1935), node labels (YARN-296) and some enhancements/bug fixes in cpu-scheduling/cgroups. We also have reservations sub-system (YARN-1051) and YARN shared cache (YARN-1492) that I would like to get in and helping reviews with. Almost all these efforts are on the edge of completion - some of them are just pending reviews. Clearly some of them will be more stable than others, some of them make it eventually, some may not.
+1 for branching it within a week so that we can stabilize it and let other features go into branch-2, I am putting out all the stops to get the above YARN efforts to be in reasonable shape for 2.6. Regarding remaining items that I haven't paid much attention, NM restart effort - mostly done by Jason Lowe - YARN-1336 is all in. YARN-291, YARN-18, YARN-1964 are not going to cut from what I see. I edited the road-map to reflect this latest reality. +Vinod On Tue, Sep 23, 2014 at 3:03 PM, Arun Murthy <a...@hortonworks.com> wrote: > Looks like most of the content is in and hadoop-2.6 is shaping up nicely. > > I'll create branch-2.6 by end of the week and we can go from there to > stabilize it - hopefully in the next few weeks. > > Thoughts? > > thanks, > Arun > > On Tue, Aug 12, 2014 at 1:34 PM, Arun C Murthy <a...@hortonworks.com> > wrote: > > > Folks, > > > > With hadoop-2.5 nearly done, it's time to start thinking ahead to > > hadoop-2.6. > > > > Currently, here is the Roadmap per the wiki: > > > > • HADOOP > > • Credential provider HADOOP-10607 > > • HDFS > > • Heterogeneous storage (Phase 2) - Support APIs for > using > > storage tiers by the applications HDFS-5682 > > • Memory as storage tier HDFS-5851 > > • YARN > > • Dynamic Resource Configuration YARN-291 > > • NodeManager Restart YARN-1336 > > • ResourceManager HA Phase 2 YARN-556 > > • Support for admin-specified labels in YARN YARN-796 > > • Support for automatic, shared cache for YARN > application > > artifacts YARN-1492 > > • Support NodeGroup layer topology on YARN YARN-18 > > • Support for Docker containers in YARN YARN-1964 > > • YARN service registry YARN-913 > > > > My suspicion is, as is normal, some will make the cut and some won't. > > Please do add/subtract from the list as appropriate. Ideally, it would be > > good to ship hadoop-2.6 in a 6-8 weeks (say, October) to keep up a > cadence. > > > > More importantly, as we discussed previously, we'd like hadoop-2.6 to be > > the *last* Apache Hadoop 2.x release which support JDK6. I'll start a > > discussion with other communities (HBase, Pig, Hive, Oozie etc.) and see > > how they feel about this. > > > > thanks, > > Arun > > > > > > > -- > > -- > Arun C. Murthy > Hortonworks Inc. > http://hortonworks.com/ > > -- > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity to > which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You. > -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
