[
https://issues.apache.org/jira/browse/HBASE-17288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15750911#comment-15750911
]
Anoop Sam John commented on HBASE-17288:
----------------------------------------
Ya the new constants for config name, def value etc should be in StoreScanner
only. I see , if MOB uses another path, then that is ok.
bq.kv size:1253360
U want to change the size into more human readable format? (Like 1.2 MB).. Hope
all refs to KV will be changed to be Cell.
BTW we have we have a config to specify the max KV size(Ya this is an old
config and so KV name there) allowed.'hbase.client.keyvalue.maxsize'. In code
its default is -1 means no size limit. But we have this entry in
hbase-default.xml means we have this size restriction in place by def. And this
is 10 MB. Just saying.
> Add warn log for huge Cell 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)
