hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13297) 0.98 and 1.0: Remove client side result size calculation
Date Fri, 20 Mar 2015 07:20:38 GMT

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

Lars Hofhansl commented on HBASE-13297:

Actually, lemme think about the extra RPC. That would be would be one more RPC for every region
touched by a scanner. If the scanner touches one region only, we've doubled the number of
RPC. Also need to fix ClientSmallScanner...

Not sure there _is_ a better solution for 0.98... Or we can also document for 0.98 that one
must make 100% sure that client and server have the exact same value for hbase.client.scanner.max.result.size.

Ideally - like caching - this could be driven from the client, then there would not be a problem
either, I guess.

Let's do the RC as is, and we'll think about this for 0.98.13.

> 0.98 and 1.0: Remove client side result size calculation
> --------------------------------------------------------
>                 Key: HBASE-13297
>                 URL: https://issues.apache.org/jira/browse/HBASE-13297
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Client
>            Reporter: Lars Hofhansl
>            Assignee: Lars Hofhansl
>             Fix For: 1.0.1, 0.98.13
>         Attachments: 13297-0.98.txt
> As described in parent, this can lead to missed rows when the client and server calculate
different size values.
> The patch here proposes a backwards compatible patch for 0.98 and 1.0.x.
> Parent will do a patch for 1.1 and 2.0.

This message was sent by Atlassian JIRA

View raw message