Grokbase Groups HBase dev April 2010
FAQ
HBASE-2481 "Client is not getting UnknownScannerExceptions; they are
being eaten" sinks this release candidate. Will fix and put up a new
candidate this evening.
St.Ack
On Tue, Apr 20, 2010 at 11:54 PM, Stack wrote:
I've posted an hbase 0.20.4 release candidate 2 here:

http://people.apache.org/~stack/hbase-0.20.4-candidate-2/

Should we release this candidate as hbase 0.20.4?

In includes some critical fixes and some performance enhancements (See
CHANGES.txt or the release notes in the docs [1] for the list of over
100 issues addressed by this candidate).

Please take it for a test spin if you have a chance.  Vote closes
Tuesday, the 27th of April.

Yours,
The HBase Team

1. http://people.apache.org/~stack/hbase-0.20.4-candidate-2/hbase-0.20.4/docs/releasenotes.html

On Sat, Apr 17, 2010 at 10:14 PM, Stack wrote:
I've posted an hbase 0.20.4 release candidate here:

http://people.apache.org/~stack/hbase-0.20.4-candidate-1/

Should we release this candidate as hbase 0.20.4?

In includes some critical fixes and some performance enhancements (See
CHANGES.txt or http://su.pr/4QEGFv for the list of over 100 issues
addressed by this candidate).

Please take it for a test spin if you have a chance.  Vote closes
Sunday, the 24th of April.

Yours,
The HBase Team

Search Discussions

  • Cosmin Lehene at Apr 23, 2010 at 5:52 am
    I've noticed there are more places where exceptions tend to be eaten, or transformed in a generic IOException. Working around this tends to obscure logic sometimes. More, most of the classes seem to both catch and throw IOException as a "standard". Perhaps working a bit towards having a richer set of IOException subclasses would make sense. Anyone thought of that?

    Cosmin
    On Apr 23, 2010, at 3:50 AM, Stack wrote:

    HBASE-2481 "Client is not getting UnknownScannerExceptions; they are
    being eaten" sinks this release candidate. Will fix and put up a new
    candidate this evening.
    St.Ack
    On Tue, Apr 20, 2010 at 11:54 PM, Stack wrote:
    I've posted an hbase 0.20.4 release candidate 2 here:

    http://people.apache.org/~stack/hbase-0.20.4-candidate-2/

    Should we release this candidate as hbase 0.20.4?

    In includes some critical fixes and some performance enhancements (See
    CHANGES.txt or the release notes in the docs [1] for the list of over
    100 issues addressed by this candidate).

    Please take it for a test spin if you have a chance. Vote closes
    Tuesday, the 27th of April.

    Yours,
    The HBase Team

    1. http://people.apache.org/~stack/hbase-0.20.4-candidate-2/hbase-0.20.4/docs/releasenotes.html

    On Sat, Apr 17, 2010 at 10:14 PM, Stack wrote:
    I've posted an hbase 0.20.4 release candidate here:

    http://people.apache.org/~stack/hbase-0.20.4-candidate-1/

    Should we release this candidate as hbase 0.20.4?

    In includes some critical fixes and some performance enhancements (See
    CHANGES.txt or http://su.pr/4QEGFv for the list of over 100 issues
    addressed by this candidate).

    Please take it for a test spin if you have a chance. Vote closes
    Sunday, the 24th of April.

    Yours,
    The HBase Team
  • Ryan Rawson at Apr 23, 2010 at 5:55 am
    The problem is checked exceptions - translating throwables into
    "generic" IOExceptions. There are some specific exception classes in
    hbase, but the problem is with all those unknown and random
    exceptions. Eg: NPEs.

    As for this issue, some kind of regression looks like.

    -ryan
    On Thu, Apr 22, 2010 at 10:51 PM, Cosmin Lehene wrote:
    I've noticed there are more places where exceptions tend to be eaten, or transformed in a generic IOException. Working around this tends to obscure logic sometimes.  More, most of the classes seem to both catch and throw IOException as a "standard". Perhaps working a bit towards having a richer set of IOException subclasses would make sense. Anyone thought of that?

    Cosmin
    On Apr 23, 2010, at 3:50 AM, Stack wrote:

    HBASE-2481 "Client is not getting UnknownScannerExceptions; they are
    being eaten" sinks this release candidate.  Will fix and put up a new
    candidate this evening.
    St.Ack
    On Tue, Apr 20, 2010 at 11:54 PM, Stack wrote:
    I've posted an hbase 0.20.4 release candidate 2 here:

    http://people.apache.org/~stack/hbase-0.20.4-candidate-2/

    Should we release this candidate as hbase 0.20.4?

    In includes some critical fixes and some performance enhancements (See
    CHANGES.txt or the release notes in the docs [1] for the list of over
    100 issues addressed by this candidate).

    Please take it for a test spin if you have a chance.  Vote closes
    Tuesday, the 27th of April.

    Yours,
    The HBase Team

    1. http://people.apache.org/~stack/hbase-0.20.4-candidate-2/hbase-0.20.4/docs/releasenotes.html

    On Sat, Apr 17, 2010 at 10:14 PM, Stack wrote:
    I've posted an hbase 0.20.4 release candidate here:

    http://people.apache.org/~stack/hbase-0.20.4-candidate-1/

    Should we release this candidate as hbase 0.20.4?

    In includes some critical fixes and some performance enhancements (See
    CHANGES.txt or http://su.pr/4QEGFv for the list of over 100 issues
    addressed by this candidate).

    Please take it for a test spin if you have a chance.  Vote closes
    Sunday, the 24th of April.

    Yours,
    The HBase Team
  • Tsuna at Apr 23, 2010 at 8:22 am

    On Thu, Apr 22, 2010 at 10:51 PM, Cosmin Lehene wrote:
    I've noticed there are more places where exceptions tend to be eaten, or transformed in a generic IOException. Working around this tends to obscure logic sometimes.  More, most of the classes seem to both catch and throw IOException as a "standard". Perhaps working a bit towards having a richer set of IOException subclasses would make sense. Anyone thought of that?
    I totally agree. HBase's use of exceptions (both internally and in
    the client API) is Just Wrong. Virtually everything throws an
    IOException and hardly any method documents what it may really
    represent, so writing proper recovery code is almost impossible (you
    can always give up or retry, but you don't really know what kind of
    problem you're dealing with). And of course IOException is a checked
    exception, which means you are *forced* to handle it, even though you
    almost never know what to do with HBase's IOEs.

    --
    Benoit "tsuna" Sigoure
    Software Engineer @ www.StumbleUpon.com
  • Stack at Apr 24, 2010 at 7:48 pm

    On Fri, Apr 23, 2010 at 1:22 AM, tsuna wrote:
    On Thu, Apr 22, 2010 at 10:51 PM, Cosmin Lehene wrote:
    I've noticed there are more places where exceptions tend to be eaten, or transformed in a generic IOException. Working around this tends to obscure logic sometimes.  More, most of the classes seem to both catch and throw IOException as a "standard". Perhaps working a bit towards having a richer set of IOException subclasses would make sense. Anyone thought of that?
    +1 Maybe a bit of design first that lists the set of possible
    exceptions (ScannerTimeoutException, WrongRegionException) and then
    issues to bring us in-line w/ a specification? You want to open an
    issue Cosmin with say an example of where we are wrong for
    illustration? Throw Benoît's comment below in there too?

    My sense is that a combination of lazyness -- "Well, IOE is going to
    be *handled* anyways" -- and a lack of agreement about what is the
    right way to do it has gotten us to here.

    Thanks,
    St.Ack

    I totally agree.  HBase's use of exceptions (both internally and in
    the client API) is Just Wrong.  Virtually everything throws an
    IOException and hardly any method documents what it may really
    represent, so writing proper recovery code is almost impossible (you
    can always give up or retry, but you don't really know what kind of
    problem you're dealing with).  And of course IOException is a checked
    exception, which means you are *forced* to handle it, even though you
    almost never know what to do with HBase's IOEs.

    --
    Benoit "tsuna" Sigoure
    Software Engineer @ www.StumbleUpon.com

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupdev @
categorieshbase, hadoop
postedApr 23, '10 at 12:50a
activeApr 24, '10 at 7:48p
posts5
users4
websitehbase.apache.org

People

Translate

site design / logo © 2022 Grokbase