Arber, There are security policies with EC2, did you unblock port 60000 for your own IP address?
J-D On Tue, Mar 17, 2009 at 4:07 AM, Yabo-Arber Xu <[email protected]> wrote: > Hi all, > > I set up a small HBase cluster on EC2. It works fine internally if all the > applications are within EC2. It, however, does not work if i am trying run > shell or client program on a external host. I've been googling for a while, > and found there was similar issues raised before: > http://www.nabble.com/Hbase-on-EC2-and-issues-with-Amazon-NAT-Internal-Addresses-td21621367.html, > > > But it seems no solutions so far. I wonder whether anybody has made progress > on this issue. Any thoughts would be greatly appreciated! > > > Attached with my hbase-site.xml. I am running the master/region server all > on one instance for testing. > > <configuration> > <property> > <name>hbase.master</name> > <value>*domU-12-31-39-00-E0-96.compute-1.internal*:60000</value> //It > does not work even if i changed this the Amazon public IP > <description>The host and port that the HBase master runs at. > </description> > </property> > > <property> > <name>hbase.rootdir</name> > > <value>hdfs://domU-12-31-39-00-E0-96.compute-1.internal:54310/hbase</value> > <description>The directory shared by region servers. > </description> > </property> > </configuration> > > > Thanks for your attention, > Arber >
