[
https://issues.apache.org/jira/browse/HBASE-10591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar updated HBASE-10591:
----------------------------------
Release Note: Introduces sanity checks for table configuration in create
and modify table against some default values. Especially we enforce region
split size >= 2MB, memstore flush size >= 1MB, and 1024 <= block size <= 16MB.
If you want to bypass the sanity checks, you can set
"hbase.table.sanity.checks" to false, at global configuration, or at table
descriptors configuration. (was: Introduces sanity checks for table
configuration in create and modify table against some default values.
Especially we enforce region split size >= 16MB, memstore flush size >= 1MB,
and 1024 <= block size <= 16MB. If you want to bypass the sanity checks, you
can set "hbase.table.sanity.checks" to false, at global configuration, or at
table descriptors configuration. )
> 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, hbase-10591_v4.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
(v6.1.5#6160)
