[
https://issues.apache.org/jira/browse/HBASE-27905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17728976#comment-17728976
]
Duo Zhang commented on HBASE-27905:
-----------------------------------
Better have a design doc first. The mechanism of the procedure scheduler is
very complicated, we need to be careful if we want to change its behavior.
> Directly schedule procedures that do not need to acquire locks
> --------------------------------------------------------------
>
> Key: HBASE-27905
> URL: https://issues.apache.org/jira/browse/HBASE-27905
> Project: HBase
> Issue Type: Improvement
> Components: proc-v2
> Affects Versions: 3.0.0-alpha-3
> Reporter: ruanhui
> Assignee: ruanhui
> Priority: Minor
> Fix For: 3.0.0-alpha-4
>
>
> Currently, in the procedure scheduler, we will not schedule any other
> procedures for a given queue if a procedure has held the exclusive lock, even
> if a procedure does not require any locks. For such procedures that do not
> require locks, we prefer that they can be executed directly without waiting
> until the procedure that held the exclusive lock is executed before starting
> to schedule execution. Otherwise, if the procedure holding the exclusive lock
> is stuck, the procedure that does not need the lock will also wait forever.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
