hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Loughran <ste...@hortonworks.com>
Subject Re: Next releases
Date Fri, 08 Nov 2013 09:30:34 GMT
On 8 November 2013 02:42, Arun C Murthy <acm@hortonworks.com> wrote:

> Gang,
>  Thinking through the next couple of releases here, appreciate f/b.
>  # hadoop-2.2.1
>  I was looking through commit logs and there is a *lot* of content here
> (81 commits as on 11/7). Some are features/improvements and some are fixes
> - it's really hard to distinguish what is important and what isn't.
>  I propose we start with a blank slate (i.e. blow away branch-2.2 and
> start fresh from a copy of branch-2.2.0)  and then be very careful and
> meticulous about including only *blocker* fixes in branch-2.2. So, most of
> the content here comes via the next minor release (i.e. hadoop-2.3)
>  In future, we continue to be *very* parsimonious about what gets into a
> patch release (major.minor.patch) - in general, these should be only
> *blocker* fixes or key operational issues.


>  # hadoop-2.3
>  I'd like to propose the following features for YARN/MR to make it into
> hadoop-2.3 and punt the rest to hadoop-2.4 and beyond:
>  * Application History Server - This is happening in  a branch and is
> close; with it we can provide a reasonable experience for new frameworks
> being built on top of YARN.
>  * Bug-fixes in RM Restart
>  * Minimal support for long-running applications (e.g. security) via
> YARN-896

+1 -the complete set isn't going to make it, but I'm sure we can identify
the key ones

>  * RM Fail-over via ZKFC
>  * Anything else?
>  HDFS???

   - If I had the time, I'd like to do some work on the HADOOP-9361
   filesystem spec & tests -this is mostly some specification, the basis of a
   better test framework for newer FS tests, and some more tests, with a
   couple of minor changes to some of the FS code, mainly in terms of
   tightening some of the exceptions thrown (IOE -> EOF)


   - I'd like the hadoop-openstack  JAR in; it's already in branch-2 so
   it's a matter of ensuring testing during the release against as many
   providers as possible.
   - There are a fair few JIRAs about updating versions of dependencies
   -the S3 JetS3t update went in this week, but there are more, as well as
   cruft in the POMs which shows up downstream. I think we could update the
   low-risk dependencies (test-time, log4j, &c), while avoiding those we know
   will be trouble (jetty). This may seem minor but it does make a big diff to
   the downstream projects.

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.

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