[
https://issues.apache.org/jira/browse/HBASE-17288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15764057#comment-15764057
]
Guanghao Zhang commented on HBASE-17288:
----------------------------------------
bq. You init these new vars when parallel seek enabled. I believe simple
mistake it is and not intended by you.
Sorry for this mistake. I will upload a new patch later.
bq. Any way 1st cell which causes the break in the row size check, will make
into the log.
Nice, but the row is still needed? We need this to find the huge row.
bq. Better we can do the row size check and the end after considering all cells
so that we can get exactly the size of the row? Or is that not possible as per
loop here?
This is not the real row size. When the scan set batch, then it is only the
batch cell's size. Now our scan support heartbeat and ScannerConnext has size
limit and time limit. Maybe it doesn't need huge row warn... I will check the
latest code in master branch.
Thanks for your reviewing. :)
> 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-v2.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)
