Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of kasha@cloudera.com designates
 209.85.219.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1375974851.29034.YahooMailNeo@web126004.mail.ne1.yahoo.com>
References: <3A68E85B-5097-4E41-8169-3307AD53983E@hortonworks.com>
	<B307D71F-F328-418A-8B92-A65C3B2748BD@apache.org>
	<793303BE-F2E8-4039-9B85-618B7D53BEDD@apache.org>
	<2246EC71-C343-4DC0-9476-22F0DA4D5EA0@apache.org>
	<CAJs-t7MZ_i0u332sG15Ra6s8F9QgcSG09ajXmt7_uwsbmKZdXw@mail.gmail.com>
	<3927B870-1AE2-4549-BB78-E496D24B1BA7@apache.org>
	<CACDdcgcdWStbLA+EwoRibiWsofqPhXT3DQfsc4yNb+0Mm3Dm4A@mail.gmail.com>
	<CAPzbcGSq59chNnFqsdySSNtmiLyHxBfpwLW3pUU7izVwYjWBBg@mail.gmail.com>
	<F2D72829-245E-4B25-BEB7-838895A644C9@hortonworks.com>
	<1C2E39C8-938A-489D-AE33-658678B3607F@yahoo-inc.com>
	<7734E8E1-1A02-4791-AE1A-A72D0C9ECC04@hortonworks.com>
	<1375974851.29034.YahooMailNeo@web126004.mail.ne1.yahoo.com>
Date: Tue, 13 Aug 2013 10:37:27 -0700
Message-ID: 
 <CALwhT95iet7aP+VosU-iCdvJsZr+fNqoEVhJFn+qFDKv1NQ18g@mail.gmail.com>
Subject: Re: [VOTE] Release Apache Hadoop 2.1.0-beta
From: Karthik Kambatla <kasha@cloudera.com>
To: "common-dev@hadoop.apache.org" <common-dev@hadoop.apache.org>
Cc: "mapreduce-dev@hadoop.apache.org" <mapreduce-dev@hadoop.apache.org>,
	"<hdfs-dev@hadoop.apache.org>" <hdfs-dev@hadoop.apache.org>,
	"yarn-dev@hadoop.apache.org" <yarn-dev@hadoop.apache.org>
Content-Type: multipart/alternative; boundary=089e0112cf10d827c304e3d7b153

--089e0112cf10d827c304e3d7b153
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Arun,

Would it be possible to include YARN-1056 in the next RC - it is a
straight-forward config change. I marked it as a blocker for 2.1.0.

Thanks
Karthik


On Thu, Aug 8, 2013 at 8:14 AM, Kihwal Lee <kihwal@yahoo-inc.com> wrote:

> Another blocker, HADOOP-9850, has been committed.
>
>
> Kihwal
>
>
> ________________________________
>  From: Arun C Murthy <acm@hortonworks.com>
> To: Daryn Sharp <daryn@yahoo-inc.com>
> Cc: "<hdfs-dev@hadoop.apache.org>" <hdfs-dev@hadoop.apache.org>; "
> mapreduce-dev@hadoop.apache.org" <mapreduce-dev@hadoop.apache.org>; "
> yarn-dev@hadoop.apache.org" <yarn-dev@hadoop.apache.org>; "
> common-dev@hadoop.apache.org" <common-dev@hadoop.apache.org>
> Sent: Thursday, August 1, 2013 1:30 PM
> Subject: Re: [VOTE] Release Apache Hadoop 2.1.0-beta
>
>
> Ok, thanks for heads up Daryn. I'll spin an RC2 once HADOOP-9816 gets in =
-
> I'd appreciate if you could help push the fix in ASAP.
>
> Thanks again!
>
> Arun
>
> On Aug 1, 2013, at 9:38 AM, Daryn Sharp <daryn@yahoo-inc.com> wrote:
>
> > I broke RPC QOP for integrity and privacy options. :(  See blocker
> HADOOP-9816.  I think I understand the problem and it shouldn't be hard t=
o
> fix.
> >
> > The bug went unnoticed because sadly there are no unit tests for the QO=
P
> options, even though it just involves a conf setting.
> >
> > Daryn
> >
> >
> > On Jul 29, 2013, at 5:00 PM, Arun C Murthy wrote:
> >
> >> Ok, I think we are close to rc1 now - the last of blockers should be
> committed later today=85 I'll try and spin RC1 tonight.
> >>
> >> thanks,
> >> Arun
> >>
> >> On Jul 21, 2013, at 12:43 AM, Devaraj Das <ddas@hortonworks.com> wrote=
:
> >>
> >>> I have just raised https://issues.apache.org/jira/browse/HDFS-5016 ..
> This
> >>> bug can easily be reproduced by some HBase tests. I'd like this to be
> >>> considered before we make a beta release. Have spoken about this with
> some
> >>> hdfs folks offline and I am told that it is being worked on.
> >>>
> >>> Thanks
> >>> Devaraj
> >>>
> >>>
> >>> On Wed, Jul 17, 2013 at 4:25 PM, Alejandro Abdelnur <tucu00@gmail.com
> >wrote:
> >>>
> >>>> As I've mentioned in my previous email, if we get YARN-701 in, we
> should
> >>>> also get in the fix for unmanaged AMs in an un-secure setup in
> 2.1.0-beta.
> >>>> Else is a regression of a functionality it is already working.
> >>>>
> >>>> Because of that, to avoid continuing delaying the release, I'm
> suggesting
> >>>> to mention in the release notes the API changes and behavior changes
> that
> >>>> YARN-918 and YARN-701 will bring into the next beta or GA release.
> >>>>
> >>>> thx
> >>>>
> >>>>
> >>>> On Wed, Jul 17, 2013 at 4:14 PM, Vinod Kumar Vavilapalli <
> >>>> vinodkv@hortonworks.com> wrote:
> >>>>
> >>>>>
> >>>>> On Jul 17, 2013, at 1:04 PM, Alejandro Abdelnur wrote:
> >>>>>
> >>>>>> * YARN-701
> >>>>>>
> >>>>>> It should be addressed before a GA release.
> >>>>>>
> >>>>>> Still, as it is this breaks unmanaged AMs and to me
> >>>>>> that would be a blocker for the beta.
> >>>>>>
> >>>>>> YARN-701 and the unmanaged AMs fix should be committed
> >>>>>> in tandem.
> >>>>>>
> >>>>>> * YARN-918
> >>>>>>
> >>>>>> It is a consequence of YARN-701 and depends on it.
> >>>>>
> >>>>>
> >>>>>
> >>>>> YARN-918 is an API change. And YARN-701 is a behaviour change. We
> need
> >>>>> both in 2.1.0.
> >>>>>
> >>>>>
> >>>>>
> >>>>>> * YARN-926
> >>>>>>
> >>>>>> It would be nice to have it addressed before GA release.
> >>>>>
> >>>>>
> >>>>> Either ways. I'd get it in sooner than later specifically when we a=
re
> >>>>> trying to replace the old API with the new one.
> >>>>>
> >>>>> Thanks,
> >>>>> +Vino
> >>>>>
> >>>>>
> >>>>
> >>
> >> --
> >> Arun C. Murthy
> >> Hortonworks Inc.
> >> http://hortonworks.com/
> >>
> >>
> >
>
> --
> Arun C. Murthy
> Hortonworks Inc.
> http://hortonworks.com/
>

--089e0112cf10d827c304e3d7b153--