hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elliott Clark (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14946) Don't allow multi's to over run the max result size.
Date Wed, 09 Dec 2015 20:02:11 GMT

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

Elliott Clark commented on HBASE-14946:
---------------------------------------

So I wrote the test and it took a while because the client was doing exponential back off
when it saw the exception. So I'm going to wire up a special exception that will mean don't
increase the backoff time.
[~ghelmling] brought up that this could break users of older clients who were ok asking for
very large gets. So this is a little larger than it was before.

> Don't allow multi's to over run the max result size.
> ----------------------------------------------------
>
>                 Key: HBASE-14946
>                 URL: https://issues.apache.org/jira/browse/HBASE-14946
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 2.0.0, 1.2.0, 1.3.0
>            Reporter: Elliott Clark
>            Assignee: Elliott Clark
>            Priority: Critical
>         Attachments: HBASE-14946-v1.patch, HBASE-14946-v2.patch, HBASE-14946-v3.patch,
HBASE-14946-v5.patch, HBASE-14946.patch
>
>
> If a user puts a list of tons of different gets into a table we will then send them along
in a multi. The server un-wraps each get in the multi. While no single get may be over the
size limit the total might be.
> We should protect the server from this. 
> We should batch up on the server side so each RPC is smaller.



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

Mime
View raw message