[
https://issues.apache.org/jira/browse/HBASE-11544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14306663#comment-14306663
]
stack commented on HBASE-11544:
-------------------------------
bq. ... and that we probably need to allow the option to handle partial result
at the client anyway, is it worth engaging in this...
[~lhofhansl] Are you suggesting that [~jonathan.lawlor]'s list under "...the
approach that I am thinking of taking for solution #1 is" above is not needed?
His list seems pretty critical. Could add your making a 2mb
rpcChunkSize/max.result.size default as a sub-issue and add another to do the
work letting out partial rows if clients configure the scanner to say they are
up for handling it.
> [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
> Priority: Critical
> Labels: beginner
>
> 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.3.4#6332)
