hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12976) Set default value for hbase.client.scanner.max.result.size
Date Thu, 19 Mar 2015 23:02:39 GMT

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

Hudson commented on HBASE-12976:
--------------------------------

SUCCESS: Integrated in HBase-1.0 #814 (See [https://builds.apache.org/job/HBase-1.0/814/])
Revert "HBASE-12976 Set default value for hbase.client.scanner.max.result.size." (larsh: rev
be95f5329ae4603e727fb1ac5102edb1e7d2d3a2)
* 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)

Mime
View raw message