[
https://issues.apache.org/jira/browse/WHIRR-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974921#action_12974921
]
Lars George commented on WHIRR-25:
----------------------------------
OK, I added WHIRR-174 (and WHIRR-175 in the process), both fix the stand-alone
ZooKeeper setup and this is working fine now using for example a config like
{code}whirr.cluster-name=hbasetest
whirr.instance-templates=1 zk,1 jt+nn+hbase-master,5 dn+tt+hbase-regionserver
whirr.provider=ec2
whirr.identity=...
whirr.credential=...
whirr.private-key-file=${sys:user.home}/.ssh/id_rsa
whirr.hardware-id=m1.large
whirr.image-id=us-east-1/ami-da0cf8b3
whirr.location-id=us-east-1
whirr.run-url-base=http://testwhirr.s3.amazonaws.com/whirr-trunk/
{code}
Note: The "testwhirr" bucket is holding the content of the local "script/"
directory.
Next up is ZK managed by HBase, which is done like so:
* Check if there is no "zk" role in the template -> set HBaseManagesZK = true
* Emit a zoo.cfg from the HBase post-configure script next to the hbase-site.xml
* Set the option in hbase-env.sh to indicate that HBase manages ZK:
{code}HBASE_MANAGES_ZK=true{code}
> Add HBase service
> -----------------
>
> Key: WHIRR-25
> URL: https://issues.apache.org/jira/browse/WHIRR-25
> Project: Whirr
> Issue Type: New Feature
> Reporter: Tom White
> Assignee: Lars George
> Fix For: 0.3.0
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
