[
https://issues.apache.org/jira/browse/HBASE-17288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15750574#comment-15750574
]
Anoop Sam John commented on HBASE-17288:
----------------------------------------
HConstants being Public, not to add these kind of constants here.
bq.HUGE_KV_SIZE_IN_BYTE_WARN_NAME = "hbase.huge.keyvalue.size.in.byte";
Why KV ref where as we call it Cells these days
We have MOB feature now where each of the Cell might be >1M in size. This is
make too many warn logs with def value of 'ase.huge.keyvalue.size.in.byte'.
(And also on row size)
> Add warn log for huge keyvalue and huge row
> -------------------------------------------
>
> Key: HBASE-17288
> URL: https://issues.apache.org/jira/browse/HBASE-17288
> Project: HBase
> Issue Type: Improvement
> Components: scan
> Reporter: Guanghao Zhang
> Assignee: Guanghao Zhang
> Priority: Minor
> Attachments: HBASE-17288-v1.patch, HBASE-17288.patch
>
>
> Some log examples from our production cluster.
> {code}
> 2016-12-10,17:08:11,478 WARN
> org.apache.hadoop.hbase.regionserver.StoreScanner: adding a HUGE KV into
> result list, kv size:1253360,
> kv:105671140000001-1-c/R:r1/1481360887152/Put/vlen=1253245/ts=923099, from
> table XXXXX
> 2016-12-10,17:08:16,724 WARN
> org.apache.hadoop.hbase.regionserver.StoreScanner: adding a HUGE KV into
> result list, kv size:1048680,
> kv:0220459/I:i_0/1481360889551/Put/vlen=1048576/ts=13642, from table XXXXXX
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
