I'm getting the same results without hbase.regionserver.dns.interface
set and with it explicitly set to default
hbase-site.xml:
configuration
property
namehbase.rootdir/name
valuehdfs://sns12.cs.princeton.edu:8020/hbase/value
/property
property
namehbase.master/name
valuesns12-virt.CS.Princeton.EDU:6/value
/property
property
namehbase.cluster.distributed/name
valuetrue/value
/property
property
namehbase.zookeeper.quorum/name
valuesns12-virt.CS.Princeton.EDU,sns13-virt.CS.Princeton.EDU,sns14-virt.CS.Princeton.EDU/value
/property
/configuration
Ryan Rawson wrote:
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 dgarbu...@gmail.com wrote:
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 0.0.0.0:*
LISTEN
Ryan Rawson wrote:
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 dgarbu...@gmail.com
wrote:
Hi all,
I'm trying to set up hbase on a cluster where each machine has multiple
interfaces. Hdfs worked right away since I could just set the name node
to
listen on 0.0.0.0, but hbase region servers seem to pick one of the
interfaces at random, ignoring the hbase.regionserver.dns.interface
option.
Is the dns.interface setting supposed to make hbase bind to a specific
interface? Is there anything special I need to do to get this to work?
dmitri
