[jira] [Commented] (TEPHRA-299) Executing a large batch delete is very slow

["Lars Hofhansl (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TEPHRA-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16842800#comment-16842800 ] 

Lars Hofhansl commented on TEPHRA-299:
--------------------------------------

Should I make a final patch and get this committed?
(I might still have commit rights... At least I'm still listed as developer. :) )

> Executing a large batch delete is very slow
> -------------------------------------------
>
>                 Key: TEPHRA-299
>                 URL: https://issues.apache.org/jira/browse/TEPHRA-299
>             Project: Tephra
>          Issue Type: Bug
>    Affects Versions: 0.15.0-incubating
>            Reporter: Lars Hofhansl
>            Assignee: Lars Hofhansl
>            Priority: Major
>         Attachments: 299-DOES-NOT_WORK.txt, 299-client-v2.txt, 299-client-v3.txt, 299-client.txt
>
>
> I noticed that batch deletes are quire slow. In the profiler I found that almost all of the time is spent in org.apache.hadoop.hbase.regionserver.wal.FSHLog.blockOnSync().
> Looking at TransactionProcessor.preDelete it is obvious why:
> The batch delete is translated into *single* puts that are added to the region one by one, so each time the WAL is flushed.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)