[HBASE-10591] Sanity check table configuration in createTable

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.99.0, hbase-10070
• Hadoop Flags: Reviewed

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.

• Assignee: Enis Soztutar
• Reporter: Enis Soztutar
• Created: 22/Feb/14 02:33
• Updated: 21/Feb/15 23:31
• Resolved: 26/Feb/14 22:24

Description

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.

Issue Links

• is depended upon by: HBASE-10791 Add integration test to demonstrate performance improvement
• supercedes: HBASE-10571 TTL of zero should be rejected