[jira] [Commented] (HBASE-13362) Set max result size from client only (like scanner caching).

["Lars Hofhansl (JIRA)" <ji...@apache.org>]

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

Lars Hofhansl commented on HBASE-13362:
---------------------------------------

Pushed to master and 1.1 so far.
Will push the 0.98 here to 1.0 as well (leaving the server protection value at Long.MAX_VALUE, so it's backwards compatible with old clients).


> Set max result size from client only (like scanner caching).
> ------------------------------------------------------------
>
>                 Key: HBASE-13362
>                 URL: https://issues.apache.org/jira/browse/HBASE-13362
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Lars Hofhansl
>            Assignee: Lars Hofhansl
>             Fix For: 2.0.0, 1.1.0, 0.98.13
>
>         Attachments: 13362-0.98.txt, 13362-master-v2.txt, 13362-master.txt
>
>
> With the recent problems we've been seeing client/server result size mismatch, I was thinking: Why was this not a problem with scanner caching?
> There are two reasons:
> # number of rows is easy to calculate (and we did it correctly)
> # caching is only controlled from the client, never set on the server alone
> We did fix both #1 and #2 in HBASE-13262.
> Still, I'd like to discuss the following:
> * default the client sent max result size to 2mb
> * remove any server only result sizing
> * continue to use hbase.client.scanner.max.result.size but enforce it via the client only (as the name implies anyway).
> Comments? Concerns?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)