Hi, correct hbase configuration file (hbase.zookeeper.quorum needs to be set to 127.0.0.1)
thanks! hbase-site.xml : <?xml version="1.0"?> <?xml-stylesheet type="text/xsl" href="configuration.xsl"?> <!-- /** * Copyright 2009 The Apache Software Foundation * * Licensed to the Apache Software Foundation (ASF) under one * or more contributor license agreements. See the NOTICE file * distributed with this work for additional information * regarding copyright ownership. The ASF licenses this file * to you under the Apache License, Version 2.0 (the * "License"); you may not use this file except in compliance * with the License. You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an "AS IS" BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. */ --> <configuration> <property> <name>hbase.rootdir</name> <value>hdfs://localhost:9000/hbase</value> <description>The directory shared by region servers. </description> </property> <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> <property> <name>hbase.cluster.distributed</name> <value>false</value> <description>The mode the cluster will be in. Possible values are false: standalone and pseudo-distributed setups with managed Zookeeper true: fully-distributed with unmanaged Zookeeper Quorum (see hbase-env.sh) </description> </property> <property> <name>hbase.regionserver.class</name> <value>org.apache.hadoop.hbase.ipc.IndexedRegionInterface</value> </property> <property> <name>hbase.regionserver.impl</name> <value>org.apache.hadoop.hbase.regionserver.tableindexed.IndexedRegionServer</value> </property> </configuration> On Mon, Jan 18, 2010 at 7:51 PM, Andrew Milkowski <andrewmilkow...@gmail.com > wrote: > Hi stack > > Environment is cygwin (version 1.7), Windows 7 64-bit > > This was the only way I could manage to get hbase up (with a standalone > zookeeper server) , problem does not exist on Unix (Centos) but that is > expected also I am working to have complete installation > hadoop/hbase/zookeeper running on the Mac will be happy to follow up on > issues. > > As far as adding "workaround", absolutely (I tried just about anything, as > the original author of this issues, I have had no problems running > "self-managed" zookeeper on Windows 32-bit XP > > (fyi, I did not try to "force" IPv4 , but I did try change cygwin sshd and > ssh configuration files to use IPV4, no effect), > > btw, thanks for your great work, product (hadoop family) is phenomenal! > > cheers > > > Following are sequenced steps and configuration files used (IndexedRegion > server parameters is of course optional) > > Sequence of run: > > 1.start zookeeper (zkServer.sh start) (ping to check "live" status: > zkCli.sh -server 127.0.0.1:2181 > > 2. start hadoop > > 3. start hbase > > <configuration> > <property> > <name>hbase.rootdir</name> > <value>hdfs://localhost:9000/hbase</value> > <description>The directory shared by region servers. > </description> > </property> > <property> > <name>hbase.cluster.distributed</name> > <value>false</value> > <description>The mode the cluster will be in. Possible values are > false: standalone and pseudo-distributed setups with managed > Zookeeper > true: fully-distributed with unmanaged Zookeeper Quorum (see > hbase-env.sh) > </description> > </property> > > <property> > <name>hbase.regionserver.class</name> > <value>org.apache.hadoop.hbase.ipc.IndexedRegionInterface</value> > </property> > <property> > <name>hbase.regionserver.impl</name> > > <value>org.apache.hadoop.hbase.regionserver.tableindexed.IndexedRegionServer</value> > </property> > > </configuration> > > and zoo.cfg file > > # The number of milliseconds of each tick > tickTime=2000 > # The number of ticks that the initial > # synchronization phase can take > initLimit=10 > # The number of ticks that can pass between > # sending a request and getting an acknowledgement > syncLimit=5 > # the directory where the snapshot is stored. > dataDir=/opt/zookeeper/data > # the port at which the clients will connect > clientPort=2181 > > > > On Mon, Jan 18, 2010 at 5:58 PM, stack <st...@duboce.net> wrote: > >> Thank you Andrew for the below. You were running all in cygwin I take it? >> Should we update this document: >> http://hadoop.apache.org/hbase/docs/r0.20.2/cygwin.html? >> >> St.Ack >> >> On Mon, Jan 18, 2010 at 2:26 PM, Andrew Milkowski < >> andrewmilkow...@gmail.com >> > wrote: >> >> > Hi, >> > >> > Have a quick workaround to start hbase on 64-bit windows >> > >> > Launch standalone zookeeper (don't add regional servers in the zoo.cfg) >> and >> > keep hbase.cluster.distributed set to false >> > >> > Hbase was able to connect to zookeeper server (probably a failover due >> to >> > internal error in hbase itself, there is definitely something wrong in >> the >> > way hbase handles its own zookeeper initiation) >> > >> > (Zookeeper instructions are in the usual place: >> > http://hadoop.apache.org/zookeeper/docs/current/zookeeperStarted.html) >> > >> > Using hbase 0.20.2 and zookeeper 3.2 versions >> > >> > performed some tests with sample table I/O all looks fine., hopefully >> this >> > will keep you going until "self-managed" zookeeper in hbase is closely >> > looked at >> > >> > cheers >> > >> > >
