[
https://issues.apache.org/jira/browse/HBASE-12976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl updated HBASE-12976:
----------------------------------
Attachment: TestMaxResultSize.txt
Here's a patch with a test illustrating the problem in 0.98. Server with a
limit, client without a limit. The scanner will only see one of the two
inserted rows.
(In trunk is does not happen this way since the client will pass its size
configuration down to the server where it will override the server setting)
> 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, TestMaxResultSize.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)
