Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <497153849.1260055640693.JavaMail.jira@brutus>
Date: Sat, 5 Dec 2009 23:27:20 +0000 (UTC)
From: "Seth Ladd (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-1961) HBase EC2 scripts
In-Reply-To: <722272007.1257617733604.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

Thanks Andrew, that allowed my zookeeper instances to start!  I received a 503 when (apparently) trying to start the hbase nodes.  But I'll try again.

org.codehaus.xfire.fault.XFireFault: Server returned error code = 503 for URI : https://ec2.amazonaws.com. Check server logs for details
	at org.codehaus.xfire.fault.XFireFault.createFault(XFireFault.java:89)
	at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:83)
	at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:114)
	at org.codehaus.xfire.client.Client.invoke(Client.java:336)
	at org.codehaus.xfire.client.XFireProxy.handleRequest(XFireProxy.java:77)
	at org.codehaus.xfire.client.XFireProxy.invoke(XFireProxy.java:57)
	at $Proxy12.describeInstances(Unknown Source)
	at com.amazon.aes.webservices.client.Jec2.describeInstances(Jec2.java:1390)
	at com.amazon.aes.webservices.client.Jec2.describeInstances(Jec2.java:1354)
	at com.amazon.aes.webservices.client.cmd.DescribeInstances.invokeOnline(DescribeInstances.java:49)
	at com.amazon.aes.webservices.client.cmd.BaseCmd.invoke(BaseCmd.java:719)
	at com.amazon.aes.webservices.client.cmd.DescribeInstances.main(DescribeInstances.java:58)
Caused by: org.codehaus.xfire.XFireRuntimeException: Server returned error code = 503 for URI : https://ec2.amazonaws.com. Check server logs for details
	at org.codehaus.xfire.transport.http.HttpChannel.sendViaClient(HttpChannel.java:130)
	at org.codehaus.xfire.transport.http.HttpChannel.send(HttpChannel.java:48)
	at org.codehaus.xfire.handler.OutMessageSender.invoke(OutMessageSender.java:26)
	at org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
	at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:79)
	... 10 more
.[Deprecated] Xalan: org.apache.xml.res.XMLErrorResources_en_US
 Started ZooKeeper instance i-cd5014a5 as ip-10-212-149-139.ec2.internal
[Deprecated] Xalan: org.apache.xml.res.XMLErrorResources_en_US
    Public DNS name is ec2-75-101-218-238.compute-1.amazonaws.com.
ZooKeeper quorum is ip-10-245-63-79.ec2.internal,ip-10-212-151-194.ec2.internal,ip-10-212-149-139.ec2.internal.
Initializing the ZooKeeper quorum ensemble.
    ec2-72-44-53-128.compute-1.amazonaws.com
lost connection
    ec2-174-129-77-191.compute-1.amazonaws.com
lost connection
    ec2-75-101-218-238.compute-1.amazonaws.com
lost connection


> 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.