I would assume that cygwin is a non-unix compatible system - localhost is more or less assured to work on all unix system.
Thanks for the report, I hope more people will benefit from this. Guys, should we consider switching to IP? IP will always work, but obviously hostname can fail... -ryan On Mon, Sep 14, 2009 at 9:29 PM, Matt Corgan <[email protected]> wrote: > Hi All, > I was setting up hbase-0.20.0 in standalone mode on cygwin tonight and ran > across this exact problem from August 31st: > > http://www.mail-archive.com/[email protected]/msg05873.html > > I believe I fixed it by changing conf/hbase-default.xml from > > <property> > <name>hbase.zookeeper.quorum</name> > <value>*localhost*</value> > <description>Comma separated list of servers in the ZooKeeper Quorum. > For example, "host1.mydomain.com,host2.mydomain.com,host3.mydomain.com". > By default this is set to localhost for local and pseudo-distributed > modes > of operation. For a fully-distributed setup, this should be set to a > full > list of ZooKeeper quorum servers. If HBASE_MANAGES_ZK is set in > hbase-env.sh > this is the list of servers which we will start/stop ZooKeeper on. > </description> > </property> > > to > > <property> > <name>hbase.zookeeper.quorum</name> > <value>*127.0.0.1*</value> > <description>Comma separated list of servers in the ZooKeeper Quorum. > For example, "host1.mydomain.com,host2.mydomain.com,host3.mydomain.com". > By default this is set to localhost for local and pseudo-distributed > modes > of operation. For a fully-distributed setup, this should be set to a > full > list of ZooKeeper quorum servers. If HBASE_MANAGES_ZK is set in > hbase-env.sh > this is the list of servers which we will start/stop ZooKeeper on. > </description> > </property> > > I guess zookeeper doesn't understand localhost in cygwin or something. > Maybe the value could be changed by default or a note could be added to the > getting started guide. Everything else has gone smoothly so far. > > Matt >
