[
https://issues.apache.org/jira/browse/HBASE-10591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13910652#comment-13910652
]
Enis Soztutar commented on HBASE-10591:
---------------------------------------
bq. As an example, I have a table with MAX_FILESIZE => '1638400' (Less than
2MB). This region handle VERY small keys/values. Value is 1 byte. Keys are less
than 32 bytes. But I want this table to be spread over all my servers. So I
have to put a small MAX_FILESIZE value.
Let me make it a per table configuration.
bq. Can we also add TTL checks here and close HBASE-10571 as a dup?
Makes sense.
bq. I also think sanity checking needs to be done for table schema
modifications as well as the initial create.
The patch does the checks in modify table as well.
> 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
>
>
> 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)
