hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10591) Sanity check table configuration in createTable
Date Tue, 25 Feb 2014 00:14:22 GMT

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

Lars Hofhansl commented on HBASE-10591:

The default split policy now starts with 2*flushSize, should we hence allow 2m as region split

> 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, hbase-10591_v3.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