hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vinod Kumar Vavilapalli <vino...@apache.org>
Subject Re: [VOTE] Release Apache Hadoop 2.1.0-beta
Date Mon, 19 Aug 2013 21:49:46 GMT

Thanks for the clarification Daryn. That is what I was asking before when I said "From my
limited understanding, this doesn't seem like a API or a compatibility issue. Can we not fix
it in subsequent bug-fix releases? "

Now, I was wavering as to whether we can omit this or not. There are other such things like
YARN-1082 (RM restart doesn't work in security), YARN-49 (dist-shell in secure mode) etc.
that is essentially a loss of some functionality in some cases (secure mode).

Flipping back the question, aren't we okay release now with all the API changes that are already
in and then immediately follow up with a bunch of bug-fix releases or wait till 'everything'
gets fixed.

Posing the question like that, I am willing to move ahead without waiting for these fixes,
but that's just me.

What do others think?

Thanks,
+Vinod

On Aug 19, 2013, at 8:25 AM, Daryn Sharp wrote:

> I've been OOO (got a call to fix this bug), but just to clarify:
> 
> We're ok with HA _not working at all_ with security enabled in 2.1.0-beta?  That's the
ramification of omitting HADOOP-9880.
> 
> Daryn
> 
> On Aug 16, 2013, at 9:20 PM, Arun C Murthy wrote:
> 
>> Yep, there are quite a number of such fixes in 2.1.1 ATM, I think it will serve us
better to get 2.1.0 out and then quickly turn around to make 2.1.1.
>> 
>> My current plan is to start work on 2.1.1 right after this release gets complete…
hopefully next week.
>> 
>> thanks,
>> Arun
>> 
>> On Aug 16, 2013, at 4:36 PM, Vinod Kumar Vavilapalli <vinodkv@hortonworks.com>
wrote:
>> 
>>> 
>>> There are other such isolated and well understood bug-fixes that we pushed to
2.1.1 in the interesting of making progress with 2.1.0 and the corresponding API changes.
>>> 
>>> 2.1.1 should happen soon enough after this.
>>> 
>>> Thanks,
>>> +Vinod
>>> 
>>> On Aug 16, 2013, at 4:22 PM, Roman Shaposhnik wrote:
>>> 
>>>> What are the downsides of getting this fix into the 2.1? It appears
>>>> that the fix is pretty isolated and well understood.
>>>> 
>>>> Thoughts?
>>>> 
>>>> Thanks,
>>>> Roman.
>>>> 
>>>> On Fri, Aug 16, 2013 at 3:04 PM, Kihwal Lee <kihwal@yahoo-inc.com>
wrote:
>>>>> I've changed the target version of HADOOP-9880 to 2.1.1.  Please change
it back, if you feel that it needs to be in 2.1.0-beta.
>>>>> 
>>>>> 
>>>>> Kihwal
>>>>> 
>>>>> 
>>>>> ________________________________
>>>>> From: Kihwal Lee <kihwal@yahoo-inc.com>
>>>>> To: Arun Murthy <acm@hortonworks.com>; "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>
>>>>> Sent: Friday, August 16, 2013 4:55 PM
>>>>> Subject: Re: [VOTE] Release Apache Hadoop 2.1.0-beta
>>>>> 
>>>>> 
>>>>> It's your call, Arun.  I.e. as long you believe rc2 meets the expectations
and objectives of 2.1.0-beta.
>>>>> 
>>>>> Kihwal
>>>>> 
>>>>> 
>>>>> ________________________________
>>>>> From: Arun Murthy <acm@hortonworks.com>
>>>>> To: "common-dev@hadoop.apache.org" <common-dev@hadoop.apache.org>
>>>>> Cc: Kihwal Lee <kihwal@yahoo-inc.com>; "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>
>>>>> Sent: Friday, August 16, 2013 3:44 PM
>>>>> Subject: Re: [VOTE] Release Apache Hadoop 2.1.0-beta
>>>>> 
>>>>> 
>>>>> That makes sense too.
>>>>> 
>>>>> 
>>>>> On Aug 16, 2013, at 10:39 AM, Vinod Kumar Vavilapalli
>>>>> <vinodkv@hortonworks.com> wrote:
>>>>> 
>>>>>> 
>>>>>> We need to make a call on what blockers will be. From my limited
understanding, this doesn't seem like a API or a compatibility issue. Can we not fix it in
subsequent bug-fix releases?
>>>>>> 
>>>>>> I do see a lot of follow up releases to 2.1.0. Getting this release
out will help downstream projects start testing with all the API stuff that has already gone
in 2.1.0.
>>>>>> 
>>>>>> Thanks,
>>>>>> +Vinod
>>>>>> 
>>>>>> On Aug 16, 2013, at 10:13 AM, Kihwal Lee wrote:
>>>>>> 
>>>>>>> We have found HADOOP-9880, which prevents Namenode HA from running
with security.
>>>>>>> 
>>>>>>> Kihwal
>>>>>>> 
>>>>>>> 
>>>>>>> ________________________________
>>>>>>> From: Arun C Murthy <acm@hortonworks.com>
>>>>>>> To: "common-dev@hadoop.apache.org" <common-dev@hadoop.apache.org>;
"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>
>>>>>>> Sent: Thursday, August 15, 2013 4:15 PM
>>>>>>> Subject: [VOTE] Release Apache Hadoop 2.1.0-beta
>>>>>>> 
>>>>>>> 
>>>>>>> Folks,
>>>>>>> 
>>>>>>> I've created a release candidate (rc2) for hadoop-2.1.0-beta
that I would like to get released - this fixes the bugs we saw since the last go-around (rc1).
>>>>>>> 
>>>>>>> The RC is available at: http://people.apache.org/~acmurthy/hadoop-2.1.0-beta-rc2/
>>>>>>> The RC tag in svn is here: http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.1.0-beta-rc2
>>>>>>> 
>>>>>>> The maven artifacts are available via repository.apache.org.
>>>>>>> 
>>>>>>> Please try the release and vote; the vote will run for the usual
7 days.
>>>>>>> 
>>>>>>> thanks,
>>>>>>> Arun
>>>>>>> 
>>>>>>> --
>>>>>>> Arun C. Murthy
>>>>>>> Hortonworks Inc.
>>>>>>> http://hortonworks.com/
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> --
>>>>>>> CONFIDENTIALITY NOTICE
>>>>>>> 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.
>>>>>> 
>>>>>> 
>>>>>> --
>>>>>> CONFIDENTIALITY NOTICE
>>>>>> 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.
>>>>> 
>>>>> --
>>>>> CONFIDENTIALITY NOTICE
>>>>> 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.
>>> 
>> 
>> --
>> Arun C. Murthy
>> Hortonworks Inc.
>> http://hortonworks.com/
>> 
>> 
>> 
>> -- 
>> CONFIDENTIALITY NOTICE
>> 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.
> 


-- 
CONFIDENTIALITY NOTICE
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.

Mime
View raw message