hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Araujo (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14791) Batch Deletes in MapReduce jobs (0.98)
Date Wed, 18 Nov 2015 14:55:11 GMT

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

Alex Araujo commented on HBASE-14791:
-------------------------------------

Those build failures look unrelated. HBase-0.98-on-Hadoop-1.1 has been failing with a compilation
error since #[1132|https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/1132/]:

{noformat}
[ERROR] /home/jenkins/jenkins-slave/workspace/HBase-0.98-on-Hadoop-1.1/hbase-common/src/main/java/org/apache/hadoop/hbase/security/UserProvider.java:[70,49]
error: cannot find symbol
{noformat}

HBase-0.98-matrix appears to have unrelated test failures. Most of the failures have been
around since #[258|https://builds.apache.org/job/HBase-0.98-matrix/258/]. These are new, but
unrelated:

*jdk=latest1.7,label=Hadoop*

java.lang.ExceptionInInitializerError: null
	at org.apache.hadoop.hbase.HBaseConfiguration.checkDefaultsVersion(HBaseConfiguration.java:73)

hbase-default.xml file seems to be for and old version of HBase (0.98.16), this version is
0.98.17-SNAPSHOT

java.lang.ExceptionInInitializerError: null
	at org.apache.hadoop.hbase.HBaseConfiguration.checkDefaultsVersion(HBaseConfiguration.java:73)
	at org.apache.hadoop.hbase.HBaseConfiguration.addHbaseResources(HBaseConfiguration.java:105)
	at org.apache.hadoop.hbase.HBaseConfiguration.create(HBaseConfiguration.java:120)
	at org.apache.hadoop.hbase.HBaseCommonTestingUtility.<init>(HBaseCommonTestingUtility.java:46)
	at org.apache.hadoop.hbase.TestClassFinder.<clinit>(TestClassFinder.java:57)

Could not initialize class org.apache.hadoop.hbase.TestClassFinder
java.lang.NoClassDefFoundError: Could not initialize class org.apache.hadoop.hbase.TestClassFinder

Could not initialize class org.apache.hadoop.hbase.util.TestCoprocessorClassLoader
java.lang.NoClassDefFoundError: Could not initialize class org.apache.hadoop.hbase.util.TestCoprocessorClassLoader

Could not initialize class org.apache.hadoop.hbase.util.TestDynamicClassLoader
java.lang.NoClassDefFoundError: Could not initialize class org.apache.hadoop.hbase.util.TestDynamicClassLoader

*jdk=latest1.6,label=Hadoop*

java.lang.NoSuchFieldError: in
	at org.apache.hadoop.hbase.codec.CellCodecWithTags$CellDecoder.parseCell(CellCodecWithTags.java:86)
	at org.apache.hadoop.hbase.codec.BaseDecoder.advance(BaseDecoder.java:67)
	at org.apache.hadoop.hbase.codec.TestCellCodecWithTags.testCellWithTag(TestCellCodecWithTags.java:76)

java.lang.NoSuchFieldError: in
	at org.apache.hadoop.hbase.codec.KeyValueCodec$KeyValueDecoder.parseCell(KeyValueCodec.java:70)
	at org.apache.hadoop.hbase.codec.BaseDecoder.advance(BaseDecoder.java:67)
	at org.apache.hadoop.hbase.codec.TestKeyValueCodec.testOne(TestKeyValueCodec.java:80)



> 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)

Mime
View raw message