[
https://issues.apache.org/jira/browse/HBASE-12035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14318987#comment-14318987
]
Enis Soztutar commented on HBASE-12035:
---------------------------------------
[~octo47]
I was starting a local cluster today, and run into an issue where master will
not come up waiting for initialization. The stack trace is below. I think it
may be due to the fact that meta is not assigned yet before this state. But I
have not dig deeper.
{code}
Thread 82 (localhost:58722.activeMasterManager):
State: TIMED_WAITING
Blocked count: 43
Waited count: 783
Stack:
java.lang.Object.wait(Native Method)
org.apache.hadoop.hbase.client.AsyncProcess.waitForMaximumCurrentTasks(AsyncProcess.java:1656)
org.apache.hadoop.hbase.client.AsyncProcess.waitForAllPreviousOpsAndReset(AsyncProcess.java:1685)
org.apache.hadoop.hbase.client.BufferedMutatorImpl.backgroundFlushCommits(BufferedMutatorImpl.java:208)
org.apache.hadoop.hbase.client.BufferedMutatorImpl.flush(BufferedMutatorImpl.java:183)
org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:1395)
org.apache.hadoop.hbase.client.HTable.put(HTable.java:1007)
org.apache.hadoop.hbase.MetaTableAccessor.put(MetaTableAccessor.java:1116)
org.apache.hadoop.hbase.MetaTableAccessor.putToMetaTable(MetaTableAccessor.java:1106)
org.apache.hadoop.hbase.MetaTableAccessor.updateTableState(MetaTableAccessor.java:1429)
org.apache.hadoop.hbase.MetaTableAccessor.updateTableState(MetaTableAccessor.java:941)
org.apache.hadoop.hbase.master.TableStateManager.udpateMetaState(TableStateManager.java:181)
org.apache.hadoop.hbase.master.TableStateManager.setTableState(TableStateManager.java:68)
org.apache.hadoop.hbase.master.HMaster.initializeZKBasedSystemTrackers(HMaster.java:573)
org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:640)
org.apache.hadoop.hbase.master.HMaster.access$500(HMaster.java:170)
org.apache.hadoop.hbase.master.HMaster$1.run(HMaster.java:1462)
java.lang.Thread.run(Thread.java:745)
{code}
> Keep table state in META
> ------------------------
>
> Key: HBASE-12035
> URL: https://issues.apache.org/jira/browse/HBASE-12035
> Project: HBase
> Issue Type: Improvement
> Components: Client, master
> Affects Versions: 2.0.0
> Reporter: Enis Soztutar
> Assignee: Andrey Stepachev
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: 12035v2.txt, HBASE-12035 (1) (1).patch, HBASE-12035 (1)
> (1).patch, HBASE-12035 (1).patch, HBASE-12035 (2).patch, HBASE-12035
> (2).patch, HBASE-12035.patch, HBASE-12035.patch, HBASE-12035.patch,
> HBASE-12035.patch, HBASE-12035.patch, HBASE-12035.patch, HBASE-12035.patch,
> HBASE-12035.patch, HBASE-12035.patch, HBASE-12035.patch, HBASE-12035.patch,
> HBASE-12035.patch, HBASE-12035.patch, HBASE-12035.patch, HBASE-12035.patch,
> HBASE-12035.patch, HBASE-12035.patch
>
>
> HBASE-7767 moved table enabled|disabled state to be kept in hdfs instead of
> zookeeper. isTableDisabled() which is used in
> HConnectionImplementation.relocateRegion() now became a master RPC call
> rather than a zookeeper client call. Since we do relocateRegion() calls
> everytime we want to relocate a region (region moved, RS down, etc) this
> implies that when the master is down, the some of the clients for uncached
> regions will be affected.
> See HBASE-7767 and HBASE-11974 for some more background.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
