[
https://issues.apache.org/jira/browse/HBASE-17408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15806211#comment-15806211
]
Hudson commented on HBASE-17408:
--------------------------------
SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #2271 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/2271/])
HBASE-17408 Introduce per request limit by number of mutations (ChiaPing
(tedyu: rev b2a9be02ac10908438dc84e9d483bc8785d7ce19)
* (edit)
hbase-client/src/test/java/org/apache/hadoop/hbase/client/TestSimpleRequestController.java
* (edit)
hbase-client/src/main/java/org/apache/hadoop/hbase/client/SimpleRequestController.java
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/coprocessor/RegionServerObserver.java
> 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)
