Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of todd@cloudera.com designates
 209.85.215.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAGpTDNfSVb5cu6zFn0EV4v1cUPNZJgyq8eUBFfT7t2kZRpvwTw@mail.gmail.com>
References: 
 <CADcMMgFVyKQCNrBiMTV7MRAw7W_UGZcmYkBD70Npey=pg9twgg@mail.gmail.com>
 <CAGpTDNdZfrYVtBTBQyKEjWHH=XJ+X1=+QVQAopX2rrGNzj-F1w@mail.gmail.com>
 <CALte62yURQPcP6Z_Du3NFvarPsSjpX3xUANFF-CoW9QTxe9aRg@mail.gmail.com>
 <CAAha9a1y_230iPYCdTyzkUd5ZkGGmg7OYEPD=Xhm+PsNkQ_PNA@mail.gmail.com>
 <CADcMMgFt7uSvfhtpKjsD18cQ4HK-FQ3T8Qpq1XS+Q9Ck3r7r5g@mail.gmail.com>
 <CALte62yRwZFDauZXMTZBQQdBjuyTJBqRnMtDpq9nRYNZMmTuiw@mail.gmail.com>
 <CALte62wPWLbiNAo9QHQ3Ym1DXbrnQwutC1J-eF8d03X5LB7=Fw@mail.gmail.com>
 <CAGpTDNfSVb5cu6zFn0EV4v1cUPNZJgyq8eUBFfT7t2kZRpvwTw@mail.gmail.com>
From: Todd Lipcon <todd@cloudera.com>
Date: Tue, 3 Jan 2012 19:36:09 -0800
Message-ID: 
 <CADY20s4zN1Yq0UGtnk3Gh_GXp-b1GqQgG9XNgGsHGBJDJ0WCxw@mail.gmail.com>
Subject: Re: ANN: The third hbase 0.92.0 release candidate is available for
 download
To: dev@hbase.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Jan 3, 2012 at 7:16 PM, Jean-Daniel Cryans <jdcryans@apache.org> wr=
ote:

> I would also suggest a third option that seems like a stretch but
> could be workable:
>
> - MAX_FILESIZE is 4x bigger so users are less likely to have a huge
> number of regions (plus all our education), so the TM is less likely
> to cause damage and could be very useful. What I mean is 5119 could be
> committed but not 5120 for 0.92.0
>

That doesn't help the folks who will be upgrading from an existing
cluster and still have too-many regions. We've got some merge hacks
but nothing super-easy to use yet. So I think we have to expect that
some folks will have lots of regions for a little while yet.

Given that people have been testing w/o the TimeoutMonitor, I think we
should leave these confs as they are in the current 92 rc and not futz
too much. If stuff gets stuck in transition we at least have decent
visibility and fix tools compared to what we had in 90.

-Todd

> On Tue, Jan 3, 2012 at 6:47 PM, Ted Yu <yuzhihong@gmail.com> wrote:
>> I cloned HBASE-5120 off of HBASE-5119 and marked it as a blocker.
>> I think it shows that we may need to revisit HBASE-4015.
>>
>> Regards
>>
>> On Tue, Jan 3, 2012 at 5:10 PM, Ted Yu <yuzhihong@gmail.com> wrote:
>>
>>> Shall we also address the scenario where timeout monitor and bulk disab=
ler
>>> race against the same region ?
>>> See
>>> https://issues.apache.org/jira/browse/HBASE-5119?focusedCommentId=3D131=
79176&page=3Dcom.atlassian.jira.plugin.system.issuetabpanels:comment-tabpan=
el#comment-13179176
>>>
>>> Cheers
>>>
>>>
>>> On Tue, Jan 3, 2012 at 5:04 PM, Stack <stack@duboce.net> wrote:
>>>
>>>> On Tue, Jan 3, 2012 at 3:12 PM, Jonathan Hsieh <jon@cloudera.com> wrot=
e:
>>>> > I am similarly concerned about the deadlocks in distributed log
>>>> splitting
>>>> > that Jimmy and Prakash have been working on.
>>>> >
>>>> > If distributed long splitting is off by default, I'm +1. =A0If it is
>>>> going to
>>>> > be default on, then I'd prefer getting those bugs bumped up to
>>>> > blockers fixed and then spinning another rc.
>>>> >
>>>>
>>>> I'll put up a new RC after HBASE-5081 goes in (I'll update our hadoop
>>>> to the released 1.0.0).
>>>>
>>>> St.Ack
>>>>
>>>
>>>


--=20
Todd Lipcon
Software Engineer, Cloudera