some remote client.
- Andy
From: Jean-Daniel Cryans
To: hbase-user@hadoop.apache.org
Sent: Monday, September 14, 2009 11:36:03 AM
Subject: Re: Region Server on EC2
Oh no sorry I misled you, this is another problem. You cannot use the
external addresses
Well we assigned and elastic IP.
Well I running remotely to test. We will have apps on other ec2 virtual
machines
I know the external can change if it restarts, but we are willing to
reconfigure if that is case, but I still would like to be able to access
hbase from outside.
Ananth T Sarathy
O
Oh no sorry I misled you, this is another problem. You cannot use the
external addresses because they change so HBase _has_ to use the
internal addresses or you could have very weird problems.
So there is another question: why do you want to connect to an EC2
cluster remotely? Any client connectio
Hmm thanks,
Where exactly am I supposed to find the nameserver? It's not the external
dns for the box right?
Ananth T Sarathy
On Mon, Sep 14, 2009 at 1:35 PM, Jean-Daniel Cryans wrote:
> You have to set hbase.regionserver.dns.interface and
> hbase.regionserver.dns.nameserver with valid values.
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
wrote:
> When we try to connect to
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
