Description
After discussing with Michael, the issue was that if you have a region size of for example 256M and you add a 1G value into a column then that region cannot split and a cluster can become lopsided. It also means that you have a really large block and the memstore would need to handle the 1G data. I proposed to add a configurable upper boundary check that is throwing an exception on the client side if the user tries to add a value larger than that limit. Ideally it would be set to the maximum region size or less.
Attachments
Attachments
Issue Links
- relates to
-
HBASE-2007 handle overly large column family in one row
-
- Closed
-
-
HBASE-2017 Set configurable max value size check to 10MB
-
- Closed
-