You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2021/11/14 13:04:00 UTC

[jira] [Resolved] (HBASE-26449) The way we add or clear failedReplicas may have race

     [ https://issues.apache.org/jira/browse/HBASE-26449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Duo Zhang resolved HBASE-26449.
-------------------------------
    Fix Version/s: HBASE-26233
     Hadoop Flags: Reviewed
       Resolution: Fixed

Merged to branch HBASE-26233.

Thanks [~sunxin] for reviewing.

> 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: HBASE-26233
>
>
> 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)