You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Nicolas Liochon (JIRA)" <ji...@apache.org> on 2014/05/21 15:24:39 UTC
[jira] [Commented] (HBASE-11223) Limit the actions number of a call
in the batch
[ https://issues.apache.org/jira/browse/HBASE-11223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14004651#comment-14004651 ]
Nicolas Liochon commented on HBASE-11223:
-----------------------------------------
This should be managed in the server rather than the client: there are other clients around. There is already some code in the server around this category of issue (gc due to request queue, this kind of things).
> 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)