Actually within 5 mins of sending out this puzzle, I found the answer...
In the machine's /etc/host, there wasn't an entry for the machine's IP address, only the loopback local host. When we added the entry in to those machines, everything went Ok. I didn't check the logs, but I bet that you are correct. Thanks! -Mike > Date: Tue, 1 Jun 2010 11:56:54 -0700 > Subject: Re: Weird problem on one of my clouds... > From: [email protected] > To: [email protected] > > On Tue, Jun 1, 2010 at 11:13 AM, Michael Segel > <[email protected]> wrote: > > Ok... when I try tools zk_dump I get the following: > > Region servers: > > - 127.0.0.1:60020 > > - 10.8.239.89:60020 > > - 127.0.0.1:60020 > > - 10.8.239.87:60020 > > - 10.8.239.95:60020 > > - 127.0.0.1:60020 > > - 10.8.239.93:60020 > > - 10.8.239.91:60020 > > - 127.0.0.1:60020 > > - 127.0.0.1:60020 > > - 127.0.0.1:60020 > > > > > > This doesn't make sense. > > Why would some of my region servers show up saying that they are local > > hosts? > > Because thats what its getting for its machine name. See the head of > HRegionServer around #242 where it does this to figure out the whoami: > > machineName = DNS.getDefaultHost( > conf.get("hbase.regionserver.dns.interface","default"), > conf.get("hbase.regionserver.dns.nameserver","default")); > > > All of the servers have the same set of configuration files. > > > If you look in the regionserver log, is it saying that its registered > on 127.0.0.1:60020? > > St.Ack _________________________________________________________________ The New Busy is not the old busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_3
