[
https://issues.apache.org/jira/browse/WHIRR-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064639#comment-13064639
]
Bruno Dumon commented on WHIRR-240:
-----------------------------------
I added a patch which should solve the problem.
It copies (actually links) the hadoop-core jar of the installed Hadoop version
to the HBase lib dir, which is the opposite of what was suggested in the
description of this patch. Cloudera does exactly the same in their Linux
packages.
This solution requires that Hadoop is installed on each node where HBase is
installed. Usually this is the case (hadoop-namenode+hbase-master and
hadoop-datanode+hbase-regionserver).
The usual suggestion in the HBase community is to use the CDH Hadoop version.
You can combine stock HBase with CDH Hadoop by using the following properties:
whirr.hbase.tarball.url=http://apache.cu.be//hbase/hbase-0.90.3/hbase-0.90.3.tar.gz
whirr.hadoop.tarball.url=http://archive.cloudera.com/cdh/3/hadoop-0.20.2-cdh3u0.tar.gz
Note that this uses the .tar.gz release of Cloudera, and not Whirr's special
cdh support which uses the Linux packages instead. I do it that way because the
CDH linux packages use different conventions from Whirr (e.g. different Linux
users).
I tried this on a small byon cluster and it seems to work fine. It doesn't seem
to need the 'wait for namenode' loop before starting hbase as suggested in
WHIRR-334, though it might be that this is due to byon timing differences.
> [HBase] Enable support for HBase 0.90.x
> ---------------------------------------
>
> Key: WHIRR-240
> URL: https://issues.apache.org/jira/browse/WHIRR-240
> Project: Whirr
> Issue Type: New Feature
> Components: service/hbase
> Affects Versions: 0.3.0
> Reporter: Lars George
> Attachments: WHIRR-240.patch
>
>
> HBase 0.90.0 is a difficult release as it either needs CDH or a patched
> Hadoop (with append) to work. The Apache tarballs won't do and HBase will not
> start.
> One way possible is to deploy the Apache Hadoop 0.20.2 tarball and then
> override the core jar with the one supplied by HBase. Since HBase relies on
> Hadoop to be setup by the Whirr service we would need some surgery that would
> imply service ordering.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
