hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-1961) HBase EC2 scripts
Date Sun, 08 Nov 2009 01:30:32 GMT

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

stack commented on HBASE-1961:

Sweet Andrew.  Should we add this to our contrib?  Pity its hard to subclass bash scripts
but it is what it is.  Thats excellent that you can say how many RS instances and then also
how many instances in zk cluster.

You've posted amis already?  Ones for hbase?  Thats what these are:

i386: ami-c644a7af
x86_64: ami-f244a79b

The scripts look great:

[stack@aa0-000-12 ec2]$ ./bin/hbase-ec2 
Usage: hbase-ec2 COMMAND
where COMMAND is one of:
  list                                 list all running HBase EC2 clusters
  launch-cluster <group> <num slaves>  launch a cluster of HBase EC2 instances
- launch-master then launch-slaves
  launch-master  <group>               launch or find a cluster master
  launch-slaves  <group> <num slaves>  launch the cluster slaves
  terminate-cluster  <group>           terminate all HBase EC2 instances
  delete-cluster <group>               delete the group information for a terminated
  login  <group|instance id>           login to the master node of the HBase EC2 cluster
  screen <group|instance id>           start or attach 'screen' on the master node of
the HBase EC2 cluster
  proxy  <group|instance id>           start a socks proxy on localhost:6666 (use w/foxyproxy)
  push   <group> <file>                scp a file to the master node of the HBase
EC2 cluster
  <shell cmd> <group|instance id>      execute any command remotely on the master
  create-image                         create a HBase AMI

What you mean by a 'storage only cluster' above?

> 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
>            Priority: Minor
>             Fix For: 0.21.0, 0.20.3
>         Attachments: contrib-ec2.tar.bz2
> 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
> 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.

View raw message