[
https://issues.apache.org/jira/browse/WHIRR-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Savu updated WHIRR-334:
------------------------------
Attachment: WHIRR-334.patch
I've updated the patch so that we can apply it using the {{patch}} command
(Bruno please use {{git diff --no-prefix}} next time).
+1 for committing it. It seems like it works most of the time and on the long
term we should find a better way of handling the order of starting services.
> 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
>
>
> 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
