[
https://issues.apache.org/jira/browse/HBASE-14943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15045906#comment-15045906
]
Ashu Pachauri commented on HBASE-14943:
---------------------------------------
v0 looks okay. But, in general, I would refrain from using more than one lock
at a point where you take reach by multiple code paths. This is just adding
more locking :)
> Deadlock in WALProcedureStore
> -----------------------------
>
> Key: HBASE-14943
> URL: https://issues.apache.org/jira/browse/HBASE-14943
> Project: HBase
> Issue Type: Bug
> Components: proc-v2
> Affects Versions: 2.0.0, 1.2.0, 1.2.1
> Reporter: Ashu Pachauri
> Assignee: Ashu Pachauri
> Priority: Blocker
> Attachments: HBASE-14943-v0.patch, deadlock-jstack.out
>
>
> Found deadlock in WALProcedureStore between the WALProcedureSyncThread and
> WALProcedureStore#update/delete/insert API which is used by the
> ProcedureExecutor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
