[
https://issues.apache.org/jira/browse/HBASE-27311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17583875#comment-17583875
]
Hudson commented on HBASE-27311:
--------------------------------
Results for branch master
[build #664 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/664/]:
(/) *{color:green}+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/master/664/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/664/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/664/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> The implementation of syncReplicationPeerLock is incomplete
> -----------------------------------------------------------
>
> Key: HBASE-27311
> URL: https://issues.apache.org/jira/browse/HBASE-27311
> Project: HBase
> Issue Type: Bug
> Components: proc-v2, Replication
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 3.0.0-alpha-4
>
>
> We also need to restore the state after loading the procedure after master
> restarts.
> And we'd better not just let the PEWorker hand there on waiting the
> semaphore, better to let the procedure suspend and retry later.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
