[jira] Commented: (HBASE-1961) HBase EC2 scripts

["Seth Ladd (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786505#action_12786505 ] 

Seth Ladd commented on HBASE-1961:
----------------------------------

Thanks very much for providing these scripts!

I've pulled the latest from svn (as of 2009-12-05) and when I run "bin/hbase-ec2 launch-cluster sethbase 5 5" I can see this in the output:

[Deprecated] Xalan: org.apache.xml.res.XMLErrorResources_en_US
Starting ZooKeeper quorum ensemble.
/Users/sethladd/Code/hbase/trunk/src/contrib/ec2/bin/launch-hbase-zookeeper: line 70: seq: command not found
ZooKeeper quorum is .
Initializing the ZooKeeper quorum ensemble.
Testing for existing master in group: sethbase
[Deprecated] Xalan: org.apache.xml.res.XMLErrorResources_en_US
[Deprecated] Xalan: org.apache.xml.res.XMLErrorResources_en_US
Starting master with AMI  (arch x86_64)
Required parameter 'AMI' missing (-h for usage)
Waiting for instance  to start.[Deprecated] Xalan: org.apache.xml.res.XMLErrorResources_en_US
.[Deprecated] Xalan: org.apache.xml.res.XMLErrorResources_en_US

Notice the "line 70: seq: command not found"
Also notice the "Required parameter 'AMI' missing

I am running this on Mac OS X 10.6.  I have also just downloaded the EC2 AMI and API tools (as of 2009-12-05)

Also, it appears like nothing is starting (though I don't know how long it usually takes) but I just see a ".[Deprecated] Xalan: org.apache.xml.res.XMLErrorResources_en_US" repeated over and over.

Any ideas or tips?

Thanks again for the scripts and the help!

> HBase EC2 scripts
> -----------------
>
>                 Key: HBASE-1961
>                 URL: https://issues.apache.org/jira/browse/HBASE-1961
>             Project: Hadoop HBase
>          Issue Type: New Feature
>         Environment: Amazon AWS EC2
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>            Priority: Minor
>
> Attached tarball is a clone of the Hadoop EC2 scripts, modified significantly to start up a HBase storage only cluster on top of HDFS backed by instance storage. 
> Tested with the HBase 0.20 branch but should work with trunk also. Only the AMI create and launch scripts are tested. Will bring up a functioning HBase cluster. 
> Do "create-hbase-image c1.xlarge" to create an x86_64 AMI, or "create-hbase-image c1.medium" to create an i386 AMI.  Public Hadoop/HBase 0.20.1 AMIs are available:
>     i386: ami-c644a7af
>     x86_64: ami-f244a79b
> launch-hbase-cluster brings up the cluster: First, a small dedicated ZK quorum, specifiable in size, default of 3. Then, the DFS namenode (formatting on first boot) and one datanode and the HBase master. Then, a specifiable number of slaves, instances running DFS datanodes and HBase region servers.  For example:
> {noformat}
>     launch-hbase-cluster testcluster 100 5
> {noformat}
> would bring up a cluster with 100 slaves supported by a 5 node ZK ensemble.
> We must colocate a datanode with the namenode because currently the master won't tolerate a brand new DFS with only namenode and no datanodes up yet. See HBASE-1960. By default the launch scripts provision ZooKeeper as c1.medium and the HBase master and region servers as c1.xlarge. The result is a HBase cluster supported by a ZooKeeper ensemble. ZK ensembles are not dynamic, but HBase clusters can be grown by simply starting up more slaves, just like Hadoop. 
> hbase-ec2-init-remote.sh can be trivially edited to bring up a jobtracker on the master node and task trackers on the slaves.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.