[
https://issues.apache.org/jira/browse/PHOENIX-3118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15392759#comment-15392759
]
Pierre Lacave commented on PHOENIX-3118:
----------------------------------------
small typo, but the default is 2MB not 2GB
https://github.com/apache/hbase/blob/master/hbase-common/src/main/resources/hbase-default.xml#L1326
{code}
<property>
<name>hbase.client.scanner.max.result.size</name>
<value>2097152</value>
<description>Maximum number of bytes returned when calling a scanner's next
method.
Note that when a single row is larger than this limit the row is still
returned completely.
The default value is 2MB, which is good for 1ge networks.
With faster and/or high latency networks this value should be increased.
</description>
</property>
{code}
> Increase default value of hbase.client.scanner.max.result.size
> --------------------------------------------------------------
>
> Key: PHOENIX-3118
> URL: https://issues.apache.org/jira/browse/PHOENIX-3118
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: James Taylor
> Fix For: 4.8.1
>
>
> See parent JIRA for a discussion on how to handle partial scan results. An
> easy workaround would be to increase the
> {{hbase.client.scanner.max.result.size}} above the default 2GB limit. In
> combination with this, we could detect in BaseScannerRegionObserver.nextRaw()
> if partial results are being returned and throw an exception. Silently
> ignoring this is bad because it can lead to incorrect query results as
> demonstrated by the parent JIRA.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
