[
https://issues.apache.org/jira/browse/HBASE-19976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16361619#comment-16361619
]
stack commented on HBASE-19976:
-------------------------------
[~Apache9] RecoverMetaProcedure is relatively new. It is neither a
TableProcedure nor a ServerProcedure (oversight?). Could this be the problem?
If it were a ServerProcedure, it would be run ahead of everyone?
> Dead lock if the worker threads in procedure executor are exhausted
> -------------------------------------------------------------------
>
> Key: HBASE-19976
> URL: https://issues.apache.org/jira/browse/HBASE-19976
> Project: HBase
> Issue Type: Bug
> Reporter: Duo Zhang
> Assignee: stack
> Priority: Critical
>
> See the comments in HBASE-19554. If all the worker threads are stuck in
> AssignProcdure since meta region is offline, then the RecoverMetaProcedure
> can not be executed and cause dead lock.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
