You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Esteban Gutierrez (JIRA)" <ji...@apache.org> on 2017/11/20 21:32:00 UTC
[jira] [Created] (HBASE-19309) Lower HConstants#MAX_ROW_LENGTH as
guardrail in order to avoid HBASE-18987
Esteban Gutierrez created HBASE-19309:
-----------------------------------------
Summary: Lower HConstants#MAX_ROW_LENGTH as guardrail in order to avoid HBASE-18987
Key: HBASE-19309
URL: https://issues.apache.org/jira/browse/HBASE-19309
Project: HBase
Issue Type: Bug
Components: HFile, regionserver
Reporter: Esteban Gutierrez
As discussed in HBASE-18987. A problem of having a row about the maximum size of a row (Short.MAX_VALUE) is when a split happens, there is a possibility that the midkey could be that row and the Put created to add the new entry in META will exceed the maximum row size since the new row key will include the table name and that will cause the split to abort. Since is not possible to raise that row key size in HFileV3, a reasonable solution is to reduce the maximum size of row key in order to avoid exceeding Short.MAX_VALUE.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)