You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2017/01/03 18:02:58 UTC
[jira] [Updated] (HBASE-17408) Introduce per request limit by
number of mutations
[ https://issues.apache.org/jira/browse/HBASE-17408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Yu updated HBASE-17408:
---------------------------
Description:
HBASE-16224 introduced hbase.client.max.perrequest.heapsize to limit the amount of data sent from client.
We should consider adding per request limit through the number of mutations in a batch.
In recent troubleshooting sessions, customer had to do this in their application code to avoid OOME on the server side.
was:
HBASE-16224 introduced hbase.client.max.perrequest.heapsize to limit the amount of data sent from client.
We should consider adding per request limit through the number of mutations in a batch.
In recent troubleshooting sessions, customer had to do this in their application code.
> Introduce per request limit by number of mutations
> --------------------------------------------------
>
> Key: HBASE-17408
> URL: https://issues.apache.org/jira/browse/HBASE-17408
> Project: HBase
> Issue Type: Improvement
> Reporter: Ted Yu
>
> HBASE-16224 introduced hbase.client.max.perrequest.heapsize to limit the amount of data sent from client.
> We should consider adding per request limit through the number of mutations in a batch.
> In recent troubleshooting sessions, customer had to do this in their application code to avoid OOME on the server side.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)