hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Duo Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-19976) Dead lock if the worker threads in procedure executor are exhausted
Date Tue, 13 Feb 2018 01:57:00 GMT

    [ https://issues.apache.org/jira/browse/HBASE-19976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16361705#comment-16361705
] 

Duo Zhang commented on HBASE-19976:
-----------------------------------

I think yield is not a easy way for the developers, the retry is in the HTable implementation...

And as I said above, the ServerCrashProcedure which carries meta should be high priority and
it is in the server queue, the RecoverMeta should also be high priority but it is in the table
queue...

> 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)

Mime
View raw message