Return-Path: Delivered-To: apmail-hadoop-hbase-user-archive@minotaur.apache.org Received: (qmail 41671 invoked from network); 2 Aug 2009 20:31:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 2 Aug 2009 20:31:17 -0000 Received: (qmail 47159 invoked by uid 500); 2 Aug 2009 20:31:22 -0000 Delivered-To: apmail-hadoop-hbase-user-archive@hadoop.apache.org Received: (qmail 47074 invoked by uid 500); 2 Aug 2009 20:31:21 -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 47064 invoked by uid 99); 2 Aug 2009 20:31:21 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Aug 2009 20:31:21 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [209.249.141.200] (HELO CorpDC-ASMX02.uscorp.audiencescience.com) (209.249.141.200) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Aug 2009 20:31:09 +0000 X-AuditID: ac120b16-b7b9bae000005d70-f7-4a75f7774d5c Received: from corpdc-exch01.corp.digimine.com (Unknown_Domain [172.18.16.20]) by CorpDC-ASMX02.uscorp.audiencescience.com (Symantec Brightmail Gateway) with SMTP id 4C.F0.23920.777F57A4; Sun, 2 Aug 2009 13:30:47 -0700 (PDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: problem starting Hbase 0.20 with Katta on EC2 Date: Sun, 2 Aug 2009 13:33:08 -0700 Message-ID: <4B94F7D3090A974E94A9BD23E57BB14302DDE114@corpdc-exch01.corp.digimine.com> In-Reply-To: <2eef7bd70908021255j1fed4fe0yfdf19efb52781a05@mail.gmail.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: problem starting Hbase 0.20 with Katta on EC2 Thread-Index: AcoTq6DEaZHVB26mTpyZMY3J90gtFQABGwuw References: <4B94F7D3090A974E94A9BD23E57BB14302DDE112@corpdc-exch01.corp.digimine.com> <971821.72817.qm@web65503.mail.ac4.yahoo.com> <4B94F7D3090A974E94A9BD23E57BB14302DDE113@corpdc-exch01.corp.digimine.com> <2eef7bd70908021255j1fed4fe0yfdf19efb52781a05@mail.gmail.com> From: "Yair Even-Zohar" To: X-Brightmail-Tracker: AAAAAA== X-Virus-Checked: Checked by ClamAV on apache.org Nope I enabled the ports by running: ec2-authorize GROUPID -p 3888 ec2-authorize GROUPID -p 2888 ec2-authorize GROUPID -p 2181 but I'm getting the exact same connection error -----Original Message----- From: Vaibhav Puranik [mailto:vpuranik@gmail.com]=20 Sent: Sunday, August 02, 2009 10:56 PM To: hbase-user@hadoop.apache.org Subject: Re: problem starting Hbase 0.20 with Katta on EC2 He means the EC2 security group, not ZK security groups. EC2 comes with a concept of security groups. Every time you launch an EC2 instance you can make it part of one or more security groups. Ports on launched EC2 instances are not open by default unless you open them by configuring security groups. You can google for more information or read here - http://wiki.github.com/auser/poolparty/ec2-security-groups Regards, Vaibhav On Sun, Aug 2, 2009 at 12:49 PM, Yair Even-Zohar wrote: > What is ZK security group? (I know very little of zookeeper) > > I thought the following zookeeper props set these up > > = zookeeper.servers=3DdomU-12-31-39-06-29-91.compute-1.internal:2888:3888 > zookeeper.clientPort=3D2181 > > do I have to set them up in Hbase too (even though that's the default)? > > > -----Original Message----- > From: Andrew Purtell [mailto:apurtell@apache.org] > Sent: Sunday, August 02, 2009 10:13 PM > To: hbase-user@hadoop.apache.org > Subject: Re: problem starting Hbase 0.20 with Katta on EC2 > > Hi, > > Have you set up the security group for your instances to allow the > Zookeeper quorum peers to communicate with each other and clients? > > You need to allow all instances to communicate with each other on the > following ports: > > 2181: client > 2888: replication > 3888: leader election > > > The above are the defaults. All can be changed via various settings > in hbase-site.xml (see hbase-default.xml). > > - Andy > > > > ________________________________ > From: Yair Even-Zohar > To: hbase-user@hadoop.apache.org; katta-developer@lists.sourceforge.net > Sent: Sunday, August 2, 2009 11:57:40 AM > Subject: problem starting Hbase 0.20 with Katta on EC2 > > I have the following problem when trying to run hbase 0.20 on ec2. > > First, I start katta which in turn starts zookeeper with the following > properties (zookeeper.zk.properties): > > > > = zookeeper.servers=3DdomU-12-31-39-06-29-91.compute-1.internal:2888:3888 > > #zookeeper client timeout in milliseconds > > zookeeper.timeout=3D150000 > > #zookeeper tick time > > zookeeper.tick-time=3D60000 > > # zookeeper init time limit > > zookeeper.init-limit=3D5 > > # zookeeper sync limit > > zookeeper.sync-limit=3D2 > > # zookeeper folder where data are stored > > zookeeper.data-dir=3D/mnt/katta/data > > # zookeeper folder where log data are stored > > zookeeper.log-data-dir=3D/mnt/katta/logs > > # zookeeper client port > > zookeeper.clientPort=3D2181 > > > > I am running Hbase 0.20 RC1 with the following zk properties in > hbase-site.xml: > > > > hbase.cluster.distributed > > true > > > > > > > > hbase.zookeeper.quorum > > domU-12-31-39-06-29-91.compute-1.internal > > > > > > > > > > Unfortunately, I'm getting the following errors: > > > > > > 2009-08-02 14:32:09,381 INFO org.apache.zookeeper.ZooKeeper: Initiating > client connection, = host=3DdomU-12-31-39-06-29-91.compute-1.internal:2181 > sessionTimeout=3D30000 > watcher=3Dorg.apache.hadoop.hbase.regionserver.HRegionServer@120bf2c > > 2009-08-02 14:32:09,383 INFO org.apache.zookeeper.ClientCnxn: > zookeeper.disableAutoWatchReset is false > > 2009-08-02 14:32:09,415 INFO org.apache.zookeeper.ClientCnxn: Attempting > connection to server > domU-12-31-39-06-29-91.compute-1.internal/10.208.46.95:2181 > > 2009-08-02 14:32:09,424 WARN org.apache.zookeeper.ClientCnxn: Exception > closing session 0x0 to sun.nio.ch.SelectionKeyImpl@181ed9e > > java.net.ConnectException: Connection refused > > at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) > > at > sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:574) > > at > org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:885) > > 2009-08-02 14:32:09,431 WARN org.apache.zookeeper.ClientCnxn: Ignoring > exception during shutdown input > > java.nio.channels.ClosedChannelException > > at > sun.nio.ch.SocketChannelImpl.shutdownInput(SocketChannelImpl.java:638) > > at > sun.nio.ch.SocketAdaptor.shutdownInput(SocketAdaptor.java:360) > > at > org.apache.zookeeper.ClientCnxn$SendThread.cleanup(ClientCnxn.java:951) > > > > Looks like I have problem connecting to zookeeper but I have no clue > why. Server name is correct, client port is 2181 and user is root. > > Any help? > > > > Thanks > > -Yair > > > >