You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/03/09 21:04:03 UTC
[jira] [Commented] (HBASE-19923) Reset peer state and config when
refresh replication source failed
[ https://issues.apache.org/jira/browse/HBASE-19923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16393581#comment-16393581 ]
Hudson commented on HBASE-19923:
--------------------------------
Results for branch branch-2
[build #465 on builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/465/]: (x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/465//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/465//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/465//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> Reset peer state and config when refresh replication source failed
> ------------------------------------------------------------------
>
> Key: HBASE-19923
> URL: https://issues.apache.org/jira/browse/HBASE-19923
> Project: HBase
> Issue Type: Bug
> Components: Replication
> Affects Versions: 3.0.0
> Reporter: Guanghao Zhang
> Assignee: Guanghao Zhang
> Priority: Major
> Fix For: 3.0.0, 2.1.0
>
> Attachments: HBASE-19923.master.001.patch, HBASE-19923.master.001.patch, HBASE-19923.master.002.patch, HBASE-19923.master.003.patch
>
>
> Now we use procedure for replication. When peer state changed, the RS will read peer state from storage to cache. If RS found the peer state changed, then it will refresh replication source. If refresh failed, the Master will retry the procedure. Then RS will read peer state again, but now the peer state in cache is right. So it don't refresh replication source...... So we need reset the peer state to old peer state when refresh failed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)