hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stack <st...@duboce.net>
Subject Re: [DISCUSSION] Default configurations in hbase-2.0.0 hbase-default.xml
Date Wed, 20 Dec 2017 01:38:06 GMT
On Tue, Dec 19, 2017 at 4:22 PM, Stack <stack@duboce.net> wrote:

> Thanks for jumping in JMS. Ok on the by-table.
>
> SNAPPY license seems fine. We'd enable it as default when you create a
> table? Let me play w/ it.
>
>
Oh. I forgot what happens if the native lib is not available, how cluster
goes down.

Caused by: java.lang.RuntimeException: native snappy library not available:
this version of libhadoop was built without snappy support.

I think we should skip out on enabling this (but recommend folks run this
way...)

Thanks JMS,
S



> Anything else from your experience that we should change JMS?
>
> Thanks sir,
> S
>
>
> On Tue, Dec 19, 2017 at 1:47 PM, Jean-Marc Spaggiari <
> jean-marc@spaggiari.org> wrote:
>
>> Can we get all tables by default Snappy compressed? I think because of the
>> license we can not, right? Just asking, in case there is an option for
>> that... Also +1 on balancing by table...
>>
>> 2017-12-18 17:34 GMT-05:00 Stack <stack@duboce.net>:
>>
>> > (I thought I'd already posted a DISCUSSION on defaults for 2.0.0 but
>> can't
>> > find it...)
>> >
>> > Dear All:
>> >
>> > I'm trying to get some eyeballs/thoughts on changes you'd like seen in
>> > hbase defaults for hbase-2.0.0. We have a an ISSUE and some good
>> discussion
>> > already up at HBASE-19148.
>> >
>> > A good case is being made for enabling balancing by table as default.
>> >
>> > Guanghao Zhang has already put in place more sensible retry/timeout
>> > numbers.
>> >
>> > Anything else we should change? Shout here or up on the issue.
>> >
>> > Thanks,
>> > S
>> >
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message