hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alejandro Abdelnur <t...@cloudera.com>
Subject Re: Heads up: branch-2.1-beta
Date Fri, 14 Jun 2013 21:02:00 GMT

This sounds great. Following is the list of JIRAs I'd like to get in. Note
that the are ready or almost ready, my estimate is that they can be taken
care of in a couple of day.


* YARN-752: In AMRMClient, automatically add corresponding rack requests
for requested nodes

impact: behavior change

status: patch avail, reviewed by Bikas. As Bikas did some changes it needs
another committer to look at it.

* YARN-521: Augment AM - RM client module to be able to request containers
only at specific locations

impact: AMRM client API change

status: patch avail, needs to be reviewed, needs YARN-752

* YARN-791: Ensure that RM RPC APIs that return nodes are consistent with
/nodes REST API

impact: Yarn client API & proto change

status: patch avail, review in progress

* YARN-649: Make container logs available over HTTP in plain text

impact: Addition to NM HTTP REST API. Needed for MAPREDUCE-4362 (which does
not change API)

status: patch avail, review in progress

* MAPREDUCE-5171: Expose blacklisted nodes from the MR AM REST API

impact: Addition to MRAM HTTP API

status: patch avail, +1ed, needs to be committed

* MAPREDUCE-5130: Add missing job config options to mapred-default.xml

impact: behavior change

status: patch avail, needs to be reviewed

* MAPREDUCE-5311: Remove slot millis computation logic and deprecate
counter constants

impact: behavior change

status: patch avail, needs to be reviewed

* YARN-787: Remove resource min from Yarn client API

impact: Yarn client API change

status: patch needs rebase, depends on MAPREDUCE-5311

On Fri, Jun 14, 2013 at 1:17 PM, Arun C Murthy <acm@hortonworks.com> wrote:

> As Ramya noted, things are looking good on branch-2.1-beta ATM.
> Henceforth, can I please ask committers to hold off non-blocker fixes for
> the final set of tests?
> thanks,
> Arun
> On Jun 4, 2013, at 8:32 AM, Arun C Murthy wrote:
> > Folks,
> >
> > The vast majority of of the planned features and API work is complete,
> thanks to everyone who contributed!
> >
> > I've created a branch-2.1-beta branch from which I anticipate I can make
> the first of our beta releases very shortly.
> >
> > For now the remaining work is to wrap up loose ends i.e. last minute api
> work (e.g. YARN-759 showed up last night for consideration), bug-fixes
> etc.; then run this through a battery of unit/system/integration tests and
> do a final review before we ship. There is more work remaining on
> documentation (e.g. HADOOP-9517) and I plan to personally focus on it this
> week - obviously help reviewing docs is very welcome.
> >
> > Committers, from now, please please exercise your judgement on where you
> commit. Typically, features should go into branch-2 with 2.3.0 as the
> version on jira (fix-version 2.3.0 is ready). The expectation is that 2.2.0
> will be limited to content in branch-2.1-beta and we stick to stabilizing
> it henceforth (I've deliberately not created 2.2.0 fix-version on jira yet).
> >
> > thanks,
> > Arun
> --
> Arun C. Murthy
> Hortonworks Inc.
> http://hortonworks.com/


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