Hey all, I figured out my issue finally. Here's a brief summary:
ISSUE: NoNode exception when creating a table through the shell - HBase Master crashes. hbase(main):011:0> create 'test_t', 'data' ERROR: java.io.IOException: java.io.IOException: java.lang.InterruptedException >From ZK Server Log: 2011-04-14 17:37:00,907 - INFO [ProcessThread:-1:PrepRequestProcessor@407] - Got user-level KeeperException when processing sessionid:0x12f569514a30000 type:delete cxid:0xc6 zxid:0xfffffffffffffffe txntype:unknown reqpath:n/a Error Path:/hbase/table/test_t Error:KeeperErrorCode = NoNode for /hbase/table/test_t Master server starts assigning regions in round robin fashion, but fails to assign to certain nodes. From master server log: 2011-04-14 17:37:00,908 WARN org.apache.hadoop.hbase.zookeeper.ZKTable: Moving table test_t state to enabled but was already enabled 2011-04-14 17:37:01,404 FATAL org.apache.hadoop.hbase.master.HMaster: Failed assignment of regions to serverName=sv006.my.domain.com,60020,1302827775531 CAUSE: In this case the master server had a fully specified hostname for each regionserver node. However, after adding a few new regionserver nodes, I left out the hostname definitions in the regionservers /etc/hosts file. In other words, the regionserver hosts file only had: 127.0.0.1 localhost.localdomain localhost I added fully specified hostnames in each region server's hosts file, which did the trick: 127.0.0.1 localhost.localdomain localhost <region.server.ip> my.region.server.domain region1 <master.server.ip> my.master.server.domain master Cheers, Jon On Fri, Apr 15, 2011 at 11:22 AM, Stack <[email protected]> wrote: > Good. Mind updating list so others benefit from your findings? I will add > an FAQ on proxy based off your list mail. Thanks. > > > > On Apr 15, 2011, at 11:14, Jonathan Bender <[email protected]> > wrote: > > > Just figured it out. I recently added some new Regionservers which had > their Hostnames configured improperly. I just added every hostname / IP to > the hosts file on each node to make it work again. > > > > Turns out it had nothing to do with LZO stuff, which was throwing me off > big time. > > > > Many thanks for the help. >
