[
https://issues.apache.org/jira/browse/HBASE-11223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14005561#comment-14005561
]
Honghua Feng commented on HBASE-11223:
--------------------------------------
bq.This should be managed in the server rather than the client: there are other
clients around.
Agree that the server rather than the client should handle such case. But even
the server handles it, it also sounds reasonable to let the client
check-and-reject such huge batch request immediately and prevent transferring
it to the server, right?
> Limit the actions number of a call in the batch
> ------------------------------------------------
>
> Key: HBASE-11223
> URL: https://issues.apache.org/jira/browse/HBASE-11223
> Project: HBase
> Issue Type: Bug
> Components: Client
> Affects Versions: 0.99.0
> Reporter: Liu Shaohui
> Assignee: Liu Shaohui
>
> Huge batch operation will make regionserver crash for GC.
> The extreme code like this:
> {code}
> final List<Delete> deletes = new ArrayList<Delete>();
> final long rows = 4000000;
> for (long i = 0; i < rows; ++i) {
> deletes.add(new Delete(Bytes.toBytes(i)));
> }
> table.delete(deletes);
> {code}
> We should limit the actions number of a call in the batch.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
