Return-Path: Delivered-To: apmail-hadoop-hbase-user-archive@minotaur.apache.org Received: (qmail 72492 invoked from network); 10 Dec 2009 17:21:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 10 Dec 2009 17:21:11 -0000 Received: (qmail 90014 invoked by uid 500); 10 Dec 2009 17:21:10 -0000 Delivered-To: apmail-hadoop-hbase-user-archive@hadoop.apache.org Received: (qmail 89956 invoked by uid 500); 10 Dec 2009 17:21:09 -0000 Mailing-List: contact hbase-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-user@hadoop.apache.org Delivered-To: mailing list hbase-user@hadoop.apache.org Received: (qmail 89945 invoked by uid 99); 10 Dec 2009 17:21:09 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Dec 2009 17:21:09 +0000 X-ASF-Spam-Status: No, hits=3.4 required=10.0 tests=HTML_MESSAGE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [76.13.9.51] (HELO web65507.mail.ac4.yahoo.com) (76.13.9.51) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 10 Dec 2009 17:20:58 +0000 Received: (qmail 96117 invoked by uid 60001); 10 Dec 2009 17:20:36 -0000 Message-ID: <795673.92962.qm@web65507.mail.ac4.yahoo.com> X-YMail-OSG: YAMkoLoVM1k.TkJGSCqJDdFTLGJu6ep4zF60LEf2PieTA_1rYXkrMfOez2xDh4OgOg2HpHfakiooBONNNcfQPKMOyo.t16gp3qDZD1tQWeXZp4JMmv_wqSx8aCpSPFkRn_VwlL.0jQRlAG.Jh.Xl.y7NgpYxnJUQ7tdlDfb_6YvU11ZWAvREblqsVEiXPvmJgrFMnW3nQf9zsoVkzU1tra72wZ5XvdjSa9urvWs9cQyhvOJmHIzHpuDgSgjhX0hH3ztRKQImce7MY4RX4OD9h_cOhtgAr2hFpHEb.caeUnBte9vLi9dhDLy9zAT8LOkL6.0uvWcj7zmXgiJj6TR4aTotG.2X8OwRf7Ub1JQMDSZJP4FnBWdGjDpprS.h4mqYwd1yV9azFjsTapHiN7b7xPmyaKGqja80_wT59yg2_kgdyGo2PJVASXBH96WUeBF.svmXeICxCJoTwbOqzo_WJGL2Uzm.70pPCZaLH33vswLT4gfNt2.On4TpwUnecCty0j0lERC06YiVyxQvzEg- Received: from [68.123.237.158] by web65507.mail.ac4.yahoo.com via HTTP; Thu, 10 Dec 2009 09:20:36 PST X-RocketYMMF: apurtell X-Mailer: YahooMailRC/240.3 YahooMailWebService/0.8.100.260964 References: <1eabbac30912032327oc05965fj2b4148289ce6a235@mail.gmail.com> <358520.81120.qm@web65515.mail.ac4.yahoo.com> <1eabbac30912080940o51334a1bmdb3a987b6bb794ed@mail.gmail.com> <161050.32757.qm@web65506.mail.ac4.yahoo.com> <1eabbac30912081111r495d4f20pb6fc6d1b8a837c98@mail.gmail.com> <2eef7bd70912081132k3960ab57ud12ac04403a4bd3@mail.gmail.com> <4B1EB7B9.7070609@apache.org> <471947.87396.qm@web65516.mail.ac4.yahoo.com> <1eabbac30912082308s4b507224n2d4f5315c1fc8d7b@mail.gmail.com> <64f07e2c0912090046m4d281af3w857bf8acced92293@mail.gmail.com> <1eabbac30912092025j4278863bm31112d216962729e@mail.gmail.com> Date: Thu, 10 Dec 2009 09:20:36 -0800 (PST) From: Andrew Purtell Subject: Re: Starting HBase in fully distributed mode... To: hbase-user@hadoop.apache.org In-Reply-To: <1eabbac30912092025j4278863bm31112d216962729e@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1691446822-1260465636=:92962" X-Virus-Checked: Checked by ClamAV on apache.org --0-1691446822-1260465636=:92962 Content-Type: text/plain; charset=us-ascii '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 To: hbase-user@hadoop.apache.org 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 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 > --0-1691446822-1260465636=:92962--