[
https://issues.apache.org/jira/browse/TEPHRA-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16817214#comment-16817214
]
Lars Hofhansl commented on TEPHRA-299:
--------------------------------------
Aaaaad. -v3 is a minimal version.
Note that all the client version are backwards compatible. The Puts are the
same the coprocessor would have generated and for an old client the coprocessor
will still step in and do the translation.
-v3 is safe, easy to verify, and should be good to go.
> 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: Poorna Chandra
> 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)
