[
https://issues.apache.org/jira/browse/WHIRR-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13070157#comment-13070157
]
Bruno Dumon commented on WHIRR-334:
-----------------------------------
I updated the patch for CDH3u1:
* configure_cdh_hbase: removed delayed_restart trick
* configure_cdh_hbase: add hbase.zookeeper.recoverable.waittime
* configure_cdh_hbase: install daemon package after configuration is performed
(otherwise it first starts against default conf), don't restart on debian as
it's not necessary.
* install_cdh_zookeeper/configure_cdh_zookeeper: install daemon package after
configuration is performed. This aligns with how things are done in general,
and otherwise this will expire client's ZK sessions due to changed ZK server
identities.
* configure_cdh_zookeeper: the service is now also called
'hadoop-zookeeper-server' on rpm systems
I ran the integration tests (of CDH Hadoop, ZooKeeper and HBase) with
everything default except for whirr.hardware-id=m1.large. These all ran
successfully.
Then I also ran the integration tests on Amazon's own Linux images, which are
rpm based, using these properties:
whirr.image-id=us-east-1/ami-221fec4b
jclouds.ec2.ami-owners=137112412989
whirr.login-user=ec2-user
whirr.hardware-id=m1.large
These tests ran also successful.
IMHO this patch is ready know. Once this is in, I can look into adjusting my
other patches to trunk. Probably WHIRR-240 first?
> 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-test.patch, WHIRR-334.patch, WHIRR-334.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
