[
https://issues.apache.org/jira/browse/HBASE-12976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14370373#comment-14370373
]
Hudson commented on HBASE-12976:
--------------------------------
FAILURE: Integrated in HBase-TRUNK #6281 (See
[https://builds.apache.org/job/HBase-TRUNK/6281/])
Revert "HBASE-12976 Set default value for
hbase.client.scanner.max.result.size." (larsh: rev
64589abe9936337fcbccdbe82e538d05020c8ee4)
* hbase-common/src/main/java/org/apache/hadoop/hbase/HConstants.java
* hbase-common/src/main/resources/hbase-default.xml
Reapply "HBASE-12976 Set default value for
hbase.client.scanner.max.result.size." in 1.1 and 2.0 only (larsh: rev
0d766544166fc9630bb00ae14a4a34a69d93f127)
* hbase-common/src/main/resources/hbase-default.xml
* hbase-common/src/main/java/org/apache/hadoop/hbase/HConstants.java
> Set default value for 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
> Assignee: Lars Hofhansl
> Fix For: 1.0.0, 2.0.0, 1.1.0, 0.98.11
>
> Attachments: 12976-v2.txt, 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)
