hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12976) Default hbase.client.scanner.max.result.size
Date Thu, 05 Feb 2015 18:17:34 GMT

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

stack commented on HBASE-12976:
-------------------------------

Sure on adding it to hbase-default.xml so can be documented.

> Default hbase.client.scanner.max.result.size
> --------------------------------------------
>
>                 Key: HBASE-12976
>                 URL: https://issues.apache.org/jira/browse/HBASE-12976
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Lars Hofhansl
>             Fix For: 2.0.0, 1.0.1, 0.94.27, 0.98.11
>
>         Attachments: 12976.txt
>
>
> Setting scanner caching is somewhat of a black art. It's hard to estimate ahead of time
how large the result set will be.
> I propose we hbase.client.scanner.max.result.size to 2mb. That is good compromise between
performance and buffer usage on typical networks (avoiding OOMs when the caching was chosen
too high).
> To an HTable client this is completely transparent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message