Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2EA23104A7 for ; Wed, 10 Jul 2013 15:48:06 +0000 (UTC) Received: (qmail 32556 invoked by uid 500); 10 Jul 2013 15:48:03 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 32286 invoked by uid 500); 10 Jul 2013 15:47:59 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 32269 invoked by uid 99); 10 Jul 2013 15:47:58 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Jul 2013 15:47:58 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of brian.jeltema@digitalenvoy.net designates 68.64.43.136 as permitted sender) Received: from [68.64.43.136] (HELO barracuda.digitalenvoy.net) (68.64.43.136) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 10 Jul 2013 15:47:53 +0000 X-ASG-Debug-ID: 1373471251-05f61154fb145a0001-ZI2oBf Received: from brian-jeltema.employees.digitalenvoy.net (norc-office.digitalenvoy.net [64.129.218.66]) by barracuda.digitalenvoy.net with ESMTP id URj2OVNoAj2nsYsL (version=TLSv1 cipher=AES128-SHA bits=128 verify=NO) for ; Wed, 10 Jul 2013 11:47:31 -0400 (EDT) X-Barracuda-Envelope-From: brian.jeltema@digitalenvoy.net X-Barracuda-Apparent-Source-IP: 64.129.218.66 X-ASG-Whitelist: Client Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Apple Message framework v1278) Subject: Re: ClusterId read in ZooKeeper is null From: Brian Jeltema X-ASG-Orig-Subj: Re: ClusterId read in ZooKeeper is null In-Reply-To: Date: Wed, 10 Jul 2013 11:47:30 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <3F603384-7632-4C2D-97CF-C1BCD210C944@digitalenvoy.net> To: user@hbase.apache.org X-Mailer: Apple Mail (2.1278) X-Barracuda-Connect: norc-office.digitalenvoy.net[64.129.218.66] X-Barracuda-Start-Time: 1373471251 X-Barracuda-Encrypted: AES128-SHA X-Barracuda-URL: http://barracuda.digitalenvoy.net:8000/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at digitalenvoy.net X-Barracuda-BRTS-Status: 1 X-Virus-Checked: Checked by ClamAV on apache.org As far as I can tell the HMaster process is running correctly. There are = no obvious problems in the logs. As suggested, I defined zookeeper.znode.parent in the client to match = the deployment, which did eliminate the warning about the null ClusterId. However, the client still hangs in = the same place. After some debugging, the client appears to be looking for a zookeeper = node named /hbase_unsecure/meta-region-server. =46rom the zookeeper cli (slightly edited): [zk: ] ls /hbase-unsecure returns [splitlog, online-snapshot, unassigned, root-region-server, rs, = table92, backup-masters, draining, table, master, shutdown, hbaseid] so meta-region-server node does not exist. As I read the code, the HBase = Master would have set that in a postOpenDeployTasks method, which apparently is not being called. At this point it's not clear to me what = else to look for. Brian On Jul 9, 2013, at 1:28 PM, Gary Helmling wrote: > Is the HMaster process running correctly on the cluster? Between the > missing cluster ID and meta region not being available, it looks like > HMaster may not have fully initialized. >=20 > Alternately, if HMaster is running correctly, did you override the = default > value for zookeeper.znode.parent in your cluster configuration, but = not set > this in your client code? >=20 >=20 > On Tue, Jul 9, 2013 at 10:05 AM, Brian Jeltema < > brian.jeltema@digitalenvoy.net> wrote: >=20 >> I'm new to HBase, and need a little guidance. I've set up a 6-node >> cluster, with 3 nodes >> running the ZooKeeper server. The database seems to be working from = the >> hbase shell; I can create tables, insert, >> scan, etc. >>=20 >> But when I try to perform operations in a Java app, I hang at: >>=20 >> 13/07/09 12:40:34 INFO zookeeper.ZooKeeper: Initiating client = connection, >> connectString=3Dcas-2:2181,cas-1:2181,cas-3:2181 sessionTimeout=3D90000= >> watcher=3Dhconnection-0x6833f0de >> 13/07/09 12:40:34 INFO zookeeper.RecoverableZooKeeper: Process >> identifier=3Dhconnection-0x6833f0de connecting to ZooKeeper >> ensemble=3Dcas-2:2181,cas-1:2181,cas-3:2181 >> 13/07/09 12:40:34 INFO zookeeper.ClientCnxn: Opening socket = connection to >> server cas-1/10.4.0.1:2181. Will not attempt to authenticate using = SASL >> (Unable to locate a login configuration) >> 13/07/09 12:40:34 INFO zookeeper.ClientCnxn: Socket connection = established >> to cas-1/10.4.0.1:2181, initiating session >> 13/07/09 12:40:34 INFO zookeeper.ClientCnxn: Session establishment >> complete on server cas-1/10.4.0.1:2181, sessionid =3D = 0x13fa5b5096e001f, >> negotiated timeout =3D 40000 >> 13/07/09 12:40:34 INFO client.ZooKeeperRegistry: ClusterId read in >> ZooKeeper is null >>=20 >> The Java code is nothing more than: >>=20 >> Configuration hConf =3D HBaseConfiguration.create(); >> hConf.set("hbase.zookeeper.quorum", "cas-1,cas-2,cas-3"); >> hConf.set("hbase.zookeeper.property.clientPort", "2181"); >> HTable hTable =3D new HTable(hConf, "tablename"); >>=20 >> a thread dump shows the app blocked: >>=20 >> "main" prio=3D10 tid=3D0x00007f1424009000 nid=3D0x2976 waiting on = condition >> [0x00007f142a0c3000] >> java.lang.Thread.State: TIMED_WAITING (sleeping) >> at java.lang.Thread.sleep(Native Method) >> at >> = org.apache.hadoop.hbase.zookeeper.ZKUtil.blockUntilAvailable(ZKUtil.java:1= 772) >> at >> = org.apache.hadoop.hbase.zookeeper.MetaRegionTracker.blockUntilAvailable(Me= taRegionTracker.java:175) >> at >> = org.apache.hadoop.hbase.client.ZooKeeperRegistry.getMetaRegionLocation(Zoo= KeeperRegistry.java:58) >> at >> = org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementatio= n.locateRegion(HConnectionManager.java:806) >> at >> = org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementatio= n.locateRegionInMeta(HConnectionManager.java:896) >> at >> = org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementatio= n.locateRegion(HConnectionManager.java:809) >> at >> = org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementatio= n.locateRegion(HConnectionManager.java:778) >> at >> org.apache.hadoop.hbase.client.HTable.finishSetup(HTable.java:245) >> at = org.apache.hadoop.hbase.client.HTable.(HTable.java:186) >> at = org.apache.hadoop.hbase.client.HTable.(HTable.java:147) >>=20 >> Any suggestions as to the cause? >>=20 >> TIA >>=20 >> Brian