hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carlo Curino <ccur...@microsoft.com>
Subject RE: [DISCUSS] Looking to a 2.8.0 release
Date Mon, 07 Dec 2015 22:17:06 GMT
Hi Vinod,

Beside the HA work Subru mentioned (YARN-2573), we are working on a few more improvements
of the reservation system 
under umbrella YARN-2572.

A few patches are already checked in in 2.8 (e.g., YARN-3454, YARN-4248, YARN-4358), these
are a combination of tooling
and performance improvements (all transparent to users that are not using reservations, and
backward compatible improvements
for folks that are using reservations).  We are trying to get as much of this finished by
the 2.8 release cut, however we should 
not hold up the release for this too much (e.g., YARN-4359 is being coded as we speak and
might not make it). 

Please let me know whether this sounds good, and whether it is fine to keep committing these
patches (YARN-4340, YARN-4420, 
YARN-4360, YARN-4359) as they become ready to 2.8 until is finalized. 

Cheers,
Carlo


-----Original Message-----
From: Subramaniam V K [mailto:subru.vk@gmail.com] 
Sent: Wednesday, November 25, 2015 11:47 AM
To: yarn-dev@hadoop.apache.org
Cc: Hadoop Common <common-dev@hadoop.apache.org>; hdfs-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org
Subject: Re: [DISCUSS] Looking to a 2.8.0 release

Hi Vinod,

Thanks for driving this. Can you add YARN-2573 which includes the work done to integrate ReservationSystem
with the RM failover mechanism to your list.
This can be reviewed and committed (branch-2) also about a month back.

Cheers,
Subru

On Wed, Nov 25, 2015 at 11:37 AM, Vinod Kumar Vavilapalli < vinodkv@apache.org> wrote:

> I think we’ve converged at a high level w.r.t 2.8. And as I just sent 
> out an email, I updated the Roadmap wiki reflecting the same:
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fwiki.
> apache.org%2fhadoop%2fRoadmap&data=01%7c01%7cCCURINO%40exchange.micros
> oft.com%7c3bc4b2cea9ee42aa858f08d2f5d132e1%7c72f988bf86f141af91ab2d7cd
> 011db47%7c1&sdata=duyyuWIqj1o%2fgZLenhz%2bx3g4QqLMIpSZiAxC55nHa7Q%3d
>
> I plan to create a 2.8 branch EOD today.
>
> The goal for all of us should be to restrict improvements & fixes to 
> only
> (a) the feature-set documented under 2.8 in the RoadMap wiki and (b) 
> other minor features that are already in 2.8.
>
> Thanks
> +Vinod
>
>
> > On Nov 11, 2015, at 12:13 PM, Vinod Kumar Vavilapalli <
> vinodkv@hortonworks.com> wrote:
> >
> >  - Cut a branch about two weeks from now
> >  - Do an RC mid next month (leaving ~4weeks since branch-cut)
> >  - As with 2.7.x series, the first release will still be called as 
> > early
> / alpha release in the interest of
> >     — gaining downstream adoption
> >     — wider testing,
> >     — yet reserving our right to fix any inadvertent 
> > incompatibilities
> introduced.
>
>
Mime
View raw message