[
https://issues.apache.org/jira/browse/HBASE-10591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13911070#comment-13911070
]
Enis Soztutar commented on HBASE-10591:
---------------------------------------
bq. nit: Should a sanity check of HTD be in HTD? Could be static public?
You mean the client can run it herself? It loads up the compression and region
split policy classes which might not be available in clients classpath.
bq. The default split policy now starts with 2*flushSize, should we hence allow
2m as region split size?
In case client writes 100GB, it would mean 50K regions still. It might be
acceptable though.
> 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
(v6.1.5#6160)
