hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Marc Spaggiari (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10591) Sanity check table configuration in createTable
Date Mon, 24 Feb 2014 13:35:20 GMT

    [ https://issues.apache.org/jira/browse/HBASE-10591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13910295#comment-13910295

Jean-Marc Spaggiari commented on HBASE-10591:

Can we add a "force" parameter in case anyone really want to have a value outside of those
values, and knows what he is doing?

As an example, I have a table with MAX_FILESIZE => '1638400' (Less than 2MB). This region
handle VERY small keys/values. Value is 1 byte. Keys are less than 32 bytes. But I want this
table to be spread over all my servers. So I have to put a small MAX_FILESIZE value.

With current patch, I will not be able to do that anymore, which is bad for me. So I would
really prefer to have a "force" option. Yes I can use hbase.hregion.max.filesize.limit and
set it to 1MB, but since I think this is still a good idea, I want to have this check for
my other tables :)

My 2ยข.

> Sanity check table configuration in createTable
> -----------------------------------------------
>                 Key: HBASE-10591
>                 URL: https://issues.apache.org/jira/browse/HBASE-10591
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>             Fix For: 0.99.0
>         Attachments: hbase-10591_v1.patch, hbase-10591_v2.patch
> We had a cluster completely become unoperational, because a couple of table was erroneously
created with MAX_FILESIZE set to 4K, which resulted in 180K regions in a short interval, and
bringing the master down due to  HBASE-4246.
> We can do some sanity checking in master.createTable() and reject the requests. We already
check the compression there, so it seems a good place. Alter table should also check for this
as well.

This message was sent by Atlassian JIRA

View raw message