[
https://issues.apache.org/jira/browse/HBASE-21486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16705789#comment-16705789
]
Hudson commented on HBASE-21486:
--------------------------------
Results for branch master
[build #639 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/639/]: (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/master/639//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/master/639//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/master/639//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> The current replication implementation for peer in STANDBY state breaks
> serial replication
> ------------------------------------------------------------------------------------------
>
> Key: HBASE-21486
> URL: https://issues.apache.org/jira/browse/HBASE-21486
> Project: HBase
> Issue Type: Sub-task
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Critical
> Fix For: 3.0.0
>
> Attachments: HBASE-21486.patch
>
>
> As we will drop recovered queues in STANDBY state, and also when transiting
> to DA, we will drain the replication queue, we may miss to update the last
> pushed sequence id, and cause the serial replication to be stuck. Need to
> find a way to deal with this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
