Return-Path: Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: (qmail 16972 invoked from network); 28 Jan 2010 02:15:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 28 Jan 2010 02:15:17 -0000 Received: (qmail 55387 invoked by uid 500); 28 Jan 2010 02:15:17 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 55285 invoked by uid 500); 28 Jan 2010 02:15:16 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-dev@hadoop.apache.org Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 55275 invoked by uid 99); 28 Jan 2010 02:15:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Jan 2010 02:15:16 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.191.125.177] (HELO n12a.bullet.mail.mud.yahoo.com) (209.191.125.177) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 28 Jan 2010 02:15:06 +0000 Received: from [68.142.200.221] by n12.bullet.mail.mud.yahoo.com with NNFMP; 28 Jan 2010 02:14:45 -0000 Received: from [76.13.13.26] by t9.bullet.mud.yahoo.com with NNFMP; 28 Jan 2010 02:14:44 -0000 Received: from [76.13.10.178] by t3.bullet.mail.ac4.yahoo.com with NNFMP; 28 Jan 2010 02:14:44 -0000 Received: from [127.0.0.1] by omp119.mail.ac4.yahoo.com with NNFMP; 28 Jan 2010 02:14:43 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 267881.8116.bm@omp119.mail.ac4.yahoo.com Received: (qmail 68508 invoked by uid 60001); 28 Jan 2010 02:14:43 -0000 Message-ID: <104245.66328.qm@web65507.mail.ac4.yahoo.com> X-YMail-OSG: nTMRjB4VM1lQx5pEqOFCJZYqUWEiN54D7RzoaJbhLpNTelCiGHIEe1.GoBBfPkEagf3Npo_mbWrR2zXoe.kaY_SuH7.zK0D09_iMNOkTsb8oKUqXnaNYeYc9ghFQylyNsWVovknLH1.HIy7Tcu93ivUOC.61SJ2KIG3URFBhMdLxP_hYUoQBC3kWTE_oscWC6QYjek19_1hA7_yYueYRdoK1CPLxoyuLTt_4SJQ6C9lVNmv7Nvizj4zFzBQk5RD5rfYKUlP3fVOWTld6iDEz70bz66AvDZ0NU_tuEhJIQPWpJUd0neVJVUsTJ4OHBIZAIws0AyqsnFyVxQansM.L2cdf6.sTClg2ldKznvMOfSSxT7Qr91UiqhM9pQ-- Received: from [66.135.63.56] by web65507.mail.ac4.yahoo.com via HTTP; Wed, 27 Jan 2010 18:14:43 PST X-RocketYMMF: apurtell X-Mailer: YahooMailRC/272.7 YahooMailWebService/0.8.100.260964 References: <20100127025302.GB46526@wlanvpn-mc2e-246-200.corp.yahoo.com> <4B5FAEB3.2060808@gmail.com> <45f85f71001261909s62184ccek5b8f0fd268f9ab68@mail.gmail.com> <7c962aed1001271545g48ca363bt396e38d39697978a@mail.gmail.com> <45f85f71001271714p1e0ec0d5s73d516e8b623aeb0@mail.gmail.com> Date: Wed, 27 Jan 2010 18:14:43 -0800 (PST) From: Andrew Purtell Subject: Re: Rolling a Hadoop 0.20.2 To: hbase-dev@hadoop.apache.org Cc: hdfs-dev@hadoop.apache.org In-Reply-To: <45f85f71001271714p1e0ec0d5s73d516e8b623aeb0@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii So the list of HDFS issues for next 0.20.x or 0.21 most relevant to HBase stability I have is: 127 200 (well, hflush) 630 793 Sound about right? Anything important I'm missing? - Andy ----- Original Message ---- > From: Todd Lipcon > To: common-dev@hadoop.apache.org > Sent: Thu, January 28, 2010 9:14:01 AM > Subject: Re: Rolling a Hadoop 0.20.2 > > I don't think 101 is a real blocker - I haven't been able to reliably > produce it. HDFS-793 fixes most of the issues I've seen in practice, and we > now have a new patch in branch-20 which should fix that. > > 127 would be nice - there's a patch on that JIRA waiting for review as > below. > > -Todd > > On Wed, Jan 27, 2010 at 3:45 PM, Stack wrote: > > > If the new release included (fixedup) hdfs-127 and hdfs-101, the hbase > > crew would be big fans of an hadoop 0.20.2. > > St.Ack > > > > On Tue, Jan 26, 2010 at 7:09 PM, Todd Lipcon wrote: > > > HDFS-127 was originally committed, then rolled back from 0.20 as it > > caused > > > test timeouts due to infinite loop. I put a new patch up there but it has > > > not been reviewed, and thus not committed. > > > > > > Owen: is there a particular rush for 0.20.2 or can we hold out for these > > > patches? > > > > > > -Todd > > > > > > 2010/1/26 Kay Kay > > > > > >> Is HDFS-127 going to be part of it ? (seems to have been committed as > > per > > >> the jira). > > >> > > >> > > >> > > >> > > >> On 1/26/10 6:53 PM, Konstantin Boudnik wrote: > > >> > > >>> +1 > > >>> On Tue, Jan 26, 2010 at 09:56AM, Owen O'Malley wrote: > > >>> > > >>> > > >>>> I'm planning on rolling a Hadoop 0.20.2 today. Are there any blockers > > >>>> that can't wait? > > >>>> > > >>>> -- Owen > > >>>> > > >>>> > > >>> > > >> > > > > >