[ 
https://issues.apache.org/jira/browse/HBASE-30502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18135543#comment-18135543
 ] 

Hudson commented on HBASE-30502:
--------------------------------

Results for branch branch-3.0
        [build #41 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3.0/41/]: 
(x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3.0/41/General_20Nightly_20Build_20Report/]








(x) {color:red}-1 jdk17 hadoop3 checks{color}
-- For more information [see jdk17 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3.0/41/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk21 hadoop3 checks{color}
-- For more information [see jdk21 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3.0/41/JDK21_20Nightly_20Build_20Report_20_28Hadoop3_29/]


> ProcedureFutureUtil.suspendIfNecessary may skip wakingup a procedure if the 
> future is completed in PEWorker thread
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-30502
>                 URL: https://issues.apache.org/jira/browse/HBASE-30502
>             Project: HBase
>          Issue Type: Improvement
>          Components: proc-v2
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.0.0-alpha-1, 3.1.0, 3.0.1
>
>
> The current implementation assumes that the future will not be completed in 
> PEWorker, so we check whether the future callback is called in the same 
> thread, if so, we think the future is completed before suspending and give up 
> waking up.
> When implementing HBASE-30402, a procedure may hold a future which is 
> completed by another procedure, in this way, the above assumption is 
> incorrent, so we need to change the logic before landing the changes in 
> HBASE-30402.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to