[
https://issues.apache.org/jira/browse/WHIRR-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13055635#comment-13055635
]
Tom White commented on WHIRR-334:
---------------------------------
> I believe we should commit this one before WHIRR-294.
OK
> Should we consider fixing WHIRR-221 so that we can have a more predictable
> cluster launch process?
It sounds like that would be useful in this case. Really we want a DAG of
dependencies, not just a list, but a list is probably good enough to start with.
> 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.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
