[jira] [Commented] (HBASE-14791) Batch Deletes in MapReduce jobs (0.98)

["Andrew Purtell (JIRA)" <ji...@apache.org>]

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

Andrew Purtell commented on HBASE-14791:
----------------------------------------

I think HadoopQA may be MIA at the moment. I'll apply this patch now and run the mapreduce tests locally. I assume you've determined the patch addresses the reported perf issues satisfactorily [~alexaraujo]? 

> Batch Deletes in MapReduce jobs (0.98)
> --------------------------------------
>
>                 Key: HBASE-14791
>                 URL: https://issues.apache.org/jira/browse/HBASE-14791
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.98.16
>            Reporter: Lars Hofhansl
>            Assignee: Alex Araujo
>              Labels: mapreduce
>             Fix For: 0.98.17
>
>         Attachments: HBASE-14791-0.98-v1.patch, HBASE-14791-0.98-v2.patch, HBASE-14791-0.98.patch
>
>
> We found that some of our copy table job run for many hours, even when there isn't that much data to copy.
> [~vik.karma] did his magic and found that the issue is with copying delete markers (we use raw mode to also move deletes across).
> Looking at the code in 0.98 it's immediately obvious that deletes (unlike puts) are not batched and hence sent to the other side one by one, causing a network RTT for each delete marker.
> Looks like in trunk it's doing the right thing (using BufferedMutators for all mutations in TableOutputFormat). So likely only a 0.98 (and 1.0, 1.1, 1.2?) issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)