hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11544) [Ergonomics] hbase.client.scanner.caching is dogged and will try to return batch even if it means OOME
Date Thu, 05 Feb 2015 05:46:35 GMT

    [ https://issues.apache.org/jira/browse/HBASE-11544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14306686#comment-14306686
] 

Lars Hofhansl commented on HBASE-11544:
---------------------------------------

I nutshell I was saying:
# For small rows we're good if we set existing hbase.client.scanner.max.result.size config
correctly. We can do that right now as default.
# For large rows we need to allow for batching if the client wants to limit its buffer size
# For large cells we need streaming, if the client wants to limit its buffer size

[~jonathan.lawlor]'s approach will get us much further on the way. Just saying that the most
important part is streaming.

I'll file an issue for #1 - just set that config in hbase-defaults.xml. Then we can concentrate
on the other issues here.


> [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)

Mime
View raw message