[
https://issues.apache.org/jira/browse/HBASE-20173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16495874#comment-16495874
]
stack commented on HBASE-20173:
-------------------------------
This patch failed to catch a scenario where we'd lock up server crash
processing when a concurrent move procedure going on; see HBASE-20634.
> [AMv2] DisableTableProcedure concurrent to ServerCrashProcedure can deadlock
> ----------------------------------------------------------------------------
>
> Key: HBASE-20173
> URL: https://issues.apache.org/jira/browse/HBASE-20173
> Project: HBase
> Issue Type: Sub-task
> Components: amv2
> Reporter: stack
> Assignee: stack
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: HBASE-20173.branch-2.001.patch,
> HBASE-20173.branch-2.002.patch
>
>
> See 'Deadlock' scenario in parent issue. Doing as focused subtask since
> parent has a few things going on in it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
