You have to set hbase.regionserver.dns.interface and hbase.regionserver.dns.nameserver with valid values. The interface will probably be something like "eth0" and the nameserver is the one provided by EC2.
J-D On Mon, Sep 14, 2009 at 1:31 PM, Ananth T. Sarathy <[email protected]> wrote: > When we try to connect to hbase running on an ec2 server from a machine > outside ec2, the regionserver on port 60020 is trying to connect to the > internal ip address rather than the external dns > > i feel it's the same issue as this > > http://issues.apache.org/jira/browse/HBASE-1279 > > > but my client keeps getting > > > 09/09/14 13:31:16 INFO ipc.HBaseClass: Retrying connect to server: / > 10.244.150.243:60020. Already tried 26 time(s). > 09/09/14 13:31:37 INFO ipc.HBaseClass: Retrying connect to server: / > 10.244.150.243:60020. Already tried 27 time(s). > > > > hbase-site.xml > > > <name>hbase.master</name> > <value>ec2externaldns:60000</value> > <description>The host and port that the HBase master runs at. > A value of 'local' runs the master and a regionserver in > a single process. > </description> > </property> > > > <property> > <name>hbase.regionserver</name> > <value>ec2externaldns:60020</value> > <description>The host and port a HBase region server runs at. > </description> > </property> > > <property> > <name>hbase.regionserver.dns.interface</name> > <value>0.0.0.0</value> > <description>Name of the network interface which a regionserver > should use to determine it's "real" IP address. This lookup > prevents strings like "localhost" and "127.0.0.1" from being > reported back to the master. > </description> > </property> > > Ananth T Sarathy >
