[
https://issues.apache.org/jira/browse/HBASE-26449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17467429#comment-17467429
]
Hudson commented on HBASE-26449:
--------------------------------
Results for branch master
[build #483 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/483/]:
(/) *{color:green}+1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/483/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/483/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/483/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 way we add or clear failedReplicas may have race
> ----------------------------------------------------
>
> Key: HBASE-26449
> URL: https://issues.apache.org/jira/browse/HBASE-26449
> Project: HBase
> Issue Type: Sub-task
> Components: read replicas
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 3.0.0-alpha-3
>
>
> We will add a replica to failedReplicas in the callback of the replay method
> call, and we will clear the failedReplicas in add method when we meet a flush
> all edit.
> They are in different threads, so it is possible that, we have already clear
> the failedReplicas due to a flush all edit, then in the callback of replay,
> we add a replica to the failedReplicas because of a failure of replicating,
> although the failure is actually before the flush all edit.
> We should find a way to fix this.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)