[
https://issues.apache.org/jira/browse/HBASE-23993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17062281#comment-17062281
]
Hudson commented on HBASE-23993:
--------------------------------
Results for branch branch-2
[build #2557 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2557/]:
(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/2557//General_Nightly_Build_Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2557//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/2557//JDK8_Nightly_Build_Report_(Hadoop3)/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2557//JDK11_Nightly_Build_Report/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(x) {color:red}-1 client integration test{color}
--Failed when running client tests on top of Hadoop 2. [see log for
details|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2557//artifact/output-integration/hadoop-2.log].
(note that this means we didn't run on Hadoop 3)
> Use loopback for zk standalone server in minizkcluster
> ------------------------------------------------------
>
> Key: HBASE-23993
> URL: https://issues.apache.org/jira/browse/HBASE-23993
> Project: HBase
> Issue Type: Sub-task
> Components: Zookeeper
> Reporter: Michael Stack
> Assignee: Michael Stack
> Priority: Major
> Fix For: 3.0.0, 2.3.0
>
>
> Use loopback for minizkcluster. HBASE-23919 shows how sometimes unit tests
> fail in setup because the minizkcluster won't come up. It looks like client
> is trying to stat the server but though the server is trying to poll a socket
> bound to 0.0.0.0, the server never notices the client pings. Using loopback,
> I don't see these odd failures anymore.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
