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

Hudson commented on HBASE-26538:
--------------------------------

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}


> Should find a way to clear the replication queue for a legacy 
> region_replica_replication peer
> ---------------------------------------------------------------------------------------------
>
>                 Key: HBASE-26538
>                 URL: https://issues.apache.org/jira/browse/HBASE-26538
>             Project: HBase
>          Issue Type: Sub-task
>          Components: read replicas, Replication
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>             Fix For: 3.0.0-alpha-3
>
>
> When rolling upgrading, we will delete the legacy region_replica_replication 
> peer. But since the old region servers still use this peer for replicating, 
> we can not delete all the replication queues.
> We need to find a way to deal with these legacy replication queues after 
> upgrading.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to