[
https://issues.apache.org/jira/browse/HBASE-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404698#comment-13404698
]
Hadoop QA commented on HBASE-6284:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12534145/HBASE-6284_Trunk-V2.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 hadoop2.0. The patch compiles against the hadoop 2.0 profile.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
-1 findbugs. The patch appears to introduce 7 new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hbase.TestZooKeeper
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/2306//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2306//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2306//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/2306//console
This message is automatically generated.
> Introduce HRegion#doMiniBatchDelete()
> -------------------------------------
>
> Key: HBASE-6284
> URL: https://issues.apache.org/jira/browse/HBASE-6284
> Project: HBase
> Issue Type: Bug
> Components: performance, regionserver
> Reporter: Zhihong Ted Yu
> Assignee: Anoop Sam John
> Fix For: 0.96.0, 0.94.2
>
> Attachments: HBASE-6284_Trunk-V2.patch, HBASE-6284_Trunk.patch
>
>
> From Anoop under thread 'Can there be a doMiniBatchDelete in HRegion':
> The HTable#delete(List<Delete>) groups the Deletes for the same RS and make
> one n/w call only. But within the RS, there will be N number of delete calls
> on the region one by one. This will include N number of HLog write and sync.
> If this also can be grouped can we get better performance for the multi row
> delete.
> I have made the new miniBatchDelete () and made the
> HTable#delete(List<Delete>) to call this new batch delete.
> Just tested initially with the one node cluster. In that itself I am getting
> a performance boost which is very much promising.
> Only one CF and qualifier.
> 10K total rows delete with a batch of 100 deletes. Only deletes happening on
> the table from one thread.
> With the new way the net time taken is reduced by more than 1/10
> Will test in a 4 node cluster also. I think it will worth doing this change.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
