[
https://issues.apache.org/jira/browse/HBASE-20847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16539462#comment-16539462
]
Duo Zhang commented on HBASE-20847:
-----------------------------------
The problem is that, in ProcedureExecutor will schedule the sub procedures
before releasing the lock(if needed, i.e, holdLock is false), this breaks our
assumption above, where we assume that the the parent procedure will not
release the lock until the sub procedures finishes...
Anyway, I think remove the assumption is still fine, as in Java, you are free
release the WriteLock before releasing the readLock. Let me change the code.
> The parent procedure of RegionTransitionProcedure may not have the table lock
> -----------------------------------------------------------------------------
>
> Key: HBASE-20847
> URL: https://issues.apache.org/jira/browse/HBASE-20847
> Project: HBase
> Issue Type: Sub-task
> Components: proc-v2, Region Assignment
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Attachments: HBASE-20847-v1.patch, HBASE-20847-v2.patch,
> HBASE-20847.patch
>
>
> For example, SCP can also schedule AssignProcedure and obviously it will not
> hold the table lock.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
