[
https://issues.apache.org/jira/browse/HBASE-14791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15010881#comment-15010881
]
Hudson commented on HBASE-14791:
--------------------------------
FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #1134 (See
[https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/1134/])
HBASE-14791 Batch Deletes in MapReduce jobs (larsh: rev
d25d74e121901d4d9705ae2c94256d947ad0a708)
*
hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestBufferedHTable.java
*
hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/MultiTableOutputFormat.java
*
hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/TableOutputFormat.java
*
hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/BufferedHTable.java
> 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)
