Wait, I think there's been some confusion: the master resolves itself to 127.0.1.1, not 127.0.0.1
I've looked at the HMaster logs (http://pastebin.com/m4ecf071e) and it says that in fact what the region servers are reading is true: the master is running as "hadoop 127.0.1.1." A few interesting things to note are: the ROOT region is not set, and the /hbase/rs node is completely empty. Is this still the matter of a host-name issue? I notice there are dns properties for all aspects of hbase, should I tamper with them? -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jean-Daniel Cryans Sent: Tuesday, November 24, 2009 11:40 AM To: [email protected] Subject: Re: Way to Specify HBase master? It seems to be the same problems isn't it? The master resolves itself to 127.0.0.1 and all region servers, when communicating with Zookeeper, read the master's znode with the local address but since there isn't a master there, it can't connect. The reason why you can't specify a master is because HBase is dynamically multi-master e.g. you can start 100 masters (one is elected), kill some backups, get new ones, etc. So each node, master and region server, in HBase has to be able to publish its own address. Like Stack said, playing with your hosts file should be enough, just make sure that the hadoop config is still sane (and try to see why it fails if so). If you have a DNS server, you can also set the following values: <property> <name>hbase.zookeeper.dns.interface</name> <value>default</value> <description>The name of the Network Interface from which a ZooKeeper server should report its IP address. </description> </property> <property> <name>hbase.zookeeper.dns.nameserver</name> <value>default</value> <description>The host name or IP address of the name server (DNS) which a ZooKeeper server should use to determine the host name used by the master for communication and display purposes. </description> </property> J-D On Tue, Nov 24, 2009 at 8:28 AM, Mark Vigeant <[email protected]> wrote: > So I tried to change the hostname and it messed up my hadoop cluster... it > appears that everything else runs fine on the host hadoop 127.0.1.1 > > I'll change strategies here: my regionservers see the host and try to connect > to it, but the connection is refused. Does anyone have any ideas on how I can > change that? > > Here's a snippet of the log from my regionserver: > http://pastebin.com/m6bbcb432 > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of stack > Sent: Monday, November 23, 2009 5:28 PM > To: [email protected] > Subject: Re: Way to Specify HBase master? > > This sounds like basic networking issue where host lookup is finding > 127.0.0.1. Can you get someone to help you setup your networking on your > machine. Else play w/ your /etc/hosts. Seems like your host name resolves > to 127.0.0.1. > St.Ack > > On Mon, Nov 23, 2009 at 12:31 PM, Mark Vigeant <[email protected] >> wrote: > >> I'm trying to play around with HBase but it hasn't been working for me. >> From the look of the logs, it appears that the master is running on >> 127.0.1.1 instead of my machine (fry) and so all of the regionservers start, >> but the logs say they cannot connect to the master. From the master logs, it >> thinks there are 0 regionservers and thus won't do anything for me. I'm >> using HBase 20.2. How can I set the IP address of the master machine? >> >> Mark Vigeant >> RiskMetrics Group, Inc. >> >> This email message and any attachments are for the sole use of the intended >> recipients and may contain proprietary and/or confidential information which >> may be privileged or otherwise protected from disclosure. Any unauthorized >> review, use, disclosure or distribution is prohibited. If you are not an >> intended recipient, please contact the sender by reply email and destroy the >> original message and any copies of the message as well as any attachments to >> the original message. >> > > This email message and any attachments are for the sole use of the intended > recipients and may contain proprietary and/or confidential information which > may be privileged or otherwise protected from disclosure. Any unauthorized > review, use, disclosure or distribution is prohibited. If you are not an > intended recipient, please contact the sender by reply email and destroy the > original message and any copies of the message as well as any attachments to > the original message. > This email message and any attachments are for the sole use of the intended recipients and may contain proprietary and/or confidential information which may be privileged or otherwise protected from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy the original message and any copies of the message as well as any attachments to the original message.
