[jira] [Commented] (HBASE-21486) The current replication implementation for peer in STANDBY state breaks serial replication
[
https://issues.apache.org/jira/browse/HBASE-21486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (HBASE-21486) The current replication implementation for peer in STANDBY state breaks serial replication
[ https://issues.apache.org/jira/browse/HBASE-21486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16704775#comment-16704775 ] Guanghao Zhang commented on HBASE-21486: +1. > 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)
[jira] [Commented] (HBASE-21486) The current replication implementation for peer in STANDBY state breaks serial replication
[ https://issues.apache.org/jira/browse/HBASE-21486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16703067#comment-16703067 ] Duo Zhang commented on HBASE-21486: --- Review board link: https://reviews.apache.org/r/69483/ > 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)
[jira] [Commented] (HBASE-21486) The current replication implementation for peer in STANDBY state breaks serial replication
[ https://issues.apache.org/jira/browse/HBASE-21486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16703065#comment-16703065 ] Duo Zhang commented on HBASE-21486: --- The checkstyle issue is because that the enum name itself is too long... [~zghaobac] PTAL. Thanks. > 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)
[jira] [Commented] (HBASE-21486) The current replication implementation for peer in STANDBY state breaks serial replication
[
https://issues.apache.org/jira/browse/HBASE-21486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701870#comment-16701870
]
Hadoop QA commented on HBASE-21486:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
11s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 3 new or modified test
files. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
25s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
31s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 3m
4s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
25s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
27s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 4m
42s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
43s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
14s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
30s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 3m
1s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} cc {color} | {color:green} 3m
1s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 3m
1s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 1m
13s{color} | {color:red} hbase-server: The patch generated 1 new + 0 unchanged
- 0 fixed = 1 total (was 0) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
17s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
10m 3s{color} | {color:green} Patch does not cause any errors with Hadoop
2.7.4 or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} hbaseprotoc {color} | {color:green}
1m 21s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 5m
35s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
44s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
37s{color} | {color:green} hbase-protocol-shaded in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}142m 24s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
38s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}195m 1s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests |
hadoop.hbase.master.procedure.TestMasterFailoverWithProcedures |
| | hadoop.hbase.regionserver.TestMultiColumnScanner |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:b002b0b |
| JIRA Issue | HBASE-21486 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12949816/HBASE-21486.patch |
| Optional Tests | dupname asflicense cc unit hbaseprotoc javac javadoc
