Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase, mail # user - [Stand alone - distributed mode] HBase master isn't initializing completely
techbuddy
2012-10-11, 21:11
techbuddy
2012-10-12, 07:27
Suraj Varma
2012-10-12, 07:47
Copy link to this message
-
答复: [Stand alone - distributed mode] HBase master isn't initializing completely
谢良 2012-10-12, 04:00
Is there any WARNING/ERROR in HDFS logfile ?
Please ensure zk&hdfs are in healthy status firstly
Could you provide your hbse version, it'll be great:)
________________________________________
发件人: techbuddy [[EMAIL PROTECTED]]
发送时间: 2012年10月12日 5:11
收件人: [EMAIL PROTECTED]
主题: [Stand alone - distributed mode] HBase master isn't initializing completely

Hi,

I've a standalone Hbase cluster configured in a distributed mode (i.e. the
ZK, Master and the RegServer all running in separate JVMs on the same host).

The HBase master doesn't seem to be intializing successfully. This has
started happening since I encountered the stop-hbase script going into an
indefinite loop followed by a forced kill of the three Hbase processes
(Zk,Master and Region server). I did manually kill these processes couple of
times earlier too, but the Hbase master never stalled partially initialized.
I have also removed the zookeeper and the hbase/test/hbase folders in an
effort to clean things up before triggering the start-hbase script.

Symptoms

1. The create table command on the Hbase shell errors out with a
PleaseHoldException (Master in initializing)

2. On the Admin UI, the regon server lists only the ROOT and the single META
regions. It doesn't list one single region of the user tables. However ,a
list command on the shell indeed lists all the user tables (that were
created in the past)

3. On the Master logs, I see the following locate region failures and
retries on the META table

2012-10-11 14:09:03,970 DEBUG
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation:
locateRegionInMeta parentTable=-ROOT-,
metaLocation={region=-ROOT-,,0.70236052,
hostname=materialstranger.corp.XXX.com, port=60020}, attempt=77 of 100
failed; retrying after sleep of 32172 because: Connection refused
2012-10-11 14:09:03,971 DEBUG
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation:
Looked up root region location,
connection=org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation@1bbbafc;
serverName=materialstranger.corp.XXX.com,60020,1349987514876
2012-10-11 14:09:36,197 DEBUG
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation:
Looked up root region location,
connection=org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation@1bbbafc;
serverName=materialstranger.corp.XXX.com,60020,1349987514876
2012-10-11 14:09:36,197 DEBUG
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation:
locateRegionInMeta parentTable=-ROOT-,
metaLocation={region=-ROOT-,,0.70236052,
hostname=materialstranger.corp.XXX.com, port=60020}, attempt=78 of 100
failed; retrying after sleep of 32275 because: Connection refused
2012-10-11 14:09:36,198 DEBUG
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation:
Looked up root region location,
connection=org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation@1bbbafc;
serverName=materialstranger.corp.XXX.com,60020,1349987514876
Any pointers on how to restore the cluster to a clean ,working state would
be highly appreciated.

-SB
--
View this message in context: http://apache-hbase.679495.n3.nabble.com/Stand-alone-distributed-mode-HBase-master-isn-t-initializing-completely-tp4032869.html
Sent from the HBase User mailing list archive at Nabble.com.