hbase-issues mailing list archives

[jira] [Commented] (HBASE-17408) Introduce per request limit by number of mutations

Date

Fri, 06 Jan 2017 02:33:58 GMT

[ https://issues.apache.org/jira/browse/HBASE-17408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15803286#comment-15803286
]
ChiaPing Tsai commented on HBASE-17408:
---------------------------------------
bq. Should we do a follow up for the server side as well
Do you mean the servers process the partial rows, and then return exception for making client
retry the remaining rows?
> 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
> Affects Versions: 2.0.0
> Reporter: Ted Yu
> Assignee: ChiaPing Tsai
> Fix For: 2.0.0
>
> Attachments: HBASE-17408.v0.patch, HBASE-17408.v1.patch, HBASE-17408.v2.patch
>
>
> 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)