[
https://issues.apache.org/jira/browse/HBASE-11544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14067434#comment-14067434
]
Lars Hofhansl commented on HBASE-11544:
---------------------------------------
Scan#setMaxResultSize is 1/2 of my #1. When the results do not fit into that
size the client will deliver partial rows to the caller, which the caller then
has to deal with. Since it can randomly (from the viewpoint of the caller)
happen all callers then have to prepared to get multiple results for the same
row for different columns, or simply never see a cell if it is too big to fit
into this size.
> [Ergonomics] hbase.client.scanner.caching is dogged and will try to return
> batch even if it means OOME
> ------------------------------------------------------------------------------------------------------
>
> Key: HBASE-11544
> URL: https://issues.apache.org/jira/browse/HBASE-11544
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Labels: noob
>
> Running some tests, I set hbase.client.scanner.caching=1000. Dataset has
> large cells. I kept OOME'ing.
> Serverside, we should measure how much we've accumulated and return to the
> client whatever we've gathered once we pass out a certain size threshold
> rather than keep accumulating till we OOME.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
