[jira] [Updated] (ZOOKEEPER-2843) auth_to_local should support reading rules from a file
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lionel Cons updated ZOOKEEPER-2843:
---
Description:
The current handling of {{zookeeper.security.auth_to_local}} in
{{KerberosName.java}} only supports rules given directly as property value.
These rules must therefore be given on the command line and:
* must be escaped properly to avoid shell expansion
* are visible in the {{ps}} output
It would be much better to put these rules in a file and pass the file path as
the property value. We would then use something like
{{-Dzookeeper.security.auth_to_local=file:/etc/zookeeper/rules}}.
Note that using the {{file:}} prefix allows keeping backward compatibility.
was:
The current handling of {{zookeeper.security.auth_to_local}} in
{{KerberosName.java}} only support rules given directly as the property value.
These rules must therefore be given on the command line and:
* must be escaped properly to avoid shell expansion
* are visible in the {{ps}} output
It would be much better to put these rules in a file and pass the file path as
the property value. We would then use something like
{{-Dzookeeper.security.auth_to_local=file:/etc/zookeeper/rules}}.
Note that using the {{file:}} prefix allows keeping backward compatibility.
> auth_to_local should support reading rules from a file
> --
>
> Key: ZOOKEEPER-2843
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2843
> Project: ZooKeeper
> Issue Type: Improvement
>Reporter: Lionel Cons
> Attachments: ZOOKEEPER-2843.patch
>
>
> The current handling of {{zookeeper.security.auth_to_local}} in
> {{KerberosName.java}} only supports rules given directly as property value.
> These rules must therefore be given on the command line and:
> * must be escaped properly to avoid shell expansion
> * are visible in the {{ps}} output
> It would be much better to put these rules in a file and pass the file path
> as the property value. We would then use something like
> {{-Dzookeeper.security.auth_to_local=file:/etc/zookeeper/rules}}.
> Note that using the {{file:}} prefix allows keeping backward compatibility.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (ZOOKEEPER-2858) Disable reverse DNS lookup for java client
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16108337#comment-16108337 ] caixiaofeng commented on ZOOKEEPER-2858: can also http://docs.oracle.com/javase/7/docs/technotes/guides/net/properties.html *sun.net.spi.nameservice.provider.=S*pecifies the name service provider that you can use. By default, Java will use the system configured name lookup mechanism, such as file, nis, etc. You can specify your own by setting this option. takes the value of a positive number, it indicates the precedence order with a small number takes higher precendence over a bigger number. Aside from the default provider, the JDK includes a DNS provider named "dns,sun". Prior to JDK 7, the first provider that was successfully loaded was used. In JDK 7, providers are chained, which means that if a lookup on a provider fails, the next provider in the list is consulted to resolve the name. > Disable reverse DNS lookup for java client > -- > > Key: ZOOKEEPER-2858 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2858 > Project: ZooKeeper > Issue Type: New Feature > Components: java client >Affects Versions: 3.4.6 >Reporter: Andrey > > I have the following setup: > - zookeeper server running in docker container > - kerberos auth > When client setup sasl connection it creates service principal name as: > - "principalUserName+"/"+addr.getHostName()", > where: > - addr.getHostName is the reverse DNS of original server host. > If zookeeper nodes will be deployed behind the firewall or software defined > network (the docker case), then reverse DNS host won't match original server > host. And this is done by design. > If these hosts won't match, then principals won't match and Kerberos auth > will fail. > Is it possible to introduce some configuration parameter to disable reverse > DNS lookups? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ZOOKEEPER-2858) Disable reverse DNS lookup for java client
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16108335#comment-16108335 ] caixiaofeng commented on ZOOKEEPER-2858: u can try to use https://issues.apache.org/jira/browse/ZOOKEEPER-1467 and server.principal set on both side of client and server. > Disable reverse DNS lookup for java client > -- > > Key: ZOOKEEPER-2858 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2858 > Project: ZooKeeper > Issue Type: New Feature > Components: java client >Affects Versions: 3.4.6 >Reporter: Andrey > > I have the following setup: > - zookeeper server running in docker container > - kerberos auth > When client setup sasl connection it creates service principal name as: > - "principalUserName+"/"+addr.getHostName()", > where: > - addr.getHostName is the reverse DNS of original server host. > If zookeeper nodes will be deployed behind the firewall or software defined > network (the docker case), then reverse DNS host won't match original server > host. And this is done by design. > If these hosts won't match, then principals won't match and Kerberos auth > will fail. > Is it possible to introduce some configuration parameter to disable reverse > DNS lookups? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
ZooKeeper-trunk - Build # 3485 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk/3485/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 66.73 MB...] [junit] 2017-07-31 23:31:18,121 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 55 [junit] 2017-07-31 23:31:18,121 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD testManyChildWatchersAutoReset [junit] 2017-07-31 23:31:18,121 [myid:] - INFO [main:ClientBase@601] - tearDown starting [junit] 2017-07-31 23:31:18,121 [myid:] - INFO [ProcessThread(sid:0 cport:24690)::PrepRequestProcessor@614] - Processed session termination for sessionid: 0x1008799f844 [junit] 2017-07-31 23:31:18,128 [myid:] - INFO [main:ZooKeeper@1332] - Session: 0x1008799f844 closed [junit] 2017-07-31 23:31:18,128 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for session: 0x1008799f844 [junit] 2017-07-31 23:31:18,128 [myid:] - INFO [NIOWorkerThread-5:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port24690,name1=Connections,name2=127.0.0.1,name3=0x1008799f844] [junit] 2017-07-31 23:31:18,129 [myid:] - INFO [ProcessThread(sid:0 cport:24690)::PrepRequestProcessor@614] - Processed session termination for sessionid: 0x1008799f8440001 [junit] 2017-07-31 23:31:18,130 [myid:] - INFO [NIOWorkerThread-5:NIOServerCnxn@627] - Closed socket connection for client /127.0.0.1:41581 which had sessionid 0x1008799f844 [junit] 2017-07-31 23:31:18,137 [myid:] - INFO [main:ZooKeeper@1332] - Session: 0x1008799f8440001 closed [junit] 2017-07-31 23:31:18,137 [myid:] - INFO [NIOWorkerThread-26:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port24690,name1=Connections,name2=127.0.0.1,name3=0x1008799f8440001] [junit] 2017-07-31 23:31:18,137 [myid:] - INFO [main:ClientBase@571] - STOPPING server [junit] 2017-07-31 23:31:18,137 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for session: 0x1008799f8440001 [junit] 2017-07-31 23:31:18,138 [myid:] - INFO [ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - ConnnectionExpirerThread interrupted [junit] 2017-07-31 23:31:18,137 [myid:] - INFO [NIOWorkerThread-26:NIOServerCnxn@627] - Closed socket connection for client /127.0.0.1:41599 which had sessionid 0x1008799f8440001 [junit] 2017-07-31 23:31:18,140 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2017-07-31 23:31:18,140 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:24690:NIOServerCnxnFactory$AcceptThread@219] - accept thread exitted run method [junit] 2017-07-31 23:31:18,141 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2017-07-31 23:31:18,141 [myid:] - INFO [main:ZooKeeperServer@541] - shutting down [junit] 2017-07-31 23:31:18,141 [myid:] - ERROR [main:ZooKeeperServer@505] - ZKShutdownHandler is not registered, so ZooKeeper server won't take any action on ERROR or SHUTDOWN server state changes [junit] 2017-07-31 23:31:18,142 [myid:] - INFO [main:SessionTrackerImpl@232] - Shutting down [junit] 2017-07-31 23:31:18,142 [myid:] - INFO [main:PrepRequestProcessor@1008] - Shutting down [junit] 2017-07-31 23:31:18,142 [myid:] - INFO [main:SyncRequestProcessor@191] - Shutting down [junit] 2017-07-31 23:31:18,142 [myid:] - INFO [ProcessThread(sid:0 cport:24690)::PrepRequestProcessor@155] - PrepRequestProcessor exited loop! [junit] 2017-07-31 23:31:18,142 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited! [junit] 2017-07-31 23:31:18,142 [myid:] - INFO [main:FinalRequestProcessor@481] - shutdown of request processor complete [junit] 2017-07-31 23:31:18,143 [myid:] - INFO [main:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port24690,name1=InMemoryDataTree] [junit] 2017-07-31 23:31:18,143 [myid:] - INFO [main:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port24690] [junit] 2017-07-31 23:31:18,143 [myid:] - INFO [main:FourLetterWordMain@87] - connecting to 127.0.0.1 24690 [junit] 2017-07-31 23:31:18,144 [myid:] - INFO [main:JMXEnv@146] - ensureOnly:[] [junit] 2017-07-31 23:31:18,197 [myid:] - INFO [main:ClientBase@626] - fdcount after test is: 54 at start it was 54 [junit] 2017-07-31 23:31:18,198 [myid:] - INFO [main:ZKTestCase$1@68] - SUCCEEDED testManyChildWatchersAutoReset [junit] 2017-07-31 23:31:18,198 [myid:] - INFO [main:ZKTestCase$1@63
ZooKeeper_branch34_jdk8 - Build # 1080 - Still Failing
See https://builds.apache.org/job/ZooKeeper_branch34_jdk8/1080/
###
## LAST 60 LINES OF THE CONSOLE
###
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H22 (couchdbtest ubuntu xenial) in workspace
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk8
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url git://git.apache.org/zookeeper.git # timeout=10
Cleaning workspace
> git rev-parse --verify HEAD # timeout=10
Resetting working tree
> git reset --hard # timeout=10
> git clean -fdx # timeout=10
Fetching upstream changes from git://git.apache.org/zookeeper.git
> git --version # timeout=10
> git fetch --tags --progress git://git.apache.org/zookeeper.git
> +refs/heads/*:refs/remotes/origin/*
> git rev-parse refs/remotes/origin/branch-3.4^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/branch-3.4^{commit} # timeout=10
Checking out Revision 76553b0ca69dbd9439b46ec318d1b04bc0e14f1f
(refs/remotes/origin/branch-3.4)
Commit message: "ZOOKEEPER-2829: Interface usability / compatibility
improvements through Java annotation."
> git config core.sparsecheckout # timeout=10
> git checkout -f 76553b0ca69dbd9439b46ec318d1b04bc0e14f1f
> git rev-list 76553b0ca69dbd9439b46ec318d1b04bc0e14f1f # timeout=10
No emails were triggered.
[ZooKeeper_branch34_jdk8] $ ant -Dtest.output=yes -Dtest.junit.threads=8
-Dtest.junit.output.format=xml -Djavac.target=1.8 clean test-core-java
Error occurred during initialization of VM
java.lang.OutOfMemoryError: unable to create new native thread
Build step 'Invoke Ant' marked build as failure
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files
were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
###
## FAILED TESTS (if any)
##
No tests ran.
[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&focusedCommentId=16107958#comment-16107958 ] ASF GitHub Bot commented on ZOOKEEPER-2184: --- Github user djenriquez commented on the issue: https://github.com/apache/zookeeper/pull/150 Hi guys, any update for this PR? Many thanks!! > 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 > Environment: Ubuntu 14.04 host, Docker containers for Zookeeper & > Kafka >Reporter: Robert P. Thille >Assignee: Flavio Junqueira >Priority: Blocker > Labels: easyfix, patch > Fix For: 3.5.4, 3.4.11 > > Attachments: ZOOKEEPER-2184.patch > > > 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 (v6.4.14#64029)
[GitHub] zookeeper issue #150: ZOOKEEPER-2184: Zookeeper Client should re-resolve hos...
Github user djenriquez commented on the issue: https://github.com/apache/zookeeper/pull/150 Hi guys, any update for this PR? Many thanks!! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
ZooKeeper-trunk-openjdk7 - Build # 1565 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/1565/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 64.68 MB...] [junit] 2017-07-31 20:23:40,659 [myid:127.0.0.1:14044] - WARN [main-SendThread(127.0.0.1:14044):ClientCnxn$SendThread@1235] - Session 0x305c4ed61ad for server 127.0.0.1/127.0.0.1:14044, unexpected error, closing socket connection and attempting reconnect [junit] java.net.ConnectException: Connection refused [junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) [junit] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739) [junit] at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357) [junit] at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214) [junit] 2017-07-31 20:23:41,013 [myid:] - INFO [SessionTracker:SessionTrackerImpl@158] - SessionTrackerImpl exited loop! [junit] 2017-07-31 20:23:41,046 [myid:127.0.0.1:13915] - INFO [main-SendThread(127.0.0.1:13915):ClientCnxn$SendThread@1113] - Opening socket connection to server 127.0.0.1/127.0.0.1:13915. Will not attempt to authenticate using SASL (unknown error) [junit] 2017-07-31 20:23:41,047 [myid:127.0.0.1:13915] - WARN [main-SendThread(127.0.0.1:13915):ClientCnxn$SendThread@1235] - Session 0x105c4ea994e for server 127.0.0.1/127.0.0.1:13915, unexpected error, closing socket connection and attempting reconnect [junit] java.net.ConnectException: Connection refused [junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) [junit] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739) [junit] at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357) [junit] at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214) [junit] 2017-07-31 20:23:41,146 [myid:] - INFO [ProcessThread(sid:0 cport:14161)::PrepRequestProcessor@614] - Processed session termination for sessionid: 0x105c4f0accf [junit] 2017-07-31 20:23:41,148 [myid:] - INFO [SyncThread:0:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port14161,name1=Connections,name2=127.0.0.1,name3=0x105c4f0accf] [junit] 2017-07-31 20:23:41,148 [myid:] - INFO [main:ZooKeeper@1332] - Session: 0x105c4f0accf closed [junit] 2017-07-31 20:23:41,148 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for session: 0x105c4f0accf [junit] 2017-07-31 20:23:41,148 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 220750 [junit] 2017-07-31 20:23:41,148 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 2431 [junit] 2017-07-31 20:23:41,148 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD testWatcherAutoResetWithLocal [junit] 2017-07-31 20:23:41,148 [myid:] - INFO [main:ClientBase@601] - tearDown starting [junit] 2017-07-31 20:23:41,149 [myid:] - INFO [main:ClientBase@571] - STOPPING server [junit] 2017-07-31 20:23:41,149 [myid:] - INFO [main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:14161 [junit] 2017-07-31 20:23:41,154 [myid:] - INFO [main:ZooKeeperServer@541] - shutting down [junit] 2017-07-31 20:23:41,154 [myid:] - ERROR [main:ZooKeeperServer@505] - ZKShutdownHandler is not registered, so ZooKeeper server won't take any action on ERROR or SHUTDOWN server state changes [junit] 2017-07-31 20:23:41,154 [myid:] - INFO [main:SessionTrackerImpl@232] - Shutting down [junit] 2017-07-31 20:23:41,154 [myid:] - INFO [main:PrepRequestProcessor@1008] - Shutting down [junit] 2017-07-31 20:23:41,154 [myid:] - INFO [main:SyncRequestProcessor@191] - Shutting down [junit] 2017-07-31 20:23:41,154 [myid:] - INFO [ProcessThread(sid:0 cport:14161)::PrepRequestProcessor@155] - PrepRequestProcessor exited loop! [junit] 2017-07-31 20:23:41,155 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited! [junit] 2017-07-31 20:23:41,155 [myid:] - INFO [main:FinalRequestProcessor@481] - shutdown of request processor complete [junit] 2017-07-31 20:23:41,155 [myid:] - INFO [main:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port14161,name1=InMemoryDataTree] [junit] 2017-07-31 20:23:41,155 [myid:] - INFO [main:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port14161] [junit] 2017-07-31 20:23:41,155 [myid:] - INFO [main:FourLetterWordMain@87] - connecting to 127.0.0.1 14161 [junit] 2017-07-31 20:23:41,156 [myid:] - INFO [main:JMXEnv@146] - ensureOnly:[] [junit] 2017-07-31 20:23:41,163 [myid:] -
Failed: ZOOKEEPER- PreCommit Build #913
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/913/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 64.90 MB...] [exec] +0 tests included. The patch appears to be a documentation patch that doesn't require tests. [exec] [exec] -1 javadoc. The javadoc tool appears to have generated 8 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/913//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/913//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/913//console [exec] [exec] This message is automatically generated. [exec] [exec] [exec] == [exec] == [exec] Adding comment to Jira. [exec] == [exec] == [exec] [exec] [exec] Comment added. [exec] a9c6ef99709c092f471c8bccd317410f713f7b3b logged out [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:1643: exec returned: 2 Total time: 12 minutes 54 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 Recording test results Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 [description-setter] Description set: ZOOKEEPER-2859 Putting comment on the pull request Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 ### ## FAILED TESTS (if any) ## 1 tests failed. FAILED: org.apache.zookeeper.server.quorum.ReconfigRecoveryTest.testCurrentServersAreObserversInNextConfig Error Message: waiting for server 3 being up Stack Trace: junit.framework.AssertionFailedError: waiting for server 3 being up at org.apache.zookeeper.server.quorum.ReconfigRecoveryTest.testCurrentServersAreObserversInNextConfig(ReconfigRecoveryTest.java:223) at org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
[jira] [Commented] (ZOOKEEPER-2859) CMake build doesn't support OS X
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16107846#comment-16107846 ] Hadoop QA commented on ZOOKEEPER-2859: -- -1 overall. GitHub Pull Request Build +1 @author. The patch does not contain any @author tags. +0 tests included. The patch appears to be a documentation patch that doesn't require tests. -1 javadoc. The javadoc tool appears to have generated 8 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/913//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/913//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/913//console This message is automatically generated. > CMake build doesn't support OS X > > > Key: ZOOKEEPER-2859 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2859 > Project: ZooKeeper > Issue Type: Bug > Environment: OS X 10.12.6 >Reporter: Andrew Schwartzmeyer >Assignee: Andrew Schwartzmeyer > > Couple problems: > libm, librt, and libdl are all Linux specific, and provided "for free" on OS X > CppUnit (at least on OS X) needs `-std=c++11` > clang's ld doesn't understand --wrap > I can post an easy patch that at least lets you build the client (but not the > tests). The tests use that `--wrap` and it's non trivial to fix that on OS X. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
Failed: ZOOKEEPER- PreCommit Build #911
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/911/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 67.94 MB...] [exec] +0 tests included. The patch appears to be a documentation patch that doesn't require tests. [exec] [exec] -1 javadoc. The javadoc tool appears to have generated 8 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/911//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/911//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/911//console [exec] [exec] This message is automatically generated. [exec] [exec] [exec] == [exec] == [exec] Adding comment to Jira. [exec] == [exec] == [exec] [exec] [exec] Comment added. [exec] 5af8cade4f0c9585f9f441448ab9a5f4ee62cf1f logged out [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:1643: exec returned: 2 Total time: 12 minutes 46 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 Recording test results Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 [description-setter] Description set: ZOOKEEPER-2852 Putting comment on the pull request Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 ### ## FAILED TESTS (if any) ## 1 tests failed. FAILED: org.apache.zookeeper.server.quorum.ReconfigRecoveryTest.testCurrentServersAreObserversInNextConfig Error Message: waiting for server 3 being up Stack Trace: junit.framework.AssertionFailedError: waiting for server 3 being up at org.apache.zookeeper.server.quorum.ReconfigRecoveryTest.testCurrentServersAreObserversInNextConfig(ReconfigRecoveryTest.java:223) at org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
[jira] [Commented] (ZOOKEEPER-2852) Snapshot size factor is not read from system property
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16107811#comment-16107811 ] Hadoop QA commented on ZOOKEEPER-2852: -- -1 overall. GitHub Pull Request Build +1 @author. The patch does not contain any @author tags. +0 tests included. The patch appears to be a documentation patch that doesn't require tests. -1 javadoc. The javadoc tool appears to have generated 8 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/911//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/911//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/911//console This message is automatically generated. > Snapshot size factor is not read from system property > - > > Key: ZOOKEEPER-2852 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2852 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.3, 3.6.0 >Reporter: Fangmin Lv >Assignee: Fangmin Lv > > There is data inconsistency issue found when leader is using on disk txn > files to sync with learner: ZOOKEEPER-2846, tried to disable this feature by > setting zookeeper.snapshotSizeFactor system property, but found this system > property is not being read anywhere. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ZOOKEEPER-2846) Leader follower sync with on disk txns can possibly leads to data inconsistency
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16107796#comment-16107796 ] Fangmin Lv commented on ZOOKEEPER-2846: --- There could be txn gap when using diff sync (which won't happen in our internal branch), since we don't log txns to txn file before taking snapshot, so this issue could happen more frequently in the open source version, any suggestion except disable the on disk txn sync for now? > Leader follower sync with on disk txns can possibly leads to data > inconsistency > --- > > Key: ZOOKEEPER-2846 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2846 > Project: ZooKeeper > Issue Type: Bug > Components: quorum >Affects Versions: 3.4.10, 3.5.3, 3.6.0 >Reporter: Fangmin Lv >Priority: Critical > > On disk txn sync could cause data inconsistency if the current leader just > had a snap sync before it became leader, and then having diff sync with its > followers may synced the txns gap on disk. Here is scenario: > Let's say S0 - S3 are followers, and S4 is leader at the beginning: > 1. Stop S2 and send one more request > 2. Stop S3 and send more requests to the quorum to let S3 have a snap sync > with S4 when it started up > 3. Stop S4 and S3 became the new leader > 4. Start S2 and had a diff sync with S3, now there are gaps in S2 > Attached the test case to verify the issue. Currently, there is no efficient > way to check the gap in txn files is a real gap or due to Epoch change. We > need to add that support, but before that, it would be safer to disable the > on disk txn leader-follower sync. > Another two scenarios which could cause the same issue: > (Scenario 1) Server A, B, C, A is leader, the others are followers: > 1). A synced to disk, but the other 2 restarted before receiving the > proposal > 2). B and C formed quorum, B is leader, and committed some requests > 3). A looking again, and sync with B, B won't able to trunc A but send snap > instead, and leaves the extra txn in A's txn file > 4). A became new leader, and someone else has a diff sync with A it will > have the extra txn > (Scenario 2) Diff sync with committed txn, will only apply to data tree but > not on disk txn file, which will also leave hole in it and lead to data > inconsistency issue when syncing with learners. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
Failed: ZOOKEEPER- PreCommit Build #912
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/912/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 3.17 KB...] [exec] Pull request id: 322 [exec] Pull request title: [ZOOKEEPER-2853] Update lastZxidSeen in FileTxnLog [exec] % Total% Received % Xferd Average Speed TimeTime Time Current [exec] Defect number: ZOOKEEPER-2853 Dload Upload Total SpentLeft Speed [exec] [exec] [exec] - Parsed args, going to checkout - [exec] [exec] [exec] == [exec] == [exec] Testing patch for pull request 322. [exec] == [exec] == [exec] [exec] [exec] [exec] 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0100 1410 1410 0516 0 --:--:-- --:--:-- --:--:-- 518 [exec] [exec] [exec] == [exec] == [exec] Pre-build trunk to verify trunk stability and javac warnings [exec] == [exec] == [exec] [exec] [exec] /home/jenkins/tools/ant/apache-ant-1.9.9/bin/ant -Djavac.args=-Xlint -Xmaxwarns 1000 -Djava5.home=/home/jenkins/tools/java5/latest -Dforrest.home=/home/jenkins/tools/forrest/latest -DZookeeperPatchProcess= clean tar > /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess/trunkJavacWarnings.txt 2>&1 [exec] Trunk compilation is broken? [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] [exec] 0 00 67180 0 13700 0 --:--:-- --:--:-- --:--:-- 13700mv: ‘/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:1643: exec returned: 1 Total time: 12 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 Recording test results Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 [description-setter] Description set: ZOOKEEPER-2853 Putting comment on the pull request Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 ### ## FAILED TESTS (if any) ## No tests ran.
[jira] [Commented] (ZOOKEEPER-2853) The lastZxidSeen in FileTxnLog.java is never being assigned
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16107790#comment-16107790 ] ASF GitHub Bot commented on ZOOKEEPER-2853: --- GitHub user lvfangmin opened a pull request: https://github.com/apache/zookeeper/pull/322 [ZOOKEEPER-2853] Update lastZxidSeen in FileTxnLog You can merge this pull request into a Git repository by running: $ git pull https://github.com/lvfangmin/zookeeper ZOOKEEPER-2853 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zookeeper/pull/322.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 #322 commit 3e59b28d70439a88847f90beec8be1d48464f161 Author: Fangmin Lyu Date: 2017-07-31T19:02:33Z [ZOOKEEPER-2853] Update lastZxidSeen in FileTxnLog > The lastZxidSeen in FileTxnLog.java is never being assigned > --- > > Key: ZOOKEEPER-2853 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2853 > Project: ZooKeeper > Issue Type: Bug > Components: server >Reporter: Fangmin Lv >Assignee: Fangmin Lv >Priority: Minor > Fix For: 3.4.10, 3.5.3, 3.6.0 > > > There is log in FileTxnLog#append to track the txn with smaller zxid than the > last seen, but the lastZxidSeen is never being assigned, so that log is not > printed when it's happened. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] zookeeper pull request #322: [ZOOKEEPER-2853] Update lastZxidSeen in FileTxn...
GitHub user lvfangmin opened a pull request: https://github.com/apache/zookeeper/pull/322 [ZOOKEEPER-2853] Update lastZxidSeen in FileTxnLog You can merge this pull request into a Git repository by running: $ git pull https://github.com/lvfangmin/zookeeper ZOOKEEPER-2853 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zookeeper/pull/322.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 #322 commit 3e59b28d70439a88847f90beec8be1d48464f161 Author: Fangmin Lyu Date: 2017-07-31T19:02:33Z [ZOOKEEPER-2853] Update lastZxidSeen in FileTxnLog --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (ZOOKEEPER-2853) The lastZxidSeen in FileTxnLog.java is never being assigned
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16107782#comment-16107782 ] Fangmin Lv commented on ZOOKEEPER-2853: --- [~maoling] yes, that's what we're doing, I'll provide a PR. > The lastZxidSeen in FileTxnLog.java is never being assigned > --- > > Key: ZOOKEEPER-2853 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2853 > Project: ZooKeeper > Issue Type: Bug > Components: server >Reporter: Fangmin Lv >Assignee: Fangmin Lv >Priority: Minor > Fix For: 3.4.10, 3.5.3, 3.6.0 > > > There is log in FileTxnLog#append to track the txn with smaller zxid than the > last seen, but the lastZxidSeen is never being assigned, so that log is not > printed when it's happened. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ZOOKEEPER-2852) Snapshot size factor is not read from system property
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16107781#comment-16107781 ] ASF GitHub Bot commented on ZOOKEEPER-2852: --- GitHub user lvfangmin opened a pull request: https://github.com/apache/zookeeper/pull/321 [ZOOKEEPER-2852] Read snapshotSizeFactor from system property You can merge this pull request into a Git repository by running: $ git pull https://github.com/lvfangmin/zookeeper ZOOKEEPER-2852 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zookeeper/pull/321.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 #321 commit 07161f36aa63c1ab5abd2753d6e1d734a51d318c Author: Fangmin Lyu Date: 2017-07-31T18:56:14Z read snapshotSizeFactor from system property > Snapshot size factor is not read from system property > - > > Key: ZOOKEEPER-2852 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2852 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.3, 3.6.0 >Reporter: Fangmin Lv >Assignee: Fangmin Lv > > There is data inconsistency issue found when leader is using on disk txn > files to sync with learner: ZOOKEEPER-2846, tried to disable this feature by > setting zookeeper.snapshotSizeFactor system property, but found this system > property is not being read anywhere. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] zookeeper pull request #321: [ZOOKEEPER-2852] Read snapshotSizeFactor from s...
GitHub user lvfangmin opened a pull request: https://github.com/apache/zookeeper/pull/321 [ZOOKEEPER-2852] Read snapshotSizeFactor from system property You can merge this pull request into a Git repository by running: $ git pull https://github.com/lvfangmin/zookeeper ZOOKEEPER-2852 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zookeeper/pull/321.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 #321 commit 07161f36aa63c1ab5abd2753d6e1d734a51d318c Author: Fangmin Lyu Date: 2017-07-31T18:56:14Z read snapshotSizeFactor from system property --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (ZOOKEEPER-2614) Port ZOOKEEPER-1576 to branch3.4
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16107699#comment-16107699 ] ASF GitHub Bot commented on ZOOKEEPER-2614: --- Github user eribeiro commented on the issue: https://github.com/apache/zookeeper/pull/320 LGTM, that is, on par with the version on `master/branch-3.5`. Wdyt @hanm ? > Port ZOOKEEPER-1576 to branch3.4 > > > Key: ZOOKEEPER-2614 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2614 > Project: ZooKeeper > Issue Type: Bug >Affects Versions: 3.4.9 >Reporter: Vishal Khandelwal >Assignee: Vishal Khandelwal > Fix For: 3.4.11 > > Attachments: ZOOKEEPER-2614.branch-3.4.00.patch > > > ZOOKEEPER-1576 handles UnknownHostException and it good to have this change > for 3.4 branch as well. Porting the changes to 3.4 after resolving the > conflicts -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] zookeeper issue #320: ZOOKEEPER-2614 Port ZOOKEEPER-1576 to branch 3.4
Github user eribeiro commented on the issue: https://github.com/apache/zookeeper/pull/320 LGTM, that is, on par with the version on `master/branch-3.5`. Wdyt @hanm ? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
ZooKeeper_branch34_openjdk7 - Build # 1594 - Failure
See https://builds.apache.org/job/ZooKeeper_branch34_openjdk7/1594/
###
## LAST 60 LINES OF THE CONSOLE
###
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on qnode1 (ubuntu) in workspace
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_openjdk7
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url git://git.apache.org/zookeeper.git # timeout=10
Cleaning workspace
> git rev-parse --verify HEAD # timeout=10
Resetting working tree
> git reset --hard # timeout=10
> git clean -fdx # timeout=10
Fetching upstream changes from git://git.apache.org/zookeeper.git
> git --version # timeout=10
> git fetch --tags --progress git://git.apache.org/zookeeper.git
> +refs/heads/*:refs/remotes/origin/*
> git rev-parse refs/remotes/origin/branch-3.4^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/branch-3.4^{commit} # timeout=10
Checking out Revision 76553b0ca69dbd9439b46ec318d1b04bc0e14f1f
(refs/remotes/origin/branch-3.4)
Commit message: "ZOOKEEPER-2829: Interface usability / compatibility
improvements through Java annotation."
> git config core.sparsecheckout # timeout=10
> git checkout -f 76553b0ca69dbd9439b46ec318d1b04bc0e14f1f
> git rev-list 76553b0ca69dbd9439b46ec318d1b04bc0e14f1f # timeout=10
No emails were triggered.
[ZooKeeper_branch34_openjdk7] $
/home/jenkins/tools/ant/apache-ant-1.9.9/bin/ant -Dtest.output=yes
-Dtest.junit.threads=8 -Dtest.junit.output.format=xml -Djavac.target=1.7 clean
test-core-java
Error: JAVA_HOME is not defined correctly.
We cannot execute /usr/lib/jvm/java-7-openjdk-amd64//bin/java
Build step 'Invoke Ant' marked build as failure
Recording test results
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files
were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
###
## FAILED TESTS (if any)
##
No tests ran.
auth_to_local should support reading rules from a file
The current handling of zookeeper.security.auth_to_local in KerberosName.java only supports rules given directly as the property value. These rules must therefore be given on the command line and: - must be escaped properly to avoid shell expansion - are visible in the ps output It would be much better to put these rules in a file and pass the file path as the property value. We would then use something like: | -Dzookeeper.security.auth_to_local=file:/etc/zookeeper/rules Note that using the file: prefix allows keeping backward compatibility. I've created https://issues.apache.org/jira/browse/ZOOKEEPER-2843 and attached a patch to add this functionality. Would it be possible to get this in 3.4.11? Cheers, Lionel
[jira] [Commented] (ZOOKEEPER-2614) Port ZOOKEEPER-1576 to branch3.4
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16107355#comment-16107355 ] ASF GitHub Bot commented on ZOOKEEPER-2614: --- Github user tschuettel commented on the issue: https://github.com/apache/zookeeper/pull/320 I fixed the indentation problem. Please check again. > Port ZOOKEEPER-1576 to branch3.4 > > > Key: ZOOKEEPER-2614 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2614 > Project: ZooKeeper > Issue Type: Bug >Affects Versions: 3.4.9 >Reporter: Vishal Khandelwal >Assignee: Vishal Khandelwal > Fix For: 3.4.11 > > Attachments: ZOOKEEPER-2614.branch-3.4.00.patch > > > ZOOKEEPER-1576 handles UnknownHostException and it good to have this change > for 3.4 branch as well. Porting the changes to 3.4 after resolving the > conflicts -- This message was sent by Atlassian JIRA (v6.4.14#64029)
Failed: ZOOKEEPER-1416 PreCommit Build #3640
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1416
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3640/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 896 B...]
> git rev-parse refs/remotes/origin/master^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 0cb4011dac7ec28637426cafd98b4f8f299ef61d
(refs/remotes/origin/master)
Commit message: "ZOOKEEPER-2829: Interface usability / compatibility
improvements through Java annotation."
> git config core.sparsecheckout # timeout=10
> git checkout -f 0cb4011dac7ec28637426cafd98b4f8f299ef61d
> git rev-list f60928787a908f358a64763f802a6d0371ad4404 # timeout=10
No emails were triggered.
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[PreCommit-ZOOKEEPER-Build] $ /bin/bash /tmp/jenkins6641791762689082743.sh
/home/jenkins/tools/java/latest1.7/bin/java
java version "1.7.0_80"
Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 386177
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 6
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 10240
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
Exception in thread "main" java.lang.UnsupportedClassVersionError:
org/apache/tools/ant/launch/Launcher : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
ERROR: Step ?Publish JUnit test result report? failed: No test report files
were found. Configuration error?
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Description set: ZOOKEEPER-2829
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
###
## FAILED TESTS (if any)
##
No tests ran.
[GitHub] zookeeper issue #320: ZOOKEEPER-2614 Port ZOOKEEPER-1576 to branch 3.4
Github user tschuettel commented on the issue: https://github.com/apache/zookeeper/pull/320 I fixed the indentation problem. Please check again. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (ZOOKEEPER-1416) Persistent Recursive Watch
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16107349#comment-16107349 ] Jordan Zimmerman commented on ZOOKEEPER-1416: - [~hanm] This issue now has 13 votes - what can I do to get this merged? We had an issue over the weekend where the number of watches grew in the millions. This patch would make that situation never happen. > Persistent Recursive Watch > -- > > Key: ZOOKEEPER-1416 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1416 > Project: ZooKeeper > Issue Type: Improvement > Components: c client, documentation, java client, server >Reporter: Phillip Liu >Assignee: Jordan Zimmerman > Attachments: ZOOKEEPER-1416.patch, ZOOKEEPER-1416.patch > > Original Estimate: 504h > Remaining Estimate: 504h > > h4. The Problem > A ZooKeeper Watch can be placed on a single znode and when the znode changes > a Watch event is sent to the client. If there are thousands of znodes being > watched, when a client (re)connect, it would have to send thousands of watch > requests. At Facebook, we have this problem storing information for thousands > of db shards. Consequently a naming service that consumes the db shard > definition issues thousands of watch requests each time the service starts > and changes client watcher. > h4. Proposed Solution > We add the notion of a Persistent Recursive Watch in ZooKeeper. Persistent > means no Watch reset is necessary after a watch-fire. Recursive means the > Watch applies to the node and descendant nodes. A Persistent Recursive Watch > behaves as follows: > # Recursive Watch supports all Watch semantics: CHILDREN, DATA, and EXISTS. > # CHILDREN and DATA Recursive Watches can be placed on any znode. > # EXISTS Recursive Watches can be placed on any path. > # A Recursive Watch behaves like a auto-watch registrar on the server side. > Setting a Recursive Watch means to set watches on all descendant znodes. > # When a watch on a descendant fires, no subsequent event is fired until a > corresponding getData(..) on the znode is called, then Recursive Watch > automically apply the watch on the znode. This maintains the existing Watch > semantic on an individual znode. > # A Recursive Watch overrides any watches placed on a descendant znode. > Practically this means the Recursive Watch Watcher callback is the one > receiving the event and event is delivered exactly once. > A goal here is to reduce the number of semantic changes. The guarantee of no > intermediate watch event until data is read will be maintained. The only > difference is we will automatically re-add the watch after read. At the same > time we add the convience of reducing the need to add multiple watches for > sibling znodes and in turn reduce the number of watch messages sent from the > client to the server. > There are some implementation details that needs to be hashed out. Initial > thinking is to have the Recursive Watch create per-node watches. This will > cause a lot of watches to be created on the server side. Currently, each > watch is stored as a single bit in a bit set relative to a session - up to 3 > bits per client per znode. If there are 100m znodes with 100k clients, each > watching all nodes, then this strategy will consume approximately 3.75TB of > ram distributed across all Observers. Seems expensive. > Alternatively, a blacklist of paths to not send Watches regardless of Watch > setting can be set each time a watch event from a Recursive Watch is fired. > The memory utilization is relative to the number of outstanding reads and at > worst case it's 1/3 * 3.75TB using the parameters given above. > Otherwise, a relaxation of no intermediate watch event until read guarantee > is required. If the server can send watch events regardless of one has > already been fired without corresponding read, then the server can simply > fire watch events without tracking. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ZOOKEEPER-2853) The lastZxidSeen in FileTxnLog.java is never being assigned
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16107240#comment-16107240 ] maoling commented on ZOOKEEPER-2853: Yes . *lastZxidSeen = hdr.getZxid();* should be added > The lastZxidSeen in FileTxnLog.java is never being assigned > --- > > Key: ZOOKEEPER-2853 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2853 > Project: ZooKeeper > Issue Type: Bug > Components: server >Reporter: Fangmin Lv >Assignee: Fangmin Lv >Priority: Minor > Fix For: 3.4.10, 3.5.3, 3.6.0 > > > There is log in FileTxnLog#append to track the txn with smaller zxid than the > last seen, but the lastZxidSeen is never being assigned, so that log is not > printed when it's happened. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ZOOKEEPER-2843) auth_to_local should support reading rules from a file
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16107234#comment-16107234
]
Lionel Cons commented on ZOOKEEPER-2843:
Adding this functionality requires very little code modification. See the
attached {{ZOOKEEPER-2843.patch}}.
Would it be possible to get this in 3.4.11?
> auth_to_local should support reading rules from a file
> --
>
> Key: ZOOKEEPER-2843
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2843
> Project: ZooKeeper
> Issue Type: Improvement
>Reporter: Lionel Cons
> Attachments: ZOOKEEPER-2843.patch
>
>
> The current handling of {{zookeeper.security.auth_to_local}} in
> {{KerberosName.java}} only support rules given directly as the property value.
> These rules must therefore be given on the command line and:
> * must be escaped properly to avoid shell expansion
> * are visible in the {{ps}} output
> It would be much better to put these rules in a file and pass the file path
> as the property value. We would then use something like
> {{-Dzookeeper.security.auth_to_local=file:/etc/zookeeper/rules}}.
> Note that using the {{file:}} prefix allows keeping backward compatibility.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ZOOKEEPER-2843) auth_to_local should support reading rules from a file
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lionel Cons updated ZOOKEEPER-2843:
---
Attachment: ZOOKEEPER-2843.patch
> auth_to_local should support reading rules from a file
> --
>
> Key: ZOOKEEPER-2843
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2843
> Project: ZooKeeper
> Issue Type: Improvement
>Reporter: Lionel Cons
> Attachments: ZOOKEEPER-2843.patch
>
>
> The current handling of {{zookeeper.security.auth_to_local}} in
> {{KerberosName.java}} only support rules given directly as the property value.
> These rules must therefore be given on the command line and:
> * must be escaped properly to avoid shell expansion
> * are visible in the {{ps}} output
> It would be much better to put these rules in a file and pass the file path
> as the property value. We would then use something like
> {{-Dzookeeper.security.auth_to_local=file:/etc/zookeeper/rules}}.
> Note that using the {{file:}} prefix allows keeping backward compatibility.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
ZooKeeper-trunk-jdk8 - Build # 1148 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-jdk8/1148/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 67.45 MB...] [junit] at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214) [junit] 2017-07-31 12:18:22,751 [myid:127.0.0.1:13918] - INFO [main-SendThread(127.0.0.1:13918):ClientCnxn$SendThread@1113] - Opening socket connection to server 127.0.0.1/127.0.0.1:13918. Will not attempt to authenticate using SASL (unknown error) [junit] 2017-07-31 12:18:22,752 [myid:127.0.0.1:13918] - WARN [main-SendThread(127.0.0.1:13918):ClientCnxn$SendThread@1235] - Session 0x10511f91a250001 for server 127.0.0.1/127.0.0.1:13918, unexpected error, closing socket connection and attempting reconnect [junit] java.net.ConnectException: Connection refused [junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) [junit] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717) [junit] at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357) [junit] at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214) [junit] 2017-07-31 12:18:23,025 [myid:127.0.0.1:13918] - INFO [main-SendThread(127.0.0.1:13918):ClientCnxn$SendThread@1113] - Opening socket connection to server 127.0.0.1/127.0.0.1:13918. Will not attempt to authenticate using SASL (unknown error) [junit] 2017-07-31 12:18:23,026 [myid:127.0.0.1:13918] - WARN [main-SendThread(127.0.0.1:13918):ClientCnxn$SendThread@1235] - Session 0x10511f91a25 for server 127.0.0.1/127.0.0.1:13918, unexpected error, closing socket connection and attempting reconnect [junit] java.net.ConnectException: Connection refused [junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) [junit] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717) [junit] at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357) [junit] at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214) [junit] 2017-07-31 12:18:23,894 [myid:127.0.0.1:13918] - INFO [main-SendThread(127.0.0.1:13918):ClientCnxn$SendThread@1113] - Opening socket connection to server 127.0.0.1/127.0.0.1:13918. Will not attempt to authenticate using SASL (unknown error) [junit] 2017-07-31 12:18:23,895 [myid:127.0.0.1:13918] - WARN [main-SendThread(127.0.0.1:13918):ClientCnxn$SendThread@1235] - Session 0x10511f91a250001 for server 127.0.0.1/127.0.0.1:13918, unexpected error, closing socket connection and attempting reconnect [junit] java.net.ConnectException: Connection refused [junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) [junit] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717) [junit] at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357) [junit] at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214) [junit] 2017-07-31 12:18:24,047 [myid:127.0.0.1:13915] - INFO [main-SendThread(127.0.0.1:13915):ClientCnxn$SendThread@1113] - Opening socket connection to server 127.0.0.1/127.0.0.1:13915. Will not attempt to authenticate using SASL (unknown error) [junit] 2017-07-31 12:18:24,048 [myid:127.0.0.1:13915] - WARN [main-SendThread(127.0.0.1:13915):ClientCnxn$SendThread@1235] - Session 0x511f9181d for server 127.0.0.1/127.0.0.1:13915, unexpected error, closing socket connection and attempting reconnect [junit] java.net.ConnectException: Connection refused [junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) [junit] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717) [junit] at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357) [junit] at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214) [junit] 2017-07-31 12:18:24,500 [myid:127.0.0.1:13915] - INFO [main-SendThread(127.0.0.1:13915):ClientCnxn$SendThread@1113] - Opening socket connection to server 127.0.0.1/127.0.0.1:13915. Will not attempt to authenticate using SASL (unknown error) [junit] 2017-07-31 12:18:24,501 [myid:127.0.0.1:13915] - WARN [main-SendThread(127.0.0.1:13915):ClientCnxn$SendThread@1235] - Session 0x511f9181d0001 for server 127.0.0.1/127.0.0.1:13915, unexpected error, closing socket connection and attempting reconnect [junit] java.net.ConnectException: Connection refused [junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) [junit] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717) [junit] at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357) [junit] at org.apache.zookeeper
