[
https://issues.apache.org/jira/browse/HBASE-12976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14370038#comment-14370038
]
Lars Hofhansl commented on HBASE-12976:
---------------------------------------
In the light of HBASE-13262, do we need to undo this change?!
It seems that when client and server do not agree about the expected size we
will lose data during scanning.
Now say we run with an old client that sees the old default setting of
Long.MAX_VALUE, but now it get chunks of 2mb back.
> 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)
