Re: abandoning 22 - was: Content request for 0.20.205 Sustaining Release

2011-09-07 Thread Konstantin Shvachko
Eric, It would take the same amount of resources to fix 0.22 as to merge append and security branches aka 0.20.205. Although I understand that Hortonworks needs to support its customer(s) and is eager to bridge the gap in functionality with its competitor(s), I think continuing with 0.20

0.20.205 Sustaining Release branch plan and content plan

2011-09-07 Thread Matt Foley
Hi all, Over the past week a number of people have provided input for patches they would like to see in 205, with reasons and risk evaluations; please see the threads Content request for 0.20.205 Sustaining Release and Add Append-HBase support in upcoming 20.205. Thanks to all who took the effort

Re: abandoning 22 - was: Content request for 0.20.205 Sustaining Release

2011-09-07 Thread Brian Bockelman
On Sep 6, 2011, at 2:08 PM, milind.bhandar...@emc.com wrote: I am very interested in hearing what the community thinks about this issue. I believe what happens here has long-term consequences. AKAIK, the bylaws do not mention anything about abandoning release. If past is any indication,

best way to replace disks on a small cluster

2011-09-07 Thread Marco Cadetg
Hi there, Current situation: 3 slaves with each two 320GB disks in RAID 1. All the disks show high read errors and io throughput has gone below 5Mb/s without running any hadoop job. (It looks like it will fall apart soon...) What is the best way to replace the bad disks? I may be able to add

Re: best way to replace disks on a small cluster

2011-09-07 Thread Marco Cadetg
Hi Mike, Thanks for your quick reply. On Wed, Sep 7, 2011 at 3:21 PM, Segel, Mike mse...@navteq.com wrote: Hi, Ok, so you have a small cluster w raid drives... First, raid isn't really a good idea. You want to replace the old raid drives w new 2TB drives in JBOD. (Which is better.)

Re: abandoning 22 - was: Content request for 0.20.205 Sustaining Release

2011-09-07 Thread Eric Baldeschwieler
Hi Konstantine, I've never advocated 21 or 22 since I've never been able to volunteer help to work on them. I think it's great if you want to run another branch, do testing etc. But given that it's neither complete, stable nor the latest majority supported project I think the expectation should

Re: abandoning 22 - was: Content request for 0.20.205 Sustaining Release

2011-09-07 Thread Arun C Murthy
Konstantin, On Sep 7, 2011, at 2:04 AM, Konstantin Shvachko wrote: I think continuing with 0.20 a-three-years-old-technology is not the best place to invest resources. In the past you advocated for 0.21 and 0.22, both now abandoned by your team(s) in favor of enhancing 0.20. It will be sad

Re: best way to replace disks on a small cluster

2011-09-07 Thread Allen Wittenauer
On Sep 7, 2011, at 6:19 AM, Marco Cadetg wrote: Current situation: 3 slaves with each two 320GB disks in RAID 1. All the disks show high read errors and io throughput has gone below 5Mb/s without running any hadoop job. (It looks like it will fall apart soon...) One the special

Re: abandoning 22 - was: Content request for 0.20.205 Sustaining Release

2011-09-07 Thread Allen Wittenauer
On Sep 7, 2011, at 9:15 AM, Arun C Murthy wrote: Using real data helps - from Apache Jira, here are the statistics for work on trunk/hadoop-0.23 in Q3 of 2011 (i.e. last 2 months alone): Hadoop Common - 224 resolved* jiras Hadoop HDFS - 153 resolved* jiras Hadoop MapReduce - 161* resolved

Re: abandoning 22 - was: Content request for 0.20.205 Sustaining Release

2011-09-07 Thread Konstantin Boudnik
On Wed, Sep 07, 2011 at 02:04AM, Konstantin Shvachko wrote: Eric, It would take the same amount of resources to fix 0.22 as to merge append and security branches aka 0.20.205. Although I understand that Hortonworks needs to support its customer(s) and is eager to bridge the gap in