hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HBASE-17408) Introduce per request limit by number of mutations
Date Wed, 11 Jan 2017 21:56:16 GMT

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

Ted Yu edited comment on HBASE-17408 at 1/11/17 9:56 PM:

Thanks for providing more background, [~enis]

was (Author: yuzhihong@gmail.com):
Thanks for providing more background, [~enis]

I was waiting for server log with DEBUG log showing bloated exception size in response. The
operator didn't know all the steps of how to deploy the hbase-server jar over the long weekend.

> 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

View raw message