hadoop-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <Milind.Bhandar...@emc.com>
Subject Re: Hadoop 0.22 update
Date Wed, 03 Aug 2011 22:41:48 GMT
Nigel,

I have created https://issues.apache.org/jira/browse/MAPREDUCE-2767, and
uploaded the patch.

Please review. Thanks.

- milind

---
Milind Bhandarkar
Greenplum Labs, EMC
((Disclaimer: Opinions expressed in this email are those of the author,
and do
not necessarily represent the views of any organization, past or present,
the author might be affiliated with.)





On 8/2/11 11:44 PM, "Nigel Daley" <ndaley@mac.com> wrote:

>+1.
>
>n.
>
>On Aug 2, 2011, at 1:35 PM, Matt Foley wrote:
>
>> +1 (non-binding).  Sounds good to me.
>> --Matt
>> 
>> 
>> On Tue, Aug 2, 2011 at 1:27 PM, Devaraj Das <ddas@hortonworks.com>
>>wrote:
>> 
>>> Yes...  I meant the LTC.
>>> 
>>> On Aug 2, 2011, at 1:23 PM, <Milind.Bhandarkar@emc.com> wrote:
>>> 
>>>> Eli,
>>>> 
>>>> I hope we don't have to remove the TaskTracker *grin*.
>>>> 
>>>> Devaraj/Allen,
>>>> 
>>>> You mean LinuxTaskController only, right ?
>>>> 
>>>> The default is DefaultTaskController, which is not relevant to these
>>>> discussions.
>>>> 
>>>> +1. This is the easiest way to get 0.22.0 out.
>>>> 
>>>> - Milind
>>>> ---
>>>> Milind Bhandarkar
>>>> Greenplum Labs, EMC
>>>> 
>>>> 
>>>> 
>>>> 
>>>> On 8/2/11 1:07 PM, "Devaraj Das" <ddas@hortonworks.com> wrote:
>>>> 
>>>>> +1 to removing the TaskController code for the 0.22 release.
>>>>> 
>>>>> In the MR-279 branch, the security issues identified in
>>>>>MAPREDUCE-2178
>>>>> have been taken care of (to my knowledge).
>>>>> 
>>>>> On Aug 2, 2011, at 12:58 PM, Eli Collins wrote:
>>>>> 
>>>>>> On Tue, Aug 2, 2011 at 12:25 PM, Eli Collins <eli@cloudera.com>
>>>>>>wrote:
>>>>>>> On Tue, Aug 2, 2011 at 12:19 PM,  <Milind.Bhandarkar@emc.com>
>>>>>>>wrote:
>>>>>>>> Having talked to various folks in the community about their
>>>>>>>> willingness to
>>>>>>>> stabilize and use 0.22 and make it production-quality, here
is
>>>>>>>>what I
>>>>>>>> propose:
>>>>>>>> 
>>>>>>>> 1. Cut a release 0.22.0 without mapreduce-2178 patch, with
>>>>>>>> hadoop.security.authentication set to simple (I.e. No
>>> authentication).
>>>>>>>> Make sure that MR-2178 is highlighted as known-issue in the
>>>>>>>>top-level
>>>>>>>> dir
>>>>>>>> (create a KNOWN-ISSUES.txt ?), and carry out a vote.
>>>>>>>> 
>>>>>>>> 2. Later, when MR-2178 patch is committed, cut a release
for
>>>>>>>>0.22.1.
>>>>>>>> (I
>>>>>>>> have heard of folks working on it, but no date commitments
yet.)
>>>>>>>> 
>>>>>>>> The reason a 0.22.0 release should happen, IMHO, even without
>>>>>>>> MR-2178, is
>>>>>>>> that the other components of Hadoop stack (e.g. Pig, hbase,
hive
>>>>>>>>etc)
>>>>>>>> will
>>>>>>>> have a release to test against, and fix any issues for
>>>>>>>> incompatibility.
>>>>>>>> Also, for folks who do not use kerberos authentication (>90%
of
>>>>>>>>the
>>>>>>>> hadoop
>>>>>>>> users, to my knowledge), it will be a release closest to
trunk,
>>>>>>>>with
>>>>>>>> HDFS
>>>>>>>> appends. Plus, any issues found in the HDFS part of the release
>>>>>>>>would
>>>>>>>> be
>>>>>>>> directly applicable to the trunk and other future releases.
(Not
>>>>>>>>so
>>>>>>>> about
>>>>>>>> map-reduce, which will undergo major surgery in trunk because
of
>>>>>>>> MR-279.)
>>>>>>>> 
>>>>>>>> Thoughts ?
>>>>>>>> 
>>>>>>> 
>>>>>>> Sounds reasonable to me.  #1 is what we did for the 0.21 release.
>>>>>> 
>>>>>> Actually, I didn't read close enough. For 0.21 we actually removed
>>>>>>the
>>>>>> task tracker, think it makes sense to do that here as well.
>>>>>> 
>>>>>> Thanks,
>>>>>> Eli
>>>>> 
>>>>> 
>>>> 
>>> 
>>> 
>
>


Mime
View raw message