Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
Reviewed
-
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.
Attachments
Attachments
Issue Links
- is depended upon by
-
HBASE-10791 Add integration test to demonstrate performance improvement
- Closed
- supercedes
-
HBASE-10571 TTL of zero should be rejected
- Closed