[
https://issues.apache.org/jira/browse/HBASE-10591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231141#comment-14231141
]
Hudson commented on HBASE-10591:
--------------------------------
SUCCESS: Integrated in HBase-0.98-on-Hadoop-1.1 #676 (See
[https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/676/])
Amend HBASE-12573 Backport HBASE-10591 Sanity check table configuration in
createTable (apurtell: rev 0d7ddab0dac718c2c14a3d15680410c001f19a41)
*
hbase-thrift/src/test/java/org/apache/hadoop/hbase/thrift/TestThriftServer.java
> 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, hbase-10070
>
> Attachments: hbase-10591_v1.patch, hbase-10591_v2.patch,
> hbase-10591_v3.patch, hbase-10591_v4.patch, hbase-10591_v5.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.3.4#6332)
