Keith, This virtual Ubuntu server is for development, not for production, right?
If so, try editing "/etc/hosts" of the Ubuntu server, so that it can resolve the correct IP (192.168.1.19) from its hostname. First two entries of /etc/hosts should like this: 127.0.0.1 localhost 127.0.1.1 your-host-name ... So replace 127.0.1.1 on the second line with 192.168.1.19. You shouldn't have to restart your server, but HBase. Please note that when you deploy production servers, you'll definitely need DNS entries for them. Thanks, -- Tatsuya Kawano (Mr.) Tokyo, Japan On Fri, Oct 9, 2009 at 8:46 AM, Keith Thomas <[email protected]> wrote: > > Thank you Barney Frank, your detailed notes were very helpful in confirming I > was doing things correctly already on the client. I did a lot of tracing > through the HBase code and concluded that the problem lay with my server. > > It looks like 0.20.0 has all sorts of DNS config entries and by default in > my setup, the address of my one server - running peudo distributed hbase and > hadoop for development purposes - resolves to 127.0.1.1 all the time. My > client gets back all sorts of addressing details from the server (from > zookeeper presumably) telling my client things are running on 127.0.1.1, > which of course they are not. > > I think my question now boils down to how can I configure Zookeeper so it > will return the address of the virtual machine it is running on > automatically, regardless of whether my laptop is connected to a network or > running disconnected on on a plane. > > To a newbie like myself he pre-0.20.0 type functionality (e..g. > 'hbase.master') seems to be more likely to meet my needs than a DNS based > solution, but what do I know :-)
