[jira] [Commented] (HBASE-19943) Only allow removing sync replication peer which is in DA state
[
https://issues.apache.org/jira/browse/HBASE-19943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16527699#comment-16527699
]
Hudson commented on HBASE-19943:
Results for branch master
[build #380 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/380/]: (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/380//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/380//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/380//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Only allow removing sync replication peer which is in DA state
> --
>
> Key: HBASE-19943
> URL: https://issues.apache.org/jira/browse/HBASE-19943
> Project: HBase
> Issue Type: Sub-task
>Reporter: Duo Zhang
>Assignee: Zheng Hu
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: HBASE-19943.HBASE-19064.001.patch,
> HBASE-19943.HBASE-19064.002.patch, HBASE-19943.HBASE-19064.002.patch
>
>
> To simplify the logic of RemovePeerProcedure. Otherwise we may also need to
> reopen regions which makes the RemovePeerProcedure can not fit for both sync
> and normal replication peer.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-19943) Only allow removing sync replication peer which is in DA state
[
https://issues.apache.org/jira/browse/HBASE-19943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16435099#comment-16435099
]
Hudson commented on HBASE-19943:
Results for branch HBASE-19064
[build #94 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19064/94/]:
(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/HBASE-19064/94//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/HBASE-19064/94//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/HBASE-19064/94//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> Only allow removing sync replication peer which is in DA state
> --
>
> Key: HBASE-19943
> URL: https://issues.apache.org/jira/browse/HBASE-19943
> Project: HBase
> Issue Type: Sub-task
>Reporter: Duo Zhang
>Assignee: Zheng Hu
>Priority: Major
> Attachments: HBASE-19943.HBASE-19064.001.patch,
> HBASE-19943.HBASE-19064.002.patch, HBASE-19943.HBASE-19064.002.patch
>
>
> To simplify the logic of RemovePeerProcedure. Otherwise we may also need to
> reopen regions which makes the RemovePeerProcedure can not fit for both sync
> and normal replication peer.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-19943) Only allow removing sync replication peer which is in DA state
[
https://issues.apache.org/jira/browse/HBASE-19943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16430100#comment-16430100
]
Hudson commented on HBASE-19943:
Results for branch HBASE-19064
[build #90 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19064/90/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19064/90//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/HBASE-19064/90//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/HBASE-19064/90//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> Only allow removing sync replication peer which is in DA state
> --
>
> Key: HBASE-19943
> URL: https://issues.apache.org/jira/browse/HBASE-19943
> Project: HBase
> Issue Type: Sub-task
>Reporter: Duo Zhang
>Assignee: Zheng Hu
>Priority: Major
> Attachments: HBASE-19943.HBASE-19064.001.patch,
> HBASE-19943.HBASE-19064.002.patch, HBASE-19943.HBASE-19064.002.patch
>
>
> To simplify the logic of RemovePeerProcedure. Otherwise we may also need to
> reopen regions which makes the RemovePeerProcedure can not fit for both sync
> and normal replication peer.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-19943) Only allow removing sync replication peer which is in DA state
[
https://issues.apache.org/jira/browse/HBASE-19943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16416727#comment-16416727
]
Hudson commented on HBASE-19943:
Results for branch HBASE-19064
[build #77 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19064/77/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19064/77//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/HBASE-19064/77//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/HBASE-19064/77//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> Only allow removing sync replication peer which is in DA state
> --
>
> Key: HBASE-19943
> URL: https://issues.apache.org/jira/browse/HBASE-19943
> Project: HBase
> Issue Type: Sub-task
>Reporter: Duo Zhang
>Assignee: Zheng Hu
>Priority: Major
> Attachments: HBASE-19943.HBASE-19064.001.patch,
> HBASE-19943.HBASE-19064.002.patch, HBASE-19943.HBASE-19064.002.patch
>
>
> To simplify the logic of RemovePeerProcedure. Otherwise we may also need to
> reopen regions which makes the RemovePeerProcedure can not fit for both sync
> and normal replication peer.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-19943) Only allow removing sync replication peer which is in DA state
[
https://issues.apache.org/jira/browse/HBASE-19943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16391794#comment-16391794
]
Hudson commented on HBASE-19943:
Results for branch HBASE-19064
[build #58 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19064/58/]:
(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/HBASE-19064/58//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/HBASE-19064/58//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/HBASE-19064/58//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> Only allow removing sync replication peer which is in DA state
> --
>
> Key: HBASE-19943
> URL: https://issues.apache.org/jira/browse/HBASE-19943
> Project: HBase
> Issue Type: Sub-task
>Reporter: Duo Zhang
>Assignee: Zheng Hu
>Priority: Major
> Attachments: HBASE-19943.HBASE-19064.001.patch,
> HBASE-19943.HBASE-19064.002.patch, HBASE-19943.HBASE-19064.002.patch
>
>
> To simplify the logic of RemovePeerProcedure. Otherwise we may also need to
> reopen regions which makes the RemovePeerProcedure can not fit for both sync
> and normal replication peer.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-19943) Only allow removing sync replication peer which is in DA state
[ https://issues.apache.org/jira/browse/HBASE-19943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16383403#comment-16383403 ] Zheng Hu commented on HBASE-19943: -- Pushed patch.v2 to HBASE-19064 branch. The find-bugs has been fixed when committing. Thanks [~Apache9] for reviewing. > Only allow removing sync replication peer which is in DA state > -- > > Key: HBASE-19943 > URL: https://issues.apache.org/jira/browse/HBASE-19943 > Project: HBase > Issue Type: Sub-task >Reporter: Duo Zhang >Assignee: Zheng Hu >Priority: Major > Attachments: HBASE-19943.HBASE-19064.001.patch, > HBASE-19943.HBASE-19064.002.patch, HBASE-19943.HBASE-19064.002.patch > > > To simplify the logic of RemovePeerProcedure. Otherwise we may also need to > reopen regions which makes the RemovePeerProcedure can not fit for both sync > and normal replication peer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-19943) Only allow removing sync replication peer which is in DA state
[
https://issues.apache.org/jira/browse/HBASE-19943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16383381#comment-16383381
]
Hadoop QA commented on HBASE-19943:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
9s{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 1 new or modified test
files. {color} |
|| || || || {color:brown} HBASE-19064 Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
56s{color} | {color:green} HBASE-19064 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
41s{color} | {color:green} HBASE-19064 passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
5s{color} | {color:green} HBASE-19064 passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 5m
44s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 1m
59s{color} | {color:red} hbase-server in HBASE-19064 has 1 extant Findbugs
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
28s{color} | {color:green} HBASE-19064 passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
23s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
43s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
43s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
4s{color} | {color:green} the patch passed {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
36s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
18m 8s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.5 2.7.4 or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
8s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
28s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green}114m
59s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
21s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}156m 32s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 |
| JIRA Issue | HBASE-19943 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12912731/HBASE-19943.HBASE-19064.002.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs shadedjars
hadoopcheck hbaseanti checkstyle compile |
| uname | Linux 038d91d79ab1 3.13.0-133-generic #182-Ubuntu SMP Tue Sep 19
15:49:21 UTC 2017 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | HBASE-19064 / 3301f9757c |
| maven | version: Apache Maven 3.5.2
(138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T07:58:13Z) |
| Default Java | 1.8.0_151 |
| findbugs | v3.1.0-RC3 |
| findbugs |
https://builds.apache.org/job/PreCommit-HBASE-Build/11768/artifact/patchprocess/branch-findbugs-hbase-server-warnings.html
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/11768/testReport/ |
| Max. process+thread count | 4045 (vs. ulimit of 1) |
| modules | C: hbase-server U: hbase-server |
| Console
[jira] [Commented] (HBASE-19943) Only allow removing sync replication peer which is in DA state
[
https://issues.apache.org/jira/browse/HBASE-19943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16383231#comment-16383231
]
Hadoop QA commented on HBASE-19943:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
16s{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 1 new or modified test
files. {color} |
|| || || || {color:brown} HBASE-19064 Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
12s{color} | {color:green} HBASE-19064 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
39s{color} | {color:green} HBASE-19064 passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
54s{color} | {color:green} HBASE-19064 passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 5m
12s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 1m
47s{color} | {color:red} hbase-server in HBASE-19064 has 24 extant Findbugs
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
26s{color} | {color:green} HBASE-19064 passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
57s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
39s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
39s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
54s{color} | {color:green} the patch passed {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
10s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 6m
8s{color} | {color:red} The patch causes 10 errors with Hadoop v2.6.5. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 8m
5s{color} | {color:red} The patch causes 10 errors with Hadoop v2.7.4. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 10m
11s{color} | {color:red} The patch causes 10 errors with Hadoop v3.0.0. {color}
|
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
0s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
27s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red}106m 28s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
22s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}137m 50s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.regionserver.TestRegionOpen |
| | hadoop.hbase.client.TestAsyncTableBatch |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 |
| JIRA Issue | HBASE-19943 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12912716/HBASE-19943.HBASE-19064.002.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs shadedjars
hadoopcheck hbaseanti checkstyle compile |
| uname | Linux 13569171a46b 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12
13:48:03 UTC 2016 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | HBASE-19064 / 0ac7692461 |
| maven | version: Apache Maven 3.5.2
(138edd61fd100ec658bfa2d307c43b76940a5d7d;
[jira] [Commented] (HBASE-19943) Only allow removing sync replication peer which is in DA state
[ https://issues.apache.org/jira/browse/HBASE-19943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16383139#comment-16383139 ] Zheng Hu commented on HBASE-19943: -- Patch v2. fix the failed TestReplicationAdmin UT. > Only allow removing sync replication peer which is in DA state > -- > > Key: HBASE-19943 > URL: https://issues.apache.org/jira/browse/HBASE-19943 > Project: HBase > Issue Type: Sub-task >Reporter: Duo Zhang >Assignee: Zheng Hu >Priority: Major > Attachments: HBASE-19943.HBASE-19064.001.patch, > HBASE-19943.HBASE-19064.002.patch > > > To simplify the logic of RemovePeerProcedure. Otherwise we may also need to > reopen regions which makes the RemovePeerProcedure can not fit for both sync > and normal replication peer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-19943) Only allow removing sync replication peer which is in DA state
[ https://issues.apache.org/jira/browse/HBASE-19943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16383135#comment-16383135 ] Zheng Hu commented on HBASE-19943: -- The TestRegionOpen UT is broken after HBASE-19391 , and the HBASE-20052 fix the failed UT. So our sync replication branch need rebase to the lastest master now .. > Only allow removing sync replication peer which is in DA state > -- > > Key: HBASE-19943 > URL: https://issues.apache.org/jira/browse/HBASE-19943 > Project: HBase > Issue Type: Sub-task >Reporter: Duo Zhang >Assignee: Zheng Hu >Priority: Major > Attachments: HBASE-19943.HBASE-19064.001.patch > > > To simplify the logic of RemovePeerProcedure. Otherwise we may also need to > reopen regions which makes the RemovePeerProcedure can not fit for both sync > and normal replication peer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-19943) Only allow removing sync replication peer which is in DA state
[
https://issues.apache.org/jira/browse/HBASE-19943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16381994#comment-16381994
]
Hadoop QA commented on HBASE-19943:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
16s{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 1 new or modified test
files. {color} |
|| || || || {color:brown} HBASE-19064 Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 7m
3s{color} | {color:green} HBASE-19064 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
38s{color} | {color:green} HBASE-19064 passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
1s{color} | {color:green} HBASE-19064 passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 5m
15s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 1m
52s{color} | {color:red} hbase-server in HBASE-19064 has 24 extant Findbugs
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
33s{color} | {color:green} HBASE-19064 passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
57s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
39s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
39s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
57s{color} | {color:green} the patch passed {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
14s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 6m
13s{color} | {color:red} The patch causes 10 errors with Hadoop v2.6.5. {color}
|
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 8m
9s{color} | {color:red} The patch causes 10 errors with Hadoop v2.7.4. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 10m
19s{color} | {color:red} The patch causes 10 errors with Hadoop v3.0.0. {color}
|
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
58s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
27s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red}103m 17s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
26s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}137m 58s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.client.replication.TestReplicationAdmin |
| | hadoop.hbase.regionserver.TestRegionOpen |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 |
| JIRA Issue | HBASE-19943 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12912583/HBASE-19943.HBASE-19064.001.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs shadedjars
hadoopcheck hbaseanti checkstyle compile |
| uname | Linux c263152a58e4 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12
13:48:03 UTC 2016 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | HBASE-19064 / 0ac7692461 |
| maven | version: Apache Maven 3.5.2
[jira] [Commented] (HBASE-19943) Only allow removing sync replication peer which is in DA state
[ https://issues.apache.org/jira/browse/HBASE-19943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16353499#comment-16353499 ] Zheng Hu commented on HBASE-19943: -- Fine , Assigned to myself. > Only allow removing sync replication peer which is in DA state > -- > > Key: HBASE-19943 > URL: https://issues.apache.org/jira/browse/HBASE-19943 > Project: HBase > Issue Type: Sub-task >Reporter: Duo Zhang >Priority: Major > > To simplify the logic of RemovePeerProcedure. Otherwise we may also need to > reopen regions which makes the RemovePeerProcedure can not fit for both sync > and normal replication peer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-19943) Only allow removing sync replication peer which is in DA state
[ https://issues.apache.org/jira/browse/HBASE-19943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16353453#comment-16353453 ] Duo Zhang commented on HBASE-19943: --- [~openinx] FYI. This is a separated work, can do it first. > Only allow removing sync replication peer which is in DA state > -- > > Key: HBASE-19943 > URL: https://issues.apache.org/jira/browse/HBASE-19943 > Project: HBase > Issue Type: Sub-task >Reporter: Duo Zhang >Priority: Major > > To simplify the logic of RemovePeerProcedure. Otherwise we may also need to > reopen regions which makes the RemovePeerProcedure can not fit for both sync > and normal replication peer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
