[
https://issues.apache.org/jira/browse/HBASE-27728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17713731#comment-17713731
]
Hudson commented on HBASE-27728:
--------------------------------
Results for branch master
[build #820 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/820/]:
(/) *{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/820/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/820/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/820/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}
> Implement a tool to migrate replication peer data between different storage
> implementation
> ------------------------------------------------------------------------------------------
>
> Key: HBASE-27728
> URL: https://issues.apache.org/jira/browse/HBASE-27728
> Project: HBase
> Issue Type: Sub-task
> Components: Replication
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 2.6.0, 3.0.0-alpha-4
>
>
> Replication peer data is usually stable unless you manually modify it, so it
> is OK to not migrate automatically. Instead, we could provide a tool to
> migrate the replication peer data.
> And after migration, users can use online configuration change or via a
> cluster a restart to load the new configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
