You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2021/12/09 01:17:00 UTC

[jira] [Commented] (HBASE-26122) Limit max result size of individual Gets

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

Andrew Kyle Purtell commented on HBASE-26122:
---------------------------------------------

What is the status of this change? Has it been reverted everywhere?

> Limit max result size of individual Gets
> ----------------------------------------
>
>                 Key: HBASE-26122
>                 URL: https://issues.apache.org/jira/browse/HBASE-26122
>             Project: HBase
>          Issue Type: New Feature
>          Components: Client, regionserver
>            Reporter: Bryan Beaudreault
>            Assignee: Bryan Beaudreault
>            Priority: Major
>             Fix For: 2.5.0, 3.0.0-alpha-2
>
>
> Scans have the ability to have a configured max result size, which causes them to return a partial result once the limit has been reached. MultiGets also can throw MultiActionResultTooLarge if the response size is over a configured quota. Neither of these really accounts for a single Get of a too-large row. Such too-large Gets can cause substantial GC pressure or worse if sent at volume.
> Currently one can work around this by converting their Get to a single row Scan, but this requires a developer to proactively know about and prepare for the issue by using a Scan upfront or wait for the RegionServer to choke on a large request and only then rewrite the Get for future requests.
> We should implement the same response size limits for for Get as for Scan, whereby the server returns a partial result to the client for handling.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)