[jira] [Updated] (HBASE-13362) set max result size from client only (like caching)?

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

     [ https://issues.apache.org/jira/browse/HBASE-13362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lars Hofhansl updated HBASE-13362:
----------------------------------
    Attachment: 13362-master.txt

extra trivial patch

* a client will rarely request chunk of 100mb or more even with 10ge networks (about 100ms transmission time with 10ge)
* the client's default limit remains 2mb, which is nice for 1ge and acceptable for 10ge networks (15ms and 1.5ms transmission time, resp, both way larger than intra DC latency)

I'll make a 0.98 and 1.0 patch as well, to make that part of the logic the same.

> set max result size from client only (like caching)?
> ----------------------------------------------------
>
>                 Key: HBASE-13362
>                 URL: https://issues.apache.org/jira/browse/HBASE-13362
>             Project: HBase
>          Issue Type: Brainstorming
>            Reporter: Lars Hofhansl
>         Attachments: 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)