[
https://issues.apache.org/jira/browse/WHIRR-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065823#comment-13065823
]
Bruno Dumon commented on WHIRR-334:
-----------------------------------
I realized the wait loop could be easily adjusted to wait for at least one
datanode to be up. Since we're wget'ing the hadoop web ui we can as well grep
it for the number of datanodes. I've adjusted the patch in this regard
(WHIRR-334-5.patch).
Tested on EC2.
In summary, this patch contains the following:
- the changes from the patch of June 24
- fix for ZK service script name:
https://github.com/bdumon/whirr/commit/0f9910439c2025240828b34af6442ebedd72bca2
- HDFS-wait-loop before starting HBase:
https://github.com/bdumon/whirr/commit/b160a0f8345524fcb9ddd5301550d9fa48b0b865
Here's an exmple of the output of the HDFS wait loop:
{noformat}
hadoop-hbase-master restart: waiting for HDFS to be available -- Fri Jul 15
08:32:38 UTC 2011
hadoop-hbase-master restart: waiting for HDFS to be available -- Fri Jul 15
08:32:41 UTC 2011
hadoop-hbase-master restart: waiting for HDFS to be available -- Fri Jul 15
08:32:44 UTC 2011
hadoop-hbase-master restart: waiting for HDFS to be available -- Fri Jul 15
08:32:47 UTC 2011
hadoop-hbase-master restart: waiting for HDFS to be available -- Fri Jul 15
08:32:50 UTC 2011
hadoop-hbase-master restart: waiting for HDFS to be available -- Fri Jul 15
08:32:53 UTC 2011
hadoop-hbase-master restart: waiting for HDFS to be available -- Fri Jul 15
08:32:56 UTC 2011
hadoop-hbase-master restart: waiting for HDFS to be available -- Fri Jul 15
08:32:59 UTC 2011
Live Datanodes : 2
Restarting Hadoop HBase master daemon: no master to stop because no pid file
/var/run/hbase/hbase-hbase-master.pid
Starting Hadoop HBase master daemon: starting master, logging to
/var/log/hbase/logs/hbase-hbase-master-ip-10-50-37-175.out
hbase-master.
{noformat}
What I said in my previous comment about double java processes can be ignored,
the double one was not Java itself but "su mapred -s
/usr/lib/jvm/java-6-sun/bin/java"
> Support for CDH3u0 HBase
> ------------------------
>
> Key: WHIRR-334
> URL: https://issues.apache.org/jira/browse/WHIRR-334
> Project: Whirr
> Issue Type: Bug
> Components: service/hbase
> Affects Versions: 0.5.0
> Reporter: Andrei Savu
> Assignee: Andrei Savu
> Fix For: 0.5.0, 0.6.0
>
> Attachments: WHIRR-334-2.patch, WHIRR-334-3.patch, WHIRR-334-4.patch,
> WHIRR-334-5.patch, WHIRR-334.patch, WHIRR-334.patch, WHIRR-334.patch
>
>
> Message from Geoff Black on the Github pull request [1]:
> {quote}
> I've updated the cdh services scripts and ZooKeeperClusterActionHandler.java
> to properly work with CDH3 when setting up an HBase cluster. Tested multiple
> times with 1 master + 1 region and also 1 master + 5 region on EC2.
> The only issue I ran into was previously documented in
> https://issues.apache.org/jira/browse/HBASE-1960 where the HBase Master shuts
> down after only one attempt to access DFS. This is something that should be
> addressed by the HBase team or a fix integrated by Cloudera into CDH.
> {quote}
> [1] https://github.com/apache/whirr/pull/1
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
