-1 for rc1
I downloaded and ran the test target 3 times.
First run failed because my umask is defaulted to 0002, which is a known
problem HADOOP-5050 committed to 0.21 but not 0.20.
Set umask to 0022 and re-ran test twice. Both resulted in failure. Here is
the list of failed tests:
[junit] Test org.apache.hadoop.mapred.TestJobTrackerRestart FAILED
(timeout)
[junit] Test
org.apache.hadoop.mapred.TestJobTrackerRestartWithLostTracker FAILED
[junit] Test org.apache.hadoop.mapred.TestJobTrackerSafeMode FAILED
[junit] Test org.apache.hadoop.mapred.TestMiniMRMapRedDebugScript FAILED
[junit] Test org.apache.hadoop.mapred.TestRecoveryManager FAILED
[junit] Test org.apache.hadoop.mapred.TestTTMemoryReporting FAILED
[junit] Test org.apache.hadoop.mapred.TestTaskTrackerLocalization FAILED
[junit] Test org.apache.hadoop.hdfsproxy.TestHdfsProxy FAILED
I am in favor of releasing hadoop-0.20.203.
And we run a version of this release on a large cluster at eBay. I know it
works.
I understand the controversy behind it. I regret it hasn't been developed in
a true community way.
I think it nevertheless adds value to Apache Hadoop.
Lets just make sure it passes the tests.
Thanks,
--Konstantin
On Tue, May 3, 2011 at 1:39 AM, Konstantin Shvachko <shv.had...@gmail.com>wrote:
> I think its a good idea to release hadoop-0.20.203. It moves Apache Hadoop
> a step forward.
>
> Looks like the technical difficulties are resolved now with latest Arun's
> commits.
> Being a superset of hadoop-0.20.2 it can be considered based on one of the
> official Apache releases.
> I don't think there was a lack of discussions on the lists about the issues
> included in the release candidate. Todd did a thorough review of the entire
> security branch. Many developers participated in discussions.
> Agreeing with Stack I wish HBase was considered a primary target for Hadoop
> support. But it is not realistic to have it in hadoop-0.20.203.
> I have some experience running a version of this release candidate on a
> large cluster. It works. I would add a couple of patches, which make it run
> on Windows for me like HADOOP-7110, HADOOP-7126. But those are not blockers.
>
> Thanks,
> --Konstantin
>
>
> On Mon, May 2, 2011 at 5:12 PM, Ian Holsman <had...@holsman.net> wrote:
>
>>
>> On May 3, 2011, at 9:58 AM, Arun C Murthy wrote:
>>
>> >>
>> >> Owen, Suresh and I have committed everything on this list except
>> >> HADOOP-6386 and HADOOP-6428. Not sure which of the two are relevant/
>> >> necessary, I'll check with Cos. Other than that hadoop-0.20.203 now a
>> >> superset of hadoop-0.20.2.
>> >>
>> >
>> > Missed adding HADOOP-5759 to that list, I'll check with Amareshwari
>> before committing.
>> >
>> > Arun
>>
>> Thanks for doing this so fast Arun.
>>
>>
>
