hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-10591) Sanity check table configuration in createTable
Date Mon, 24 Feb 2014 23:50:31 GMT

     [ https://issues.apache.org/jira/browse/HBASE-10591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Enis Soztutar updated HBASE-10591:

    Attachment: hbase-10591_v3.patch

v3 patch: 
 - Adds checks for 1K <= block cache <= 16M
 - Adds checks for TTL > 0
 - Adds "hbase.table.sanity.check" conf option (global or per table) in case the user knows
what she is doing. The .limit conf options are removed. 

Let me write up a release note. 

> 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