[
https://issues.apache.org/jira/browse/HBASE-11223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14005802#comment-14005802
]
Nicolas Liochon commented on HBASE-11223:
-----------------------------------------
bq. right?
For sure :-)
But as it needs to be done server side anyway; and it's should remain an
extreme case (i.e. a bug in the client code) that we don't need to optimize,
imho there is no much value in doing it client side.
> 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)