On Thu, Apr 29, 2010 at 4:39 AM, Michael Segel
wrote:
> The problem with Hadoop and of course HBase is that they determine their own
> IP network based on the machine's actual name, so that even if you have
> multiple interfaces, the nodes will choose the interface that matches the
> machine na
37 -0400
> From: dgarbu...@gmail.com
> To: hbase-user@hadoop.apache.org
> CC: jterr...@cs.princeton.edu
> Subject: Re: hbase with multiple interfaces
>
> I'm getting the same results without hbase.regionserver.dns.interface
> set and with it explicitly set
Ah yes I was reading my netstat wrong, we have the same deal.
So hbase will use hostname to determine which IP you wish to
communicate on, then use that to bind and report to the master.
The setting hbase.regionserver.dns.interface
should work the same as the similar setting in Hadoop. If i
I'm getting the same results without hbase.regionserver.dns.interface
set and with it explicitly set to "default"
hbase-site.xml:
hbase.rootdir
hdfs://sns12.cs.princeton.edu:8020/hbase
hbase.master
sns12-virt.CS.Princeton.EDU:6
hbase.c
If you are using the "hbase.regionserver.dns.interface" option this is
what would happen - binding to a specific interface.
What is your config looking like?
On Wed, Apr 28, 2010 at 4:54 PM, dmitri garbuzov wrote:
> Doesn't look like it's binding to 0.0.0.0
>
> sudo lsof -i :60020
> COMMAND PI
Doesn't look like it's binding to 0.0.0.0
sudo lsof -i :60020
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
java22530 hadoop 37u IPv4 81808593 0t0 TCP
sns12-virt.CS.Princeton.EDU:60020 (LISTEN)
sudo netstat -an | grep 60020
tcp0 0 128.112.7.112:60020
HBase does bind to 0.0.0.0:60020. It uses the hostname to report this
to META and that is how other people find the region servers.
Are you not seeing this?
On Wed, Apr 28, 2010 at 4:15 PM, dmitri garbuzov wrote:
> Hi all,
>
> I'm trying to set up hbase on a cluster where each machine has multi
