You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2014/06/05 20:41:02 UTC
[jira] [Commented] (HBASE-98) [hbase] Region split broken
[ https://issues.apache.org/jira/browse/HBASE-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019078#comment-14019078 ]
Hudson commented on HBASE-98:
-----------------------------
SUCCESS: Integrated in flume-trunk #637 (See [https://builds.apache.org/job/flume-trunk/637/])
FLUME-2397: HBase-98 compatibility (jarcec: http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=0cba73698dbba6b78d0a2cd7b469f4377723470a)
* flume-ng-sinks/flume-ng-hbase-sink/src/main/java/org/apache/flume/sink/hbase/AsyncHBaseSink.java
* pom.xml
* flume-ng-sinks/flume-hdfs-sink/pom.xml
* flume-ng-sinks/flume-ng-hbase-sink/src/test/java/org/apache/flume/sink/hbase/TestAsyncHBaseSink.java
* flume-ng-sinks/flume-ng-hbase-sink/pom.xml
> [hbase] Region split broken
> ---------------------------
>
> Key: HBASE-98
> URL: https://issues.apache.org/jira/browse/HBASE-98
> Project: HBase
> Issue Type: Bug
> Reporter: Jim Kellerman
> Attachments: console.txt
>
>
> testSplitRegionIsDeleted failed in Hadoop-Nightly #207. From the log for that test (attached), it appears that it tries to split the region 3 times instead of just once.
> I did see the error:
> [junit] Exception in thread "HMaster.metaScanner" java.lang.IllegalArgumentException: Can't build a writable with empty bytes array
> [junit] at org.apache.hadoop.hbase.util.Writables.getWritable(Writables.java:77)
> [junit] at org.apache.hadoop.hbase.HMaster$BaseScanner.scanRegion(HMaster.java:272)
> [junit] at org.apache.hadoop.hbase.HMaster$MetaScanner.scanOneMetaRegion(HMaster.java:602)
> [junit] at org.apache.hadoop.hbase.HMaster$MetaScanner.maintenanceScan(HMaster.java:659)
> [junit] at org.apache.hadoop.hbase.HMaster$BaseScanner.run(HMaster.java:175)
> [junit] at java.lang.Thread.run(Thread.java:595)
> and afterwards there were no reports from the metaScanner so this may be related to HADOOP-1730
--
This message was sent by Atlassian JIRA
(v6.2#6252)