[GitHub] zookeeper pull request #532: ZOOKEEPER-3043: QuorumKerberosHostBasedAuthTest...
Github user eolivelli closed the pull request at: https://github.com/apache/zookeeper/pull/532 ---
ZooKeeper_branch35_jdk8 - Build # 984 - Still Failing
See https://builds.apache.org/job/ZooKeeper_branch35_jdk8/984/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 61.75 KB...] [junit] Running org.apache.zookeeper.test.ServerCnxnTest in thread 1 [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.055 sec, Thread: 7, Class: org.apache.zookeeper.test.SaslSuperUserTest [junit] Running org.apache.zookeeper.test.SessionInvalidationTest in thread 7 [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.67 sec, Thread: 7, Class: org.apache.zookeeper.test.SessionInvalidationTest [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.366 sec, Thread: 1, Class: org.apache.zookeeper.test.ServerCnxnTest [junit] Running org.apache.zookeeper.test.SessionTest in thread 7 [junit] Running org.apache.zookeeper.test.SessionTimeoutTest in thread 1 [junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.6 sec, Thread: 1, Class: org.apache.zookeeper.test.SessionTimeoutTest [junit] Running org.apache.zookeeper.test.SessionTrackerCheckTest in thread 1 [junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.083 sec, Thread: 1, Class: org.apache.zookeeper.test.SessionTrackerCheckTest [junit] Running org.apache.zookeeper.test.SessionUpgradeTest in thread 1 [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 148.705 sec, Thread: 8, Class: org.apache.zookeeper.test.RecoveryTest [junit] Running org.apache.zookeeper.test.StandaloneTest in thread 8 [junit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.806 sec, Thread: 7, Class: org.apache.zookeeper.test.SessionTest [junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.7 sec, Thread: 8, Class: org.apache.zookeeper.test.StandaloneTest [junit] Running org.apache.zookeeper.test.StatTest in thread 7 [junit] Running org.apache.zookeeper.test.StaticHostProviderTest in thread 8 [junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.938 sec, Thread: 7, Class: org.apache.zookeeper.test.StatTest [junit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.878 sec, Thread: 8, Class: org.apache.zookeeper.test.StaticHostProviderTest [junit] Running org.apache.zookeeper.test.StringUtilTest in thread 7 [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.068 sec, Thread: 7, Class: org.apache.zookeeper.test.StringUtilTest [junit] Running org.apache.zookeeper.test.SyncCallTest in thread 8 [junit] Running org.apache.zookeeper.test.TruncateTest in thread 7 [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.007 sec, Thread: 8, Class: org.apache.zookeeper.test.SyncCallTest [junit] Running org.apache.zookeeper.test.WatchEventWhenAutoResetTest in thread 8 [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 107.45 sec, Thread: 5, Class: org.apache.zookeeper.test.RestoreCommittedLogTest [junit] Running org.apache.zookeeper.test.WatchedEventTest in thread 5 [junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.105 sec, Thread: 5, Class: org.apache.zookeeper.test.WatchedEventTest [junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 18.899 sec, Thread: 1, Class: org.apache.zookeeper.test.SessionUpgradeTest [junit] Running org.apache.zookeeper.test.WatcherFuncTest in thread 5 [junit] Running org.apache.zookeeper.test.WatcherTest in thread 1 [junit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.046 sec, Thread: 5, Class: org.apache.zookeeper.test.WatcherFuncTest [junit] Running org.apache.zookeeper.test.X509AuthTest in thread 5 [junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.078 sec, Thread: 5, Class: org.apache.zookeeper.test.X509AuthTest [junit] Running org.apache.zookeeper.test.ZkDatabaseCorruptionTest in thread 5 [junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 20.307 sec, Thread: 7, Class: org.apache.zookeeper.test.TruncateTest [junit] Running org.apache.zookeeper.test.ZooKeeperQuotaTest in thread 7 [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.747 sec, Thread: 7, Class: org.apache.zookeeper.test.ZooKeeperQuotaTest [junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 22.336 sec, Thread: 8, Class: org.apache.zookeeper.test.WatchEventWhenAutoResetTest [junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 14.686 sec, Thread: 5, Class: org.apache.zookeeper.test.ZkDatabaseCorruptionTest [junit] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 32.181 sec, Thread: 1, Class: org.apache.zookeeper.test.WatcherTest
[jira] [Commented] (ZOOKEEPER-3043) QuorumKerberosHostBasedAuthTest fails on Linux box: Unable to parse:includedir /etc/krb5.conf.d/
[
https://issues.apache.org/jira/browse/ZOOKEEPER-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494546#comment-16494546
]
Hudson commented on ZOOKEEPER-3043:
---
FAILURE: Integrated in Jenkins build ZooKeeper-trunk #43 (See
[https://builds.apache.org/job/ZooKeeper-trunk/43/])
ZOOKEEPER-3043: QuorumKerberosHostBasedAuthTest fails on Linux box: (phunt: rev
fa34d0d01e33a40465ebd72497f37d62f0a4bce0)
* (edit) build.xml
* (edit)
src/java/test/org/apache/zookeeper/server/quorum/auth/KerberosTestUtils.java
> QuorumKerberosHostBasedAuthTest fails on Linux box: Unable to
> parse:includedir /etc/krb5.conf.d/
>
>
> Key: ZOOKEEPER-3043
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3043
> Project: ZooKeeper
> Issue Type: Improvement
> Components: build, kerberos, tests
>Affects Versions: 3.5.4, 3.6.0, 3.4.12
>Reporter: Enrico Olivelli
>Assignee: Enrico Olivelli
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.6.0, 3.4.13, 3.5.5
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> I am testing 3.5.4-BETA rc0 and I get this error while running tests
> ant -Dtestcase=QuorumKerberosHostBasedAuthTest test-core-java
>
> {code}
> Testsuite:
> org.apache.zookeeper.server.quorum.auth.QuorumKerberosHostBasedAuthTest
> Tests run: 0, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1,029 sec
> - Standard Output ---
> 2018-05-14 13:29:36,829 [myid:] - INFO [main:JUnit4ZKTestRunner@47] - No
> test.method specified. using default methods.
> 2018-05-14 13:29:36,834 [myid:] - INFO [main:JUnit4ZKTestRunner@47] - No
> test.method specified. using default methods.
> 2018-05-14 13:29:36,839 [myid:] - INFO [main:MiniKdc@230] - Configuration:
> 2018-05-14 13:29:36,839 [myid:] - INFO [main:MiniKdc@231] -
> ---
> 2018-05-14 13:29:36,841 [myid:] - INFO [main:MiniKdc@233] - debug: false
> 2018-05-14 13:29:36,841 [myid:] - INFO [main:MiniKdc@233] - transport: TCP
> 2018-05-14 13:29:36,841 [myid:] - INFO [main:MiniKdc@233] -
> max.ticket.lifetime: 8640
> 2018-05-14 13:29:36,841 [myid:] - INFO [main:MiniKdc@233] - org.name:
> EXAMPLE
> 2018-05-14 13:29:36,841 [myid:] - INFO [main:MiniKdc@233] - kdc.port: 0
> 2018-05-14 13:29:36,841 [myid:] - INFO [main:MiniKdc@233] - org.domain: COM
> 2018-05-14 13:29:36,841 [myid:] - INFO [main:MiniKdc@233] -
> max.renewable.lifetime: 60480
> 2018-05-14 13:29:36,841 [myid:] - INFO [main:MiniKdc@233] - instance:
> DefaultKrbServer
> 2018-05-14 13:29:36,842 [myid:] - INFO [main:MiniKdc@233] -
> kdc.bind.address: localhost
> 2018-05-14 13:29:36,842 [myid:] - INFO [main:MiniKdc@235] -
> ---
> 2018-05-14 13:29:37,855 [myid:] - INFO [main:MiniKdc@356] - MiniKdc stopped.
> - ---
> Testcase:
> org.apache.zookeeper.server.quorum.auth.QuorumKerberosHostBasedAuthTest took
> 0 sec
> Caused an ERROR
> Unable to parse:includedir /etc/krb5.conf.d/
> java.lang.RuntimeException: Unable to parse:includedir /etc/krb5.conf.d/
> at
> org.apache.kerby.kerberos.kerb.common.Krb5Parser.load(Krb5Parser.java:72)
> at
> org.apache.kerby.kerberos.kerb.common.Krb5Conf.addKrb5Config(Krb5Conf.java:47)
> at
> org.apache.kerby.kerberos.kerb.client.ClientUtil.getDefaultConfig(ClientUtil.java:94)
> at
> org.apache.kerby.kerberos.kerb.client.KrbClientBase.(KrbClientBase.java:51)
> at
> org.apache.kerby.kerberos.kerb.client.KrbClient.(KrbClient.java:38)
> at
> org.apache.kerby.kerberos.kerb.server.SimpleKdcServer.(SimpleKdcServer.java:54)
> at
> org.apache.zookeeper.server.quorum.auth.MiniKdc.start(MiniKdc.java:285)
> at
> org.apache.zookeeper.server.quorum.auth.KerberosSecurityTestcase.startMiniKdc(KerberosSecurityTestcase.java:70)
> at
> org.apache.zookeeper.server.quorum.auth.KerberosSecurityTestcase.setUpSasl(KerberosSecurityTestcase.java:56)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
ZooKeeper-trunk - Build # 43 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk/43/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 147.77 KB...] [junit] Running org.apache.zookeeper.test.SessionTimeoutTest in thread 5 [junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.01 sec, Thread: 5, Class: org.apache.zookeeper.test.SessionTimeoutTest [junit] Running org.apache.zookeeper.test.SessionTrackerCheckTest in thread 5 [junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.107 sec, Thread: 5, Class: org.apache.zookeeper.test.SessionTrackerCheckTest [junit] Running org.apache.zookeeper.test.SessionUpgradeTest in thread 5 [junit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.45 sec, Thread: 6, Class: org.apache.zookeeper.test.SessionTest [junit] Running org.apache.zookeeper.test.StandaloneTest in thread 6 [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 140.225 sec, Thread: 8, Class: org.apache.zookeeper.test.RecoveryTest [junit] Running org.apache.zookeeper.test.StatTest in thread 8 [junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.802 sec, Thread: 6, Class: org.apache.zookeeper.test.StandaloneTest [junit] Running org.apache.zookeeper.test.StaticHostProviderTest in thread 6 [junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.433 sec, Thread: 8, Class: org.apache.zookeeper.test.StatTest [junit] Running org.apache.zookeeper.test.StringUtilTest in thread 8 [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.07 sec, Thread: 8, Class: org.apache.zookeeper.test.StringUtilTest [junit] Running org.apache.zookeeper.test.SyncCallTest in thread 8 [junit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.414 sec, Thread: 6, Class: org.apache.zookeeper.test.StaticHostProviderTest [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.944 sec, Thread: 8, Class: org.apache.zookeeper.test.SyncCallTest [junit] Running org.apache.zookeeper.test.TruncateTest in thread 6 [junit] Running org.apache.zookeeper.test.WatchEventWhenAutoResetTest in thread 8 [junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 19.071 sec, Thread: 5, Class: org.apache.zookeeper.test.SessionUpgradeTest [junit] Running org.apache.zookeeper.test.WatchedEventTest in thread 5 [junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.109 sec, Thread: 5, Class: org.apache.zookeeper.test.WatchedEventTest [junit] Running org.apache.zookeeper.test.WatcherFuncTest in thread 5 [junit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.098 sec, Thread: 5, Class: org.apache.zookeeper.test.WatcherFuncTest [junit] Running org.apache.zookeeper.test.WatcherTest in thread 5 [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 99.016 sec, Thread: 3, Class: org.apache.zookeeper.test.RestoreCommittedLogTest [junit] Running org.apache.zookeeper.test.X509AuthTest in thread 3 [junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.094 sec, Thread: 3, Class: org.apache.zookeeper.test.X509AuthTest [junit] Running org.apache.zookeeper.test.ZkDatabaseCorruptionTest in thread 3 [junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 16.093 sec, Thread: 6, Class: org.apache.zookeeper.test.TruncateTest [junit] Running org.apache.zookeeper.test.ZooKeeperQuotaTest in thread 6 [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.159 sec, Thread: 6, Class: org.apache.zookeeper.test.ZooKeeperQuotaTest [junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 21.533 sec, Thread: 8, Class: org.apache.zookeeper.test.WatchEventWhenAutoResetTest [junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 19.854 sec, Thread: 3, Class: org.apache.zookeeper.test.ZkDatabaseCorruptionTest [junit] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 32.497 sec, Thread: 5, Class: org.apache.zookeeper.test.WatcherTest [junit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 279.023 sec, Thread: 1, Class: org.apache.zookeeper.test.ReconfigTest [junit] Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 606.828 sec, Thread: 4, Class: org.apache.zookeeper.test.DisconnectedWatcherTest [junit] Test org.apache.zookeeper.test.DisconnectedWatcherTest FAILED [junit] Tests run: 104, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 545.661 sec, Thread: 2, Class: org.apache.zookeeper.test.NettyNettySuiteTest [junit] Tests run: 104, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 548.238 sec, Thread: 7, Class: org.apache.zookeeper.test.NioNettySuiteTest
[jira] [Commented] (ZOOKEEPER-2317) Non-OSGi compatible version
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494547#comment-16494547 ] Hudson commented on ZOOKEEPER-2317: --- FAILURE: Integrated in Jenkins build ZooKeeper-trunk #43 (See [https://builds.apache.org/job/ZooKeeper-trunk/43/]) ZOOKEEPER-2317: Ensure that OSGi versions are valid (phunt: rev 1c3aac025528faf8c776f5b715c23c4cc58138b8) * (edit) build.xml > Non-OSGi compatible version > --- > > Key: ZOOKEEPER-2317 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2317 > Project: ZooKeeper > Issue Type: Bug > Components: build >Affects Versions: 3.5.1 > Environment: Karaf OSGi container >Reporter: Markus Tippmann >Assignee: Sachin >Priority: Blocker > Labels: pull-request-available > Fix For: 3.6.0, 3.5.5 > > Attachments: > 0001-Put-a-different-version-string-into-the-jar-meta-dat.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > Bundle cannot be deployed to OSGi container. > Manifest version is not OSGi compatible. > Instead of using 3.5.1-alpha, manifest needs to contain 3.5.1.alpha -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ZOOKEEPER-1919) Update the C implementation of removeWatches to have it match ZOOKEEPER-1910
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494545#comment-16494545 ] Hudson commented on ZOOKEEPER-1919: --- FAILURE: Integrated in Jenkins build ZooKeeper-trunk #43 (See [https://builds.apache.org/job/ZooKeeper-trunk/43/]) ZOOKEEPER-1919 Update the C implementation of removeWatches to have it (phunt: rev 9c4bd4d335c52beb44f303b8b6e0abfe03cb9241) * (edit) src/c/src/zk_hashtable.c * (edit) src/c/tests/TestClient.cc * (edit) src/c/include/zookeeper.h * (edit) src/c/src/zookeeper.c * (edit) src/c/include/proto.h > Update the C implementation of removeWatches to have it match ZOOKEEPER-1910 > > > Key: ZOOKEEPER-1919 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1919 > Project: ZooKeeper > Issue Type: Bug > Components: c client >Affects Versions: 3.5.0 >Reporter: Raul Gutierrez Segales >Assignee: Raul Gutierrez Segales >Priority: Blocker > Labels: pull-request-available > Fix For: 3.6.0, 3.5.5 > > Attachments: ZOOKEEPER-1919.patch, ZOOKEEPER-1919.patch > > Time Spent: 2h > Remaining Estimate: 0h > > See https://issues.apache.org/jira/browse/ZOOKEEPER-1910 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ZOOKEEPER-2317) Non-OSGi compatible version
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-2317: Fix Version/s: 3.6.0 > Non-OSGi compatible version > --- > > Key: ZOOKEEPER-2317 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2317 > Project: ZooKeeper > Issue Type: Bug > Components: build >Affects Versions: 3.5.1 > Environment: Karaf OSGi container >Reporter: Markus Tippmann >Assignee: Sachin >Priority: Blocker > Labels: pull-request-available > Fix For: 3.6.0, 3.5.5 > > Attachments: > 0001-Put-a-different-version-string-into-the-jar-meta-dat.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > Bundle cannot be deployed to OSGi container. > Manifest version is not OSGi compatible. > Instead of using 3.5.1-alpha, manifest needs to contain 3.5.1.alpha -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] zookeeper issue #531: [ZOOKEEPER-2317] Ensure that OSGi versions are valid
Github user phunt commented on the issue: https://github.com/apache/zookeeper/pull/531 +1, lgtm. Thanks @timothyjward ! ---
[jira] [Resolved] (ZOOKEEPER-2317) Non-OSGi compatible version
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt resolved ZOOKEEPER-2317. - Resolution: Fixed Fix Version/s: (was: 3.6.0) Issue resolved by pull request 531 [https://github.com/apache/zookeeper/pull/531] > Non-OSGi compatible version > --- > > Key: ZOOKEEPER-2317 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2317 > Project: ZooKeeper > Issue Type: Bug > Components: build >Affects Versions: 3.5.1 > Environment: Karaf OSGi container >Reporter: Markus Tippmann >Assignee: Sachin >Priority: Blocker > Labels: pull-request-available > Fix For: 3.5.5 > > Attachments: > 0001-Put-a-different-version-string-into-the-jar-meta-dat.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Bundle cannot be deployed to OSGi container. > Manifest version is not OSGi compatible. > Instead of using 3.5.1-alpha, manifest needs to contain 3.5.1.alpha -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] zookeeper pull request #531: [ZOOKEEPER-2317] Ensure that OSGi versions are ...
Github user asfgit closed the pull request at: https://github.com/apache/zookeeper/pull/531 ---
[GitHub] zookeeper issue #532: ZOOKEEPER-3043: QuorumKerberosHostBasedAuthTest fails ...
Github user phunt commented on the issue: https://github.com/apache/zookeeper/pull/532 +1, lgtm. Thanks @eolivelli Please close this PR manually as it's not the default branch for the repo. thx. ---
[GitHub] zookeeper issue #524: ZOOKEEPER-3043: QuorumKerberosHostBasedAuthTest fails ...
Github user phunt commented on the issue: https://github.com/apache/zookeeper/pull/524 +1, lgtm. Thanks @eolivelli ---
[GitHub] zookeeper pull request #524: ZOOKEEPER-3043: QuorumKerberosHostBasedAuthTest...
Github user asfgit closed the pull request at: https://github.com/apache/zookeeper/pull/524 ---
[GitHub] zookeeper issue #528: ZOOKEEPER-3034 Facing issues while building from sourc...
Github user phunt commented on the issue: https://github.com/apache/zookeeper/pull/528 ps. you can try using my repos, makes it easy to try out various envs: https://hub.docker.com/r/phunt/ See the readme on how to run - I typically map my zk source directory into the container directly to aid in testing. these images have cppunit installed - you can use the package manager to uninstall them if you want to test with and without --without-cppunit ---
[GitHub] zookeeper issue #528: ZOOKEEPER-3034 Facing issues while building from sourc...
Github user phunt commented on the issue: https://github.com/apache/zookeeper/pull/528 Seems like it breaks ubuntu 14.04 (not sure what else, that's what I tried). This is working fine w/o the patch: ./configure checking for doxygen... no checking for perl... /usr/bin/perl checking for dot... no checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes ./configure: line 5034: syntax error near unexpected token `CPPUNIT,' ./configure: line 5034: `PKG_CHECK_MODULES_STATIC(CPPUNIT, cppunit >= 1.10.2)' ---
[GitHub] zookeeper issue #511: Incorrect constant value
Github user phunt commented on the issue: https://github.com/apache/zookeeper/pull/511 @roy2220 now that #522 is committed can you give it a try and verify? Thanks! ---
[jira] [Created] (ZOOKEEPER-3054) ipv6 detection in configure.ac is broken
Patrick Hunt created ZOOKEEPER-3054: --- Summary: ipv6 detection in configure.ac is broken Key: ZOOKEEPER-3054 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3054 Project: ZooKeeper Issue Type: Bug Components: c client, tests Affects Versions: 3.6.0, 3.5.5 Reporter: Patrick Hunt When I run the test using (jdk8 tag): https://hub.docker.com/r/phunt/zk-docker-devenv.ubuntu.14.04/tags/ it fails with an IPV6 failure. afaict the container does not have ipv6 configured, although the kernel has it available as a feature. I believe this to be the real issue - it's a kernel feature but no available in the runtime. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ZOOKEEPER-3053) add remove watches capabilities to the c cli
Patrick Hunt created ZOOKEEPER-3053: --- Summary: add remove watches capabilities to the c cli Key: ZOOKEEPER-3053 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3053 Project: ZooKeeper Issue Type: Bug Components: c client, tests Affects Versions: 3.6.0, 3.5.5 Reporter: Patrick Hunt It would be good to be able to exercise the remove watches functionality from the c client cli. Mostly for testing purposes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ZOOKEEPER-3052) testReadOnly fails on slow host
Patrick Hunt created ZOOKEEPER-3052: --- Summary: testReadOnly fails on slow host Key: ZOOKEEPER-3052 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3052 Project: ZooKeeper Issue Type: Bug Components: c client, tests Affects Versions: 3.6.0, 3.5.5 Reporter: Patrick Hunt Fix For: 3.6.0, 3.5.5 When running on a slow host (docker ubuntu on mac) the "sleep(3)" in tests/zkServer.sh is not sufficient wait for the server to enter RO mode. Recommend adding a "isro" 4lw check in the script to wait until the server is in RO mode. If this takes longer than 60 seconds the zkServer.sh should fail. For more background see the comment here: https://github.com/apache/zookeeper/pull/522#issuecomment-392980087 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] zookeeper pull request #522: ZOOKEEPER-1919 Update the C implementation of r...
Github user asfgit closed the pull request at: https://github.com/apache/zookeeper/pull/522 ---
[GitHub] zookeeper issue #522: ZOOKEEPER-1919 Update the C implementation of removeWa...
Github user phunt commented on the issue: https://github.com/apache/zookeeper/pull/522 Hm. I had some trouble testing this. In particular I ran into the following. Some of this might be due to the fact that I run ubuntu in a docker container on my mac, but I think it could be an issue regardless: 1) tests/zkServer.sh isn't sleeping long enough and the client gives up too soon (RO mode takes a while to kick in) 2) IPV6 is identified but failing 3) remove watches wasn't added to the c cli so you can't exercise outside the test. I'll enter jiras for these. Some are good Newbie issues. ---
[jira] [Reopened] (ZOOKEEPER-3046) testManyChildWatchersAutoReset is flaky
[ https://issues.apache.org/jira/browse/ZOOKEEPER-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bogdan Kanivets reopened ZOOKEEPER-3046: > testManyChildWatchersAutoReset is flaky > --- > > Key: ZOOKEEPER-3046 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3046 > Project: ZooKeeper > Issue Type: Bug > Components: tests >Affects Versions: 3.5.3, 3.4.12 >Reporter: Bogdan Kanivets >Assignee: Bogdan Kanivets >Priority: Minor > Labels: flaky, pull-request-available > Fix For: 3.6.0, 3.4.13, 3.5.5 > > Time Spent: 0.5h > Remaining Estimate: 0h > > According to the > [dashboard|https://builds.apache.org/job/ZooKeeper-Find-Flaky-Tests/lastSuccessfulBuild/artifact/report.html] > testManyChildWatchersAutoReset is flaky in 3.4 and 3.5 > [ZooKeeper_branch34_java10|https://builds.apache.org/job/ZooKeeper_branch34_java10//13] > [ZooKeeper_branch35_java9|https://builds.apache.org/job/ZooKeeper_branch35_java9/253] > Test times out and because of that ant doesn't capture any output. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ZOOKEEPER-1910) RemoveWatches wrongly removes the watcher if multiple watches exists on a path
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-1910: Fix Version/s: (was: 3.6.0) > RemoveWatches wrongly removes the watcher if multiple watches exists on a path > -- > > Key: ZOOKEEPER-1910 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1910 > Project: ZooKeeper > Issue Type: Bug > Components: java client, server >Reporter: Rakesh R >Assignee: Rakesh R >Priority: Major > Fix For: 3.5.0 > > Attachments: ZOOKEEPER-1910.patch, ZOOKEEPER-1910.patch, > ZOOKEEPER-1910.patch, ZOOKEEPER-1910.patch > > > Consider a case where zkclient has added 2 data watchers(say 'w1' and 'w2') > on '/node1'. > Now user has removed w1, but this is deleting the 'CnxnWatcher' in ZK server > against the "/node1" path. This will affect other data watchers(if any) of > same client on same path. In our case 'w2' would not be notified. > Note: please see the attached test case to understand more. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ZOOKEEPER-1910) RemoveWatches wrongly removes the watcher if multiple watches exists on a path
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-1910: Fix Version/s: 3.6.0 > RemoveWatches wrongly removes the watcher if multiple watches exists on a path > -- > > Key: ZOOKEEPER-1910 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1910 > Project: ZooKeeper > Issue Type: Bug > Components: java client, server >Reporter: Rakesh R >Assignee: Rakesh R >Priority: Major > Fix For: 3.5.0, 3.6.0 > > Attachments: ZOOKEEPER-1910.patch, ZOOKEEPER-1910.patch, > ZOOKEEPER-1910.patch, ZOOKEEPER-1910.patch > > > Consider a case where zkclient has added 2 data watchers(say 'w1' and 'w2') > on '/node1'. > Now user has removed w1, but this is deleting the 'CnxnWatcher' in ZK server > against the "/node1" path. This will affect other data watchers(if any) of > same client on same path. In our case 'w2' would not be notified. > Note: please see the attached test case to understand more. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Success: ZOOKEEPER- PreCommit Build #1766
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1766/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 82.04 MB...] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] +1 tests included. The patch appears to include 3 new or modified tests. [exec] [exec] +1 javadoc. The javadoc tool did not generate any warning messages. [exec] [exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings. [exec] [exec] +1 findbugs. The patch does not introduce any new Findbugs (version 3.0.1) warnings. [exec] [exec] +1 release audit. The applied patch does not increase the total number of release audit warnings. [exec] [exec] +1 core tests. The patch passed core unit tests. [exec] [exec] +1 contrib tests. The patch passed contrib unit tests. [exec] [exec] Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1766//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1766//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1766//console [exec] [exec] This message is automatically generated. [exec] [exec] [exec] == [exec] == [exec] Adding comment to Jira. [exec] == [exec] == [exec] [exec] [exec] Comment with id 16493732 added to ZOOKEEPER-2184. [exec] Session logged out. Session was JSESSIONID=3AEC897009EFB90BD6C8F504EE3331B4. [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] [exec] mv: '/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess' and '/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess' are the same file BUILD SUCCESSFUL Total time: 17 minutes 4 seconds Archiving artifacts Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Recording test results Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 [description-setter] Description set: ZOOKEEPER-2184 Putting comment on the pull request Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Email was triggered for: Success Sending email for trigger: Success Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 ### ## FAILED TESTS (if any) ## All tests passed
[jira] [Commented] (ZOOKEEPER-2184) Zookeeper Client should re-resolve hosts when connection attempts fail
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493732#comment-16493732 ] Hadoop QA commented on ZOOKEEPER-2184: -- +1 overall. GitHub Pull Request Build +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 3.0.1) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1766//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1766//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1766//console This message is automatically generated. > Zookeeper Client should re-resolve hosts when connection attempts fail > -- > > Key: ZOOKEEPER-2184 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2184 > Project: ZooKeeper > Issue Type: Bug > Components: java client >Affects Versions: 3.4.6, 3.4.7, 3.4.8, 3.4.9, 3.4.10, 3.5.0, 3.5.1, 3.5.2, > 3.5.3, 3.4.11 > Environment: Ubuntu 14.04 host, Docker containers for Zookeeper & > Kafka >Reporter: Robert P. Thille >Assignee: Andor Molnar >Priority: Blocker > Labels: easyfix, patch, pull-request-available > Fix For: 3.6.0, 3.4.13, 3.5.5 > > Attachments: ZOOKEEPER-2184.patch > > Time Spent: 4h 50m > Remaining Estimate: 0h > > Testing in a Docker environment with a single Kafka instance using a single > Zookeeper instance. Restarting the Zookeeper container will cause it to > receive a new IP address. Kafka will never be able to reconnect to Zookeeper > and will hang indefinitely. Updating DNS or /etc/hosts with the new IP > address will not help the client to reconnect as the > zookeeper/client/StaticHostProvider resolves the connection string hosts at > creation time and never re-resolves. > A solution would be for the client to notice that connection attempts fail > and attempt to re-resolve the hostnames in the connectString. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Failed: ZOOKEEPER- PreCommit Build #1765
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1765/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 82.96 MB...] [exec] [exec] +1 javadoc. The javadoc tool did not generate any warning messages. [exec] [exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings. [exec] [exec] +1 findbugs. The patch does not introduce any new Findbugs (version 3.0.1) warnings. [exec] [exec] +1 release audit. The applied patch does not increase the total number of release audit warnings. [exec] [exec] -1 core tests. The patch failed core unit tests. [exec] [exec] +1 contrib tests. The patch passed contrib unit tests. [exec] [exec] Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1765//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1765//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1765//console [exec] [exec] This message is automatically generated. [exec] [exec] [exec] == [exec] == [exec] Adding comment to Jira. [exec] == [exec] == [exec] [exec] [exec] Comment with id 16493723 added to ZOOKEEPER-2184. [exec] Session logged out. Session was JSESSIONID=6AE06EA97FF58B975BFED15E45E26C10. [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] [exec] mv: '/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess' and '/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess' are the same file BUILD FAILED /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build.xml:1737: exec returned: 1 Total time: 17 minutes 26 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Recording test results Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 [description-setter] Description set: ZOOKEEPER-2184 Putting comment on the pull request Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 ### ## FAILED TESTS (if any) ## 1 tests failed. FAILED: org.apache.zookeeper.test.DisconnectedWatcherTest.testManyChildWatchersAutoReset Error Message: test timed out after 60 milliseconds Stack Trace: org.junit.runners.model.TestTimedOutException: test timed out after 60 milliseconds at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:502) at org.apache.zookeeper.ClientCnxn.submitRequest(ClientCnxn.java:1499) at org.apache.zookeeper.ClientCnxn.submitRequest(ClientCnxn.java:1487) at org.apache.zookeeper.ZooKeeper.setData(ZooKeeper.java:2253) at org.apache.zookeeper.test.DisconnectedWatcherTest.testManyChildWatchersAutoReset(DisconnectedWatcherTest.java:243) at org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.lang.Thread.run(Thread.java:748)
[jira] [Commented] (ZOOKEEPER-2184) Zookeeper Client should re-resolve hosts when connection attempts fail
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493723#comment-16493723 ] Hadoop QA commented on ZOOKEEPER-2184: -- -1 overall. GitHub Pull Request Build +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 3.0.1) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1765//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1765//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1765//console This message is automatically generated. > Zookeeper Client should re-resolve hosts when connection attempts fail > -- > > Key: ZOOKEEPER-2184 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2184 > Project: ZooKeeper > Issue Type: Bug > Components: java client >Affects Versions: 3.4.6, 3.4.7, 3.4.8, 3.4.9, 3.4.10, 3.5.0, 3.5.1, 3.5.2, > 3.5.3, 3.4.11 > Environment: Ubuntu 14.04 host, Docker containers for Zookeeper & > Kafka >Reporter: Robert P. Thille >Assignee: Andor Molnar >Priority: Blocker > Labels: easyfix, patch, pull-request-available > Fix For: 3.6.0, 3.4.13, 3.5.5 > > Attachments: ZOOKEEPER-2184.patch > > Time Spent: 4h 50m > Remaining Estimate: 0h > > Testing in a Docker environment with a single Kafka instance using a single > Zookeeper instance. Restarting the Zookeeper container will cause it to > receive a new IP address. Kafka will never be able to reconnect to Zookeeper > and will hang indefinitely. Updating DNS or /etc/hosts with the new IP > address will not help the client to reconnect as the > zookeeper/client/StaticHostProvider resolves the connection string hosts at > creation time and never re-resolves. > A solution would be for the client to notice that connection attempts fail > and attempt to re-resolve the hostnames in the connectString. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] zookeeper pull request #534: ZOOKEEPER-2184 Zookeeper Client should re-resol...
GitHub user anmolnar opened a pull request: https://github.com/apache/zookeeper/pull/534 ZOOKEEPER-2184 Zookeeper Client should re-resolve hosts when connection attempts fail This is the master/3.5 port of #451 You can merge this pull request into a Git repository by running: $ git pull https://github.com/anmolnar/zookeeper ZOOKEEPER-2184_master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zookeeper/pull/534.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #534 commit 98ea0044ebf7c3773d10001b7ace8e8e74ec94ce Author: Andor Molnar Date: 2018-05-29T15:19:15Z ZOOKEEPER-2184. Ported the patch from branch-3.4 ---
Re: Maven migration doc - thoughts and suggestions
Sorry, one important clarification: These are not decided yet, in the contrary, the main goal would be to have a discussion about these (and more) points and arrive to a mutual agreement on how we should do the migration, and to make sure this will not die and forgotten in a pull request somewhere. Norbert On Tue, May 29, 2018 at 4:12 PM Norbert Kalmar wrote: > Thanks Andor! > > A quick update on where were at with the maven migration plan: > - All 3 active branches will get the full maven build. > - End artifacts will change, 3 separate jar for server, client and common, > possible package change as well (backward compatibility will break) > - The changes will be committed to master / 3.5 / 3.4 in smaller > iterations, starting with moving the docs to it's new folder > > Check out the docs for more info, and some explanation why we arrived to > the above conclusions in the above statements. > The link again: > https://docs.google.com/document/d/1WXqhaPlCwchcWc8RCEzbCmVa4WbBDlfR3GQngikGjqc/edit?usp=sharing > > Regards, > Norbert > > On Mon, May 28, 2018 at 1:09 PM Andor Molnar wrote: > >> Excellent job Norbert, this doc will be very useful to discuss all kinds >> of >> aspects of the migration. >> I've left some comments already. >> >> Thanks, >> Andor >> >> >> >> On Fri, May 25, 2018 at 3:14 PM, Norbert Kalmar >> wrote: >> >> > Hi, >> > >> > After doing some proof of work and had some discussion, I have created a >> > google docs about the maven migration. >> > >> > Please read through, and comment your thoughts and suggestions. >> > >> > https://docs.google.com/document/d/1WXqhaPlCwchcWc8RCEzbCmVa4WbBD >> > lfR3GQngikGjqc/edit?usp=sharing >> > >> > >> > Thanks! >> > Norbert >> > >> >
Re: Maven migration doc - thoughts and suggestions
Thanks Andor! A quick update on where were at with the maven migration plan: - All 3 active branches will get the full maven build. - End artifacts will change, 3 separate jar for server, client and common, possible package change as well (backward compatibility will break) - The changes will be committed to master / 3.5 / 3.4 in smaller iterations, starting with moving the docs to it's new folder Check out the docs for more info, and some explanation why we arrived to the above conclusions in the above statements. The link again: https://docs.google.com/document/d/1WXqhaPlCwchcWc8RCEzbCmVa4WbBDlfR3GQngikGjqc/edit?usp=sharing Regards, Norbert On Mon, May 28, 2018 at 1:09 PM Andor Molnar wrote: > Excellent job Norbert, this doc will be very useful to discuss all kinds of > aspects of the migration. > I've left some comments already. > > Thanks, > Andor > > > > On Fri, May 25, 2018 at 3:14 PM, Norbert Kalmar > wrote: > > > Hi, > > > > After doing some proof of work and had some discussion, I have created a > > google docs about the maven migration. > > > > Please read through, and comment your thoughts and suggestions. > > > > https://docs.google.com/document/d/1WXqhaPlCwchcWc8RCEzbCmVa4WbBD > > lfR3GQngikGjqc/edit?usp=sharing > > > > > > Thanks! > > Norbert > > >
ZooKeeper_branch35_jdk8 - Build # 983 - Still Failing
See https://builds.apache.org/job/ZooKeeper_branch35_jdk8/983/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 61.30 KB...] [junit] Running org.apache.zookeeper.test.ServerCnxnTest in thread 6 [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.259 sec, Thread: 4, Class: org.apache.zookeeper.test.SaslSuperUserTest [junit] Running org.apache.zookeeper.test.SessionInvalidationTest in thread 4 [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.337 sec, Thread: 6, Class: org.apache.zookeeper.test.ServerCnxnTest [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.687 sec, Thread: 4, Class: org.apache.zookeeper.test.SessionInvalidationTest [junit] Running org.apache.zookeeper.test.SessionTest in thread 6 [junit] Running org.apache.zookeeper.test.SessionTimeoutTest in thread 4 [junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.366 sec, Thread: 4, Class: org.apache.zookeeper.test.SessionTimeoutTest [junit] Running org.apache.zookeeper.test.SessionTrackerCheckTest in thread 4 [junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.08 sec, Thread: 4, Class: org.apache.zookeeper.test.SessionTrackerCheckTest [junit] Running org.apache.zookeeper.test.SessionUpgradeTest in thread 4 [junit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.805 sec, Thread: 6, Class: org.apache.zookeeper.test.SessionTest [junit] Running org.apache.zookeeper.test.StandaloneTest in thread 6 [junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.693 sec, Thread: 6, Class: org.apache.zookeeper.test.StandaloneTest [junit] Running org.apache.zookeeper.test.StatTest in thread 6 [junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.632 sec, Thread: 6, Class: org.apache.zookeeper.test.StatTest [junit] Running org.apache.zookeeper.test.StaticHostProviderTest in thread 6 [junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 19.191 sec, Thread: 4, Class: org.apache.zookeeper.test.SessionUpgradeTest [junit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.83 sec, Thread: 6, Class: org.apache.zookeeper.test.StaticHostProviderTest [junit] Running org.apache.zookeeper.test.StringUtilTest in thread 6 [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.058 sec, Thread: 6, Class: org.apache.zookeeper.test.StringUtilTest [junit] Running org.apache.zookeeper.test.SyncCallTest in thread 4 [junit] Running org.apache.zookeeper.test.TruncateTest in thread 6 [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.724 sec, Thread: 4, Class: org.apache.zookeeper.test.SyncCallTest [junit] Running org.apache.zookeeper.test.WatchEventWhenAutoResetTest in thread 4 [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 176.48 sec, Thread: 7, Class: org.apache.zookeeper.test.RecoveryTest [junit] Running org.apache.zookeeper.test.WatchedEventTest in thread 7 [junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.117 sec, Thread: 7, Class: org.apache.zookeeper.test.WatchedEventTest [junit] Running org.apache.zookeeper.test.WatcherFuncTest in thread 7 [junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 19.639 sec, Thread: 4, Class: org.apache.zookeeper.test.WatchEventWhenAutoResetTest [junit] Running org.apache.zookeeper.test.WatcherTest in thread 4 [junit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.319 sec, Thread: 7, Class: org.apache.zookeeper.test.WatcherFuncTest [junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 23.244 sec, Thread: 6, Class: org.apache.zookeeper.test.TruncateTest [junit] Running org.apache.zookeeper.test.X509AuthTest in thread 6 [junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.092 sec, Thread: 6, Class: org.apache.zookeeper.test.X509AuthTest [junit] Running org.apache.zookeeper.test.ZkDatabaseCorruptionTest in thread 7 [junit] Running org.apache.zookeeper.test.ZooKeeperQuotaTest in thread 6 [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.186 sec, Thread: 6, Class: org.apache.zookeeper.test.ZooKeeperQuotaTest [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 143.49 sec, Thread: 5, Class: org.apache.zookeeper.test.RestoreCommittedLogTest [junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 15.016 sec, Thread: 7, Class: org.apache.zookeeper.test.ZkDatabaseCorruptionTest [junit] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 31.288 sec, Thread: 4, Class: org.apache.zookeeper.test.WatcherTest
[jira] [Updated] (ZOOKEEPER-2184) Zookeeper Client should re-resolve hosts when connection attempts fail
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andor Molnar updated ZOOKEEPER-2184: Fix Version/s: 3.5.5 3.4.13 3.6.0 > Zookeeper Client should re-resolve hosts when connection attempts fail > -- > > Key: ZOOKEEPER-2184 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2184 > Project: ZooKeeper > Issue Type: Bug > Components: java client >Affects Versions: 3.4.6, 3.4.7, 3.4.8, 3.4.9, 3.4.10, 3.5.0, 3.5.1, 3.5.2, > 3.5.3, 3.4.11 > Environment: Ubuntu 14.04 host, Docker containers for Zookeeper & > Kafka >Reporter: Robert P. Thille >Assignee: Andor Molnar >Priority: Blocker > Labels: easyfix, patch, pull-request-available > Fix For: 3.6.0, 3.4.13, 3.5.5 > > Attachments: ZOOKEEPER-2184.patch > > Time Spent: 4h 40m > Remaining Estimate: 0h > > Testing in a Docker environment with a single Kafka instance using a single > Zookeeper instance. Restarting the Zookeeper container will cause it to > receive a new IP address. Kafka will never be able to reconnect to Zookeeper > and will hang indefinitely. Updating DNS or /etc/hosts with the new IP > address will not help the client to reconnect as the > zookeeper/client/StaticHostProvider resolves the connection string hosts at > creation time and never re-resolves. > A solution would be for the client to notice that connection attempts fail > and attempt to re-resolve the hostnames in the connectString. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
