Everything seems to be working fine. You just need to run "hbase shell" as root - I guess we have some environment or file permissions issues.
Check the install / configure scripts for CDH for more info about where config files are located. Cheers, -- Andrei Savu On Tue, Oct 25, 2011 at 8:53 PM, Amandeep Khurana <[email protected]> wrote: > Just spun up a cluster using the 0.6 release. This one has zoo.cfg > configured incorectly: > > On starting HBase shell, I see: > 11/10/25 17:48:23 FATAL zookeeper.ZKConfig: The server in zoo.cfg cannot be > set to localhost in a fully-distributed setup because it won't be reachable. > See "Getting Started" for more information. > > hbase-site.xml has the quorum correctly configured but zoo.cfg on the HBase > master has localhost in the server list: > server.0=localhost:2888:3888 > > -ak > > > On Tue, Oct 25, 2011 at 10:32 AM, Amandeep Khurana <[email protected]>wrote: > >> Hi >> >> I'm trying to spin up an HBase cluster using the following recipe: >> >> whirr.cluster-name=hbase-1 >> whirr.instance-templates=1 zookeeper,1 >> hadoop-namenode+hadoop-jobtracker+hbase-master,3 >> hadoop-datanode+hadoop-tasktracker+hbase-regionserver >> hbase-site.dfs.replication=1 >> whirr.zookeeper.install-function=install_cdh_zookeeper >> whirr.zookeeper.configure-function=configure_cdh_zookeeper >> whirr.hadoop.install-function=install_cdh_hadoop >> whirr.hadoop.configure-function=configure_cdh_hadoop >> whirr.hbase.install-function=install_cdh_hbase >> whirr.hbase.configure-function=configure_cdh_hbase >> whirr.provider=aws-ec2 >> whirr.identity=${env:AWS_ACCESS_KEY_ID} >> whirr.credential=${env:AWS_SECRET_ACCESS_KEY} >> whirr.hardware-id=cc1.4xlarge >> whirr.image-id=us-east-1/ami-1cad5275 >> whirr.location-id=us-east-1 >> whirr.private-key-file=${sys:user.home}/.ssh/whirr >> whirr.public-key-file=${whirr.private-key-file}.pub >> #hbase-env.HBASE_MASTER_OPTS=-Xms1000m -Xmx1000m -Xmn256m >> -XX:+UseConcMarkSweepGC -XX:+AggressiveOpts -verbose:gc -XX:+PrintGCDetails >> -XX:+PrintGCTimeStamps -Xloggc:/data/hbase/logs/hbase-master-gc.log >> #hbase-env.HBASE_REGIONSERVER_OPTS=-Xms2000m -Xmx2000m -Xmn256m >> -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=88 >> -XX:+AggressiveOpts -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps >> -Xloggc:/data/hbase/logs/hbase-regionserver-gc.log >> >> The zookeeper quorum property in hbase-site.xml gets configured to >> localhost across the cluster rather than the server running zk. Any >> pointers/tips? >> >> -ak >> > >
