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] [Updated] (HBASE-14946) Don't allow multi's to over run the max result size.
Date Fri, 11 Dec 2015 03:01:11 GMT

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

Elliott Clark updated HBASE-14946:
    Release Note: The HBase region server will now send a chunk of get responses to a client
if the total response size is too large. This will only be done for clients 1.2.0 and beyond.
Older clients by default will have the old behavior.

> 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
>             Fix For: 2.0.0, 1.2.0, 1.3.0
>         Attachments: HBASE-14946-v1.patch, HBASE-14946-v10.patch, HBASE-14946-v11.patch,
HBASE-14946-v2.patch, HBASE-14946-v3.patch, HBASE-14946-v5.patch, HBASE-14946-v6.patch, HBASE-14946-v7.patch,
HBASE-14946-v8.patch, HBASE-14946-v9.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

View raw message