'lost connection' is a SSH problem. Did you set up a SSH private key on your AWS/EC2 account named "root"?
Did you set EC2_ROOT_SSH_KEY in hbase-ec2-env.sh to the local filesystem path where the private key file is located? Are the permissions correct on the private key file? Try: chmod 600 /path/to/private/key. If all above fails, change '-q' to '-v -v' in SSH_OPTS in hbase-ec2-env.sh and retry. This will produce a lot of debug output from SSH on the console, which may point to the problem. - Andy ________________________________ From: Something Something <[email protected]> To: [email protected] Sent: Wed, December 9, 2009 8:25:41 PM Subject: Re: Starting HBase in fully distributed mode... When I run: hbase-ec2 launch-cluster testcluster 3 3 I keep getting 'lost connection' messages (See below). Tried this 4 times. Please help. Thanks. ------------------------------------------------------------- Creating/checking security groups Security group testcluster-master exists, ok Security group testcluster exists, ok Security group testcluster-zookeeper exists, ok Starting ZooKeeper quorum ensemble. Starting an AMI with ID ami-b0cb29d9 (arch i386) in group testcluster-zookeeper Waiting for instance i-9db6f4f5 to start: .................. Started ZooKeeper instance i-9db6f4f5 as domU-12-31-38-01-7D-D1.compute-1.internal Public DNS name is ec2-174-129-148-5.compute-1.amazonaws.com. Starting an AMI with ID ami-b0cb29d9 (arch i386) in group testcluster-zookeeper Waiting for instance i-2db7f545 to start: ................. Started ZooKeeper instance i-2db7f545 as domU-12-31-38-01-7D-43.compute-1.internal Public DNS name is ec2-174-129-157-122.compute-1.amazonaws.com. Starting an AMI with ID ami-b0cb29d9 (arch i386) in group testcluster-zookeeper Waiting for instance i-afb7f5c7 to start: ...................... Started ZooKeeper instance i-afb7f5c7 as domU-12-31-38-01-78-F3.compute-1.internal Public DNS name is ec2-174-129-179-14.compute-1.amazonaws.com. ZooKeeper quorum is domU-12-31-38-01-7D-D1.compute-1.internal,domU-12-31-38-01-7D-43.compute-1.internal,domU-12-31-38-01-78-F3.compute-1.internal. Initializing the ZooKeeper quorum ensemble. ec2-174-129-148-5.compute-1.amazonaws.com lost connection ec2-174-129-157-122.compute-1.amazonaws.com lost connection ec2-174-129-179-14.compute-1.amazonaws.com lost connection On Wed, Dec 9, 2009 at 12:46 AM, Seth Ladd <[email protected]> wrote: > > Sounds like others have used Andrew's script successfully. The only > > difference seems to be that it starts a *dedicated* ZooKeeper quorum. > > Should have listened to Mark when he suggested that 4 days ago :) > > > > Anyway, I will try Andrew's script tomorrow. > > I can vouch that the scripts in svn trunk work. Thanks to Andrew for > his help! I was able to start a 3 node Zookeeper and 5 node HBase > cluster on EC2 from just the scripts. > > Seth >
