[
https://issues.apache.org/jira/browse/HBASE-17288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15738728#comment-15738728
]
Guanghao Zhang commented on HBASE-17288:
----------------------------------------
bq. no longer updates totalBytesRead
Use currentInResultRowSizeInByte instead of totalBytesRead. So it doesn't need
totalBytesRead.
bq. it moves the throw of RowTooBigException up into checkKvSize() ahead of
size and batch progress accounting in the scanner context
I thought it is ok to throw RowToOBigException first because we don't catch
this exception and after this exception we don't use this scanner context
anymore.
> 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.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)
