[
https://issues.apache.org/jira/browse/HBASE-28830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882578#comment-17882578
]
Duo Zhang commented on HBASE-28830:
-----------------------------------
OK, so the problem is that, you need to deal with two tables so you need to
take two locks while executing?
I think it is easy to introduce dead lock? Better to just submit the procedure
directly instead of adding it as a subprocedure?
> when a procedure on a table executed as a child procedure, further table
> procedure operations on that table are blocked forever waiting to acquire the
> table procedure lock
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-28830
> URL: https://issues.apache.org/jira/browse/HBASE-28830
> Project: HBase
> Issue Type: Bug
> Components: proc-v2
> Affects Versions: 3.0.0-beta-1, 2.5.10
> Reporter: Chandra Sekhar K
> Assignee: Chandra Sekhar K
> Priority: Critical
> Labels: pull-request-available
> Attachments: CustomCoProcessor.java
>
>
> when a procedure on a table executed as a child procedure, furthur table
> procedure operations on that table are blocked forever waiting to aquire the
> table procedure lock .
> This issue occur due to not clearing of table lock for the table procedures
> submitted as child procedures after the changes in HBASE-28683,
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
