Folks,
I thought I'd drop a note and let folks know that I've scheduled a Hadoop
YARN/MapReduce meetup during Hadoop Summit, June 2012.
The agenda is:
# YARN - State of the art
# YARN futures
- Premption
- Resource Isolation
- Multi-resource scheduling
# Implementing new YARN
a) Revert HDFS-3157 and commit HADOOP-8285 and HADOOP-8366 on
branch-2.0.0-alpha, so these are the only changes since rc0. Roll a
new rc1 from here.
I have merged HDFS-3157 revert.
Do you mind taking a look at HADOOP-8285 and HADOOP-8366?
Thanks,
Uma
Thanks Nic!
On May 14, 2012, at 11:07 AM, Tsz Wo Sze wrote:
Let me merge HADOOP-8285 and HADOOP-8366. Thanks.
Tsz-Wo
- Original Message -
From: Uma Maheswara Rao G mahesw...@huawei.com
To: general@hadoop.apache.org general@hadoop.apache.org
Cc:
Sent: Monday, May 14, 2012
Great! Thanks a lot Nicholas!
From: Tsz Wo Sze [szets...@yahoo.com]
Sent: Monday, May 14, 2012 11:37 PM
To: general@hadoop.apache.org
Subject: Re: [VOTE] Release hadoop-2.0.0-alpha
Let me merge HADOOP-8285 and HADOOP-8366. Thanks.
Tsz-Wo
- Original
As soon as jira is back up and I can post an updated patch I'll merge
HDFS-3418 (also incompatible).
On Mon, May 14, 2012 at 12:16 PM, Tsz Wo Sze szets...@yahoo.com wrote:
I just have merged HADOOP-8285 and HADOOP-8366. I also have merged HDFS-3211
since it is an incompatible protocol change
Do we want to get MAPREDUCE-4067 in as well ? It affects folks who may be
writing their own AMs. Shouldn't affect MR clients though. I believe 2.0
alpha doesn't freeze the Yarn protocols for the 2.0 branch, so probably not
critical.
Thanks
- Sid
On Mon, May 14, 2012 at 1:32 PM, Eli Collins
Hey Arun,
One more thing on the rc tarball: the source artifact doesn't appear
to be an exact svn export, based on a diff. For example, it includes
the README, NOTICE, and LICENSE files, as well as a few other things
which appear to be build artifacts (eg
