Could it be due to security groups on EC2 - are your EC2 ports open for HBase connections?
Thanks and Regards, Sonal www.meghsoft.com http://in.linkedin.com/in/sonalgoyal On Fri, Jun 18, 2010 at 11:11 PM, Oliver Meyn <[email protected]> wrote: > Hi All, > > Is there a trick to running a single, standalone hbase on a single ec2 > instance? I have hbase running locally as standalone and again on a > separate testing machine in the office and my java client can talk to them > both just fine. If I setup an ec2 instance with the same configs as the > testing machine my client can't connect - meaning it attempts to connect and > then hangs with no further logging. If I turn off hbase on the ec2 instance > and try to connect I get the usual ConnectionException: Connection refused. > When hbase is running I can connect to the admin console on :60010 just > fine, and I've confirmed that there are no blocked ports facing me. > > I suspect this has something to with ip addresses, specifically the elastic > ip story of the external ip not being known to the instance (where it > instead has a 10.x.x.x address), but fiddling hasn't helped. > > Any thoughts? > > Thanks, > Oliver > >
