ZooKeeper_branch35_jdk8 - Build # 18 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch35_jdk8/18/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 390598 lines...]
 [exec] Log Message Received: [2016-03-20 
05:50:24,661:27945(0x2ad6abd79540):ZOO_INFO@testLogCallbackInit@993: 
testLogCallbackInit #8]
 [exec] Log Message Received: [2016-03-20 
05:50:24,661:27945(0x2ad6abd79540):ZOO_INFO@testLogCallbackInit@993: 
testLogCallbackInit #9]
 [exec] Log Message Received: [2016-03-20 
05:50:24,661:27945(0x2ad6abd79540):ZOO_INFO@zookeeper_close@3257: Closing 
zookeeper sessionId=0x101a1ee9ef8000e to [127.0.0.1:22181]
 [exec] ]
 [exec]  : elapsed 1001 : OK
 [exec] Zookeeper_simpleSystem::testLogCallbackClearLog Message Received: 
[2016-03-20 05:50:24,661:27945(0x2ad6abd79540):ZOO_INFO@log_env@1027: Client 
environment:zookeeper.version=zookeeper C client 3.5.1]
 [exec] Log Message Received: [2016-03-20 
05:50:24,661:27945(0x2ad6abd79540):ZOO_INFO@log_env@1031: Client 
environment:host.name=asf910.gq1.ygridcore.net]
 [exec] Log Message Received: [2016-03-20 
05:50:24,661:27945(0x2ad6abd79540):ZOO_INFO@log_env@1038: Client 
environment:os.name=Linux]
 [exec] Log Message Received: [2016-03-20 
05:50:24,661:27945(0x2ad6abd79540):ZOO_INFO@log_env@1039: Client 
environment:os.arch=3.13.0-36-lowlatency]
 [exec] Log Message Received: [2016-03-20 
05:50:24,661:27945(0x2ad6abd79540):ZOO_INFO@log_env@1040: Client 
environment:os.version=#63-Ubuntu SMP PREEMPT Wed Sep 3 21:56:12 UTC 2014]
 [exec] Log Message Received: [2016-03-20 
05:50:24,661:27945(0x2ad6abd79540):ZOO_INFO@log_env@1048: Client 
environment:user.name=jenkins]
 [exec] Log Message Received: [2016-03-20 
05:50:24,661:27945(0x2ad6abd79540):ZOO_INFO@log_env@1056: Client 
environment:user.home=/home/jenkins]
 [exec] Log Message Received: [2016-03-20 
05:50:24,661:27945(0x2ad6abd79540):ZOO_INFO@log_env@1068: Client 
environment:user.dir=/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk8/branch-3.5/build/test/test-cppunit]
 [exec] Log Message Received: [2016-03-20 
05:50:24,661:27945(0x2ad6abd79540):ZOO_INFO@zookeeper_init_internal@: 
Initiating client connection, host=127.0.0.1:22181 sessionTimeout=1 
watcher=0x45d2a0 sessionId=0 sessionPasswd= context=0x7fff41399540 
flags=0]
 [exec] Log Message Received: [2016-03-20 
05:50:24,662:27945(0x2ad6ae408700):ZOO_INFO@check_events@2357: initiated 
connection to server [127.0.0.1:22181]]
 [exec] Log Message Received: [2016-03-20 
05:50:24,680:27945(0x2ad6ae408700):ZOO_INFO@check_events@2409: session 
establishment complete on server [127.0.0.1:22181], 
sessionId=0x101a1ee9ef8000f, negotiated timeout=1 ]
 [exec]  : elapsed 1000 : OK
 [exec] Zookeeper_simpleSystem::testAsyncWatcherAutoReset ZooKeeper server 
started : elapsed 10852 : OK
 [exec] Zookeeper_simpleSystem::testDeserializeString : elapsed 0 : OK
 [exec] Zookeeper_simpleSystem::testFirstServerDown : elapsed 1001 : OK
 [exec] Zookeeper_simpleSystem::testNullData : elapsed 1036 : OK
 [exec] Zookeeper_simpleSystem::testIPV6 : elapsed 1013 : OK
 [exec] Zookeeper_simpleSystem::testCreate : elapsed 1024 : OK
 [exec] Zookeeper_simpleSystem::testPath : elapsed 1049 : OK
 [exec] Zookeeper_simpleSystem::testPathValidation : elapsed 1142 : OK
 [exec] Zookeeper_simpleSystem::testPing : elapsed 17943 : OK
 [exec] Zookeeper_simpleSystem::testAcl : elapsed 1025 : OK
 [exec] Zookeeper_simpleSystem::testChroot : elapsed 4222 : OK
 [exec] Zookeeper_simpleSystem::testAuth ZooKeeper server started ZooKeeper 
server started : elapsed 31118 : OK
 [exec] Zookeeper_simpleSystem::testHangingClient : elapsed 1040 : OK
 [exec] Zookeeper_simpleSystem::testWatcherAutoResetWithGlobal ZooKeeper 
server started ZooKeeper server started ZooKeeper server started : elapsed 
16124 : OK
 [exec] Zookeeper_simpleSystem::testWatcherAutoResetWithLocal ZooKeeper 
server started ZooKeeper server started ZooKeeper server started : elapsed 
16982 : OK
 [exec] Zookeeper_simpleSystem::testGetChildren2 : elapsed 1204 : OK
 [exec] Zookeeper_simpleSystem::testLastZxid : elapsed 4543 : OK
 [exec] Zookeeper_simpleSystem::testRemoveWatchers ZooKeeper server started 
: elapsed 4653 : OK
 [exec] Zookeeper_readOnly::testReadOnly : elapsed 4157 : OK
 [exec] 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk8/branch-3.5/src/c/tests/TestReconfig.cc:490:
 Assertion: assertion failed [Expression: found != string::npos]
 [exec] Failures !!!
 [exec] Run: 72   Failure total: 1   Failures: 1   Errors: 0
 [exec] FAIL: zktest-mt
 [exec] ==
 [exec] 1 of 2 tests failed
 [exec] Please report to u...@zookeeper.apache.org
 [exec] ==
 [exec] make[1]: 

[jira] [Commented] (ZOOKEEPER-2240) Make the three-node minimum more explicit in documentation and on website

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15203119#comment-15203119
 ] 

Hudson commented on ZOOKEEPER-2240:
---

SUCCESS: Integrated in ZooKeeper-trunk #2860 (See 
[https://builds.apache.org/job/ZooKeeper-trunk/2860/])
ZOOKEEPER-2240 Make the three-node minimum more explicit in documentation and 
on website (Shawn Heisey and Arshad Mohammad via phunt) (phunt: 
[http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN=rev=1735836])
* trunk/CHANGES.txt
* trunk/docs/index.pdf
* trunk/docs/javaExample.pdf
* trunk/docs/linkmap.pdf
* trunk/docs/recipes.pdf
* trunk/docs/releasenotes.pdf
* trunk/docs/zookeeperAdmin.html
* trunk/docs/zookeeperAdmin.pdf
* trunk/docs/zookeeperHierarchicalQuorums.pdf
* trunk/docs/zookeeperInternals.pdf
* trunk/docs/zookeeperJMX.pdf
* trunk/docs/zookeeperObservers.pdf
* trunk/docs/zookeeperOver.pdf
* trunk/docs/zookeeperProgrammers.pdf
* trunk/docs/zookeeperQuotas.pdf
* trunk/docs/zookeeperReconfig.pdf
* trunk/docs/zookeeperStarted.html
* trunk/docs/zookeeperStarted.pdf
* trunk/docs/zookeeperTutorial.pdf
* trunk/src/docs/src/documentation/content/xdocs/zookeeperAdmin.xml
* trunk/src/docs/src/documentation/content/xdocs/zookeeperStarted.xml


> Make the three-node minimum more explicit in documentation and on website
> -
>
> Key: ZOOKEEPER-2240
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2240
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: documentation
>Reporter: Shawn Heisey
>Assignee: Arshad Mohammad
>Priority: Trivial
> Fix For: 3.4.9, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2240-03.patch, ZOOKEEPER-2240.patch, 
> ZOOKEEPER-2240.patch, zookeeperAdmin.pdf, zookeeperStarted.pdf
>
>
> One of the most important parts of a production zookeeper deployment is the 
> three-node minimum requirement for fault tolerance ... but when I glance at 
> the website and the documentation, this requirement is difficult to actually 
> find.
> It is buried deep in the admin documentation, in a sentence that says "Thus, 
> a deployment that consists of three machines can handle one failure, and a 
> deployment of five machines can handle two failures."  Other parts of the 
> documentation hint at it, but nothing that I've seen comes out and explicitly 
> says it.
> Ideally, documentation about this requirement would be in a location where it 
> can be easily pinpointed with a targeted URL, so I can point to ZK 
> documentation with a link and clearly tell SolrCloud users that this is a 
> real requirement.
> If someone can point me to version control locations where I can check out or 
> clone the docs and the website, I'm happy to attempt a patch.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

ZooKeeper-trunk-jdk8 - Build # 533 - Failure

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper-trunk-jdk8/533/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 369814 lines...]
[junit] at 
org.apache.zookeeper.server.quorum.LearnerHandler.run(LearnerHandler.java:622)
[junit] 2016-03-20 05:37:06,583 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2016-03-20 05:37:06,583 [myid:] - INFO  
[ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - 
ConnnectionExpirerThread interrupted
[junit] 2016-03-20 05:37:06,582 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2016-03-20 05:37:06,582 [myid:] - WARN  
[LearnerHandler-/127.0.0.1:41810:LearnerHandler@619] - *** GOODBYE 
/127.0.0.1:41810 
[junit] 2016-03-20 05:37:06,586 [myid:] - INFO  
[QuorumPeer[myid=5](plain=/127.0.0.1:30214)(secure=disabled):MBeanRegistry@128] 
- Unregister MBean 
[org.apache.ZooKeeperService:name0=ReplicatedServer_id5,name1=replica.5,name2=Leader]
[junit] 2016-03-20 05:37:06,586 [myid:] - WARN  
[LearnerHandler-/127.0.0.1:41810:LearnerHandler@903] - Ignoring unexpected 
exception
[junit] java.lang.InterruptedException
[junit] at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireInterruptibly(AbstractQueuedSynchronizer.java:1220)
[junit] at 
java.util.concurrent.locks.ReentrantLock.lockInterruptibly(ReentrantLock.java:335)
[junit] at 
java.util.concurrent.LinkedBlockingQueue.put(LinkedBlockingQueue.java:339)
[junit] at 
org.apache.zookeeper.server.quorum.LearnerHandler.shutdown(LearnerHandler.java:901)
[junit] at 
org.apache.zookeeper.server.quorum.LearnerHandler.run(LearnerHandler.java:622)
[junit] 2016-03-20 05:37:06,586 [myid:] - WARN  
[QuorumPeer[myid=5](plain=/127.0.0.1:30214)(secure=disabled):QuorumPeer@1126] - 
Unexpected exception
[junit] java.lang.InterruptedException
[junit] at java.lang.Object.wait(Native Method)
[junit] at 
org.apache.zookeeper.server.quorum.Leader.lead(Leader.java:559)
[junit] at 
org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:1123)
[junit] 2016-03-20 05:37:06,587 [myid:] - INFO  
[QuorumPeer[myid=5](plain=/127.0.0.1:30214)(secure=disabled):Leader@613] - 
Shutting down
[junit] 2016-03-20 05:37:06,587 [myid:] - WARN  
[QuorumPeer[myid=5](plain=/127.0.0.1:30214)(secure=disabled):QuorumPeer@1157] - 
PeerState set to LOOKING
[junit] 2016-03-20 05:37:06,587 [myid:] - WARN  
[QuorumPeer[myid=5](plain=/127.0.0.1:30214)(secure=disabled):QuorumPeer@1139] - 
QuorumPeer main thread exited
[junit] 2016-03-20 05:37:06,587 [myid:] - INFO  
[QuorumPeer[myid=5](plain=/127.0.0.1:30214)(secure=disabled):MBeanRegistry@128] 
- Unregister MBean [org.apache.ZooKeeperService:name0=ReplicatedServer_id5]
[junit] 2016-03-20 05:37:06,587 [myid:] - INFO  
[QuorumPeer[myid=5](plain=/127.0.0.1:30214)(secure=disabled):MBeanRegistry@128] 
- Unregister MBean 
[org.apache.ZooKeeperService:name0=ReplicatedServer_id5,name1=replica.5]
[junit] 2016-03-20 05:37:06,587 [myid:] - INFO  
[QuorumPeer[myid=5](plain=/127.0.0.1:30214)(secure=disabled):MBeanRegistry@128] 
- Unregister MBean 
[org.apache.ZooKeeperService:name0=ReplicatedServer_id5,name1=replica.1]
[junit] 2016-03-20 05:37:06,587 [myid:] - INFO  
[QuorumPeer[myid=5](plain=/127.0.0.1:30214)(secure=disabled):MBeanRegistry@128] 
- Unregister MBean 
[org.apache.ZooKeeperService:name0=ReplicatedServer_id5,name1=replica.2]
[junit] 2016-03-20 05:37:06,587 [myid:] - INFO  
[QuorumPeer[myid=5](plain=/127.0.0.1:30214)(secure=disabled):MBeanRegistry@128] 
- Unregister MBean 
[org.apache.ZooKeeperService:name0=ReplicatedServer_id5,name1=replica.3]
[junit] 2016-03-20 05:37:06,586 [myid:] - INFO  
[/127.0.0.1:30216:QuorumCnxManager$Listener@659] - Leaving listener
[junit] 2016-03-20 05:37:06,588 [myid:] - INFO  [main:QuorumUtil@254] - 
Shutting down leader election 
QuorumPeer[myid=5](plain=/127.0.0.1:30214)(secure=disabled)
[junit] 2016-03-20 05:37:06,588 [myid:] - INFO  [main:QuorumUtil@259] - 
Waiting for QuorumPeer[myid=5](plain=/127.0.0.1:30214)(secure=disabled) to exit 
thread
[junit] 2016-03-20 05:37:06,588 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 30202
[junit] 2016-03-20 05:37:06,589 [myid:] - INFO  [main:QuorumUtil@243] - 
127.0.0.1:30202 is no longer accepting client connections
[junit] 2016-03-20 05:37:06,589 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 30205
[junit] 2016-03-20 05:37:06,589 [myid:] - INFO  [main:QuorumUtil@243] - 
127.0.0.1:30205 is no longer accepting client connections
[junit] 2016-03-20 05:37:06,589 [myid:] - INFO  

Failed: ZOOKEEPER-2195 PreCommit Build #3113

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2195
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3113/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 388168 lines...]
 [exec] -1 tests included.  The patch doesn't appear to include any new 
or modified tests.
 [exec] Please justify why no new tests are needed 
for this patch.
 [exec] Also please list what manual steps were 
performed to verify this patch.
 [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 2.0.3) 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-Build/3113//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3113//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3113//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] 31187129398bf8222490935e0a32053be006 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1605:
 exec returned: 1

Total time: 19 minutes 33 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Recording test results
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
[description-setter] Description set: ZOOKEEPER-2195
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7



###
## FAILED TESTS (if any) 
##
All tests passed

[jira] [Commented] (ZOOKEEPER-2195) fsync.warningthresholdms in zoo.cfg not working

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15203113#comment-15203113
 ] 

Hadoop QA commented on ZOOKEEPER-2195:
--

-1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12793958/ZOOKEEPER-2195-2.patch
  against trunk revision 1735836.

+1 @author.  The patch does not contain any @author tags.

-1 tests included.  The patch doesn't appear to include any new or modified 
tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

+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 2.0.3) 
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-Build/3113//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3113//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3113//console

This message is automatically generated.

> fsync.warningthresholdms in zoo.cfg not working
> ---
>
> Key: ZOOKEEPER-2195
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2195
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: quorum
>Affects Versions: 3.4.6, 3.5.0
>Reporter: David Fan
>Assignee: Biju Nair
>Priority: Trivial
> Fix For: 3.4.9, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2195-1.patch, ZOOKEEPER-2195-2.patch, 
> ZOOKEEPER-2195-DOC.patch, ZOOKEEPER-2195.patch
>
>
> Config fsync.warningthresholdms in zoo.cfg does not work.
> I find QuorumPeerConfig.parseProperties give fsync.warningthresholdms a 
> prefix like "zookeeper.fsync.warningthresholdms".  But in class FileTxnLog 
> where fsync.warningthresholdms is used, code is 
> :Long.getLong("fsync.warningthresholdms", 1000),without prefix "zookeeper.", 
> therefore can not get fsync.warningthresholdms's value.
> I wonder the speed of fsync, need this config to see whether the speed is 
> good enough.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2141) ACL cache in DataTree never removes entries

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15203108#comment-15203108
 ] 

Hadoop QA commented on ZOOKEEPER-2141:
--

+1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12793634/ZOOKEEPER-2141.patch
  against trunk revision 1735836.

+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 2.0.3) 
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-Build/3112//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3112//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3112//console

This message is automatically generated.

> ACL cache in DataTree never removes entries
> ---
>
> Key: ZOOKEEPER-2141
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2141
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.4.6
>Reporter: Karol Dudzinski
>Assignee: Adam Milne-Smith
> Attachments: ZOOKEEPER-2141.patch, ZOOKEEPER-2141.patch, 
> ZOOKEEPER-2141.patch, ZOOKEEPER-2141.patch, ZOOKEEPER-2141.patch
>
>
> The problem and potential solutions are discussed in 
> http://mail-archives.apache.org/mod_mbox/zookeeper-user/201502.mbox/browser
> I will attach a proposed patch in due course.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Success: ZOOKEEPER-2141 PreCommit Build #3112

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2141
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3112/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 386865 lines...]
 [exec]   
http://issues.apache.org/jira/secure/attachment/12793634/ZOOKEEPER-2141.patch
 [exec]   against trunk revision 1735836.
 [exec] 
 [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 2.0.3) 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-Build/3112//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3112//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3112//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] f60b5a0fb44c941cebcd7d24776838a7e6256ef2 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 

BUILD SUCCESSFUL
Total time: 19 minutes 6 seconds
Archiving artifacts
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Recording test results
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
[description-setter] Description set: ZOOKEEPER-2141
Email was triggered for: Success
Sending email for trigger: Success
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7



###
## FAILED TESTS (if any) 
##
All tests passed

Success: ZOOKEEPER-2388 PreCommit Build #3102

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2388
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3102/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 378879 lines...]
 [exec]   
http://issues.apache.org/jira/secure/attachment/12793843/ZOOKEEPER-2388-01.patch
 [exec]   against trunk revision 1735116.
 [exec] 
 [exec] +1 @author.  The patch does not contain any @author tags.
 [exec] 
 [exec] +1 tests included.  The patch appears to include 6 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 2.0.3) 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-Build/3102//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3102//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3102//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] 8b6c05a4dab56c24b619c4c3ed8d8ed473fda214 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 

BUILD SUCCESSFUL
Total time: 13 minutes 54 seconds
Archiving artifacts
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Recording test results
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
[description-setter] Description set: ZOOKEEPER-2388
Email was triggered for: Success
Sending email for trigger: Success
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7



###
## FAILED TESTS (if any) 
##
All tests passed

[jira] [Commented] (ZOOKEEPER-2387) Attempt to gracefully stop the

[Patrick Hunt (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15203102#comment-15203102
 ] 

Patrick Hunt commented on ZOOKEEPER-2387:
-

bq. users who would like any inflight or queued tasks like snapshot is shutdown 
before bringing down ZK completely

why would "users" care? Our job is to make this as transparent as possible to 
users. We do this in general in ZK, which is why you typically don't need to 
set a ton of config parameters when you setup a cluster, we just "do the right 
thing" rather than involving the user.

> Attempt to gracefully stop the 
> ---
>
> Key: ZOOKEEPER-2387
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2387
> Project: ZooKeeper
>  Issue Type: Improvement
>Reporter: Biju Nair
>Assignee: Biju Nair
> Attachments: ZOOKEEPER-2387-1.patch
>
>
> To stop ZooKeeper service, {{kill}} is issued against the ZK process. It will 
> be good to gracefully stop all the subcomponents.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2391) setMin/MaxSessionTimeout of ZookeeperServer are implemented in quite a weak way

[Patrick Hunt (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15203101#comment-15203101
 ] 

Patrick Hunt commented on ZOOKEEPER-2391:
-

bq. Does "the docs" mean the comment of Javadoc or something else?

I suspect Flavio was referring to the documentation proper. It's under 
src/docs/... Notice there is existing documentation for these parameters.

bq. Should I test the code in 3.4 and 3.5?

if you think it makes sense to commit to those branches then it's helpful if 
you apply the patch to them and check. Sometimes we need to submit separate 
patches because of conflicts...

> setMin/MaxSessionTimeout of ZookeeperServer are implemented in quite a weak 
> way
> ---
>
> Key: ZOOKEEPER-2391
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2391
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: documentation, server
>Reporter: Kazuaki Banzai
>Assignee: Kazuaki Banzai
>Priority: Minor
> Attachments: ZOOKEEPER-2391.patch
>
>
> setMin/MaxSessionTimeout of ZookeeperServer are implemented in quite a weak 
> way.
> * -1 restores the default, but this is not documented.
> * values < -1 are permitted but make no sense.
> * min > max is permitted but makes not sense.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2382) Make fsync.warningthresholdms property configurable through zoo.cfg

[Patrick Hunt (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15203098#comment-15203098
 ] 

Patrick Hunt commented on ZOOKEEPER-2382:
-

No worries. It's not great code, a legacy of being around for a while. ;-)

> Make fsync.warningthresholdms property configurable through zoo.cfg
> ---
>
> Key: ZOOKEEPER-2382
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2382
> Project: ZooKeeper
>  Issue Type: Improvement
>Reporter: Biju Nair
>Assignee: Biju Nair
>Priority: Minor
> Attachments: ZOOKEEPER-2382-DRAFT.patch
>
>
> Currently {{fsync.warningthresholdms}} property can be set as a Java system 
> property. But it would help if this property can be made configurable through 
> {{zoo.cfg}} so that configuration management tools can leverage it. Also the 
> Java system property name should be standardized (refer ZOOKEEPER-2316) so 
> that the property is inline with the standard followed by other properties.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: We need to prioritize getting logging fixed in trunk/3.5

[Flavio Junqueira]

Agreed, sounds like a good plan, +1.

Thanks, Chris!

-Flavio

> On 17 Mar 2016, at 06:02, Patrick Hunt  wrote:
> 
> That makes sense to me as well. +1. Thank you Chris!
> 
> Patrick
> 
> On Wed, Mar 16, 2016 at 9:42 AM, Raúl Gutiérrez Segalés  
> wrote:
>> +1. This sounds like a good plan. Thanks Chris!
>> On Mar 16, 2016 9:36 AM, "Chris Nauroth"  wrote:
>> 
>>> We now have multiple binding +1's for a revert.  To finalize the plan,
>>> here is what I propose:
>>> 
>>> 1. Full revert of ZOOKEEPER-1371, targeted to 3.5.2.
>>> 
>>> 2. Retarget ZOOKEEPER-1371 to 3.5.3 with the scope limited to just the
>>> SLF4J logging API changes.  We'd omit the build changes that dropped the
>>> SLF4J-Log4J 1.2 binding from the distro.  This would be a
>>> backwards-compatible change, and I believe it was the original intent of
>>> ZOOKEEPER-1371.  This is not critical to complete for 3.5.3.  I'm just
>>> pushing it ahead to the next version.
>>> 
>>> 3. Retarget ZOOKEEPER-2342 to 3.6.0 for tracking Log4J 2 migration.  This
>>> will have to happen someday since Log4J 1 is end of life, but it will
>>> likely be backwards-incompatible, and the change provides no value add to
>>> justify it for the 3.5 line.
>>> 
>>> I'll wait 24 hours before proceeding with a revert in case anyone else
>>> wants to comment.
>>> 
>>> --Chris Nauroth
>>> 
>>> 
>>> 
>>> 
>>> On 3/16/16, 6:47 AM, "Camille Fournier"  wrote:
>>> 
 I'm a strong +1 to get this fixed even if it requires reverting the
 original patch. Broken logging is huge. Let's do whatever is expedient and
 sensible to fix it.
 
 On Tue, Mar 15, 2016 at 7:27 PM, Chris Nauroth 
 wrote:
 
> Yes, that's basically my assessment too.  Copy-pasting my earlier
> comment
> from ZOOKEEPER-1371:
> 
> "After this patch, ZooKeeper no longer produces any logging, because
> there
> is no SLF4J binding jar available on the runtime classpath."
> 
> 
> There is no compatibility problem with switching to SLF4J exclusively as
> our API of choice for logging instead of calling the Log4J API.  The
> incompatible part is that the distro isn't shipping with any SLF4J
> binding
> included.  Perhaps we can do a partial revert of just that part of
> ZOOKEEPER-1371.
> 
> --Chris Nauroth
> 
> 
> 
> 
> On 3/15/16, 11:54 AM, "Patrick Hunt"  wrote:
> 
>> Hm, I started looking at the original patch in more depth:
>> 
> 
> 
>>> https://issues.apache.org/jira/secure/attachment/12773684/ZOOKEEPER-1371-
> 0
>> 5.patch
>> 
>> is the real root issue 2342 is trying to address the following line
>> change:
>> 
>> -> transitive="false"/>
>> +> transitive="false" conf="test->default"/>
>> 
>> Specifically that we changed from runtime to test only for this
>> dependency? Perhaps we just need to revert that? I see some other
>> magic happening in the build.xml file that I don't quite understand -
>> adding a new target and NoLog4j... references.
>> 
>> Raul perhaps you can give more insight since it seems like you worked
>> on 1371 most recently?
>> 
>> Patrick
>> 
>> 
>> On Tue, Mar 15, 2016 at 11:41 AM, Chris Nauroth
>>  wrote:
>>> I agree.  Even if we don't fully understand every minute technical
>>> detail
>>> of Log4J 2 vs. Log4J 1, I think we've learned enough from my
>>> work-in-progress patch to declare that a migration is too risky for
> the
>>> 3.5 line.  Reverting ZOOKEEPER-1371 (the earlier
> backwards-incompatible
>>> logging change) is the better choice for the interest of proceeding
> with
>>> 3.5 releases.
>>> 
>>> --Chris Nauroth
>>> 
>>> 
>>> 
>>> 
>>> On 3/15/16, 11:23 AM, "Patrick Hunt"  wrote:
>>> 
 I just commented on ZOOKEEPER-2342... not sure I fully understand all
 the issues to be honest. Given how much we're trying to do in 3.5 it
 seems like it would be prudent to wait on 1371 until 3.6... IMO. :-)
 
 Patrick
 
 On Tue, Mar 15, 2016 at 11:15 AM, Chris Nauroth
  wrote:
> At this point, I am +1 for a revert of the patch that introduced
> the
> problem (ZOOKEEPER-1371).  We need more time to come up with a
> migration
> path to Log4J 2 that minimizes impact on operators.  That will take
> time,
> and I'd prefer that we don't hold up 3.5.2-alpha for it.
> 
> --Chris Nauroth
> 
> 
> 
> 
> On 3/15/16, 11:08 AM, "Patrick Hunt"  wrote:
> 
>> Hi folks, can we prioritize getting logging fixed? It's causing

[jira] [Commented] (ZOOKEEPER-2391) setMin/MaxSessionTimeout of ZookeeperServer are implemented in quite a weak way

[Kazuaki Banzai (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15200145#comment-15200145
 ] 

Kazuaki Banzai commented on ZOOKEEPER-2391:
---

Thank you for replying this report.
This is my first bug report and I don't understand the process of contribution 
well.
So please let me ask some questions.
>>Do you want to update the docs as well in your patch?
Does "the docs" mean the comment of Javadoc or something else?
I added the documentation tag because I wrote Javadoc comment(I'm sorry if I 
misunderstand the use of the tag).
>>Also, I think we need to fix this in branches 3.4, 3.5, and trunk, yes?
Yes.
I wrote this patch in trunk branch, but I didn't check the code in 3.4 and 3.5.
Should I test the code in 3.4 and 3.5?

> setMin/MaxSessionTimeout of ZookeeperServer are implemented in quite a weak 
> way
> ---
>
> Key: ZOOKEEPER-2391
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2391
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: documentation, server
>Reporter: Kazuaki Banzai
>Assignee: Kazuaki Banzai
>Priority: Minor
> Attachments: ZOOKEEPER-2391.patch
>
>
> setMin/MaxSessionTimeout of ZookeeperServer are implemented in quite a weak 
> way.
> * -1 restores the default, but this is not documented.
> * values < -1 are permitted but make no sense.
> * min > max is permitted but makes not sense.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2393) Revert run-time dependency on log4j and slf4j-log4j12

[Chris Nauroth (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15202321#comment-15202321
 ] 

Chris Nauroth commented on ZOOKEEPER-2393:
--

[~arshad.mohammad], thank you for putting this patch together quickly.  Thank 
you also for updating the license information.  I tested this successfully by 
building a distro tarball.  I verified that both server and client produce logs 
as expected out of the box, without additional deployment steps for an SLF4J 
binding.

In zookeeperAdmin.xml, we have 3 remaining references to 1.2.16 in some sample 
classpath settings.  Could you please update those to 1.2.17?

> Revert run-time dependency on log4j and slf4j-log4j12
> -
>
> Key: ZOOKEEPER-2393
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2393
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Reporter: Arshad Mohammad
>Assignee: Arshad Mohammad
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2393.patch
>
>
> Zookeeper run-time dependency on log4j and slf4j-log4j12 was removed as part 
> of ZOOKEEPER-1371 jira work.
> Following things were done as part of ZOOKEEPER-1371
> # Removed direct log4j API use from the code, instead used slf4j-api
> # Changed  log4j  and slf4j-log4j12 run time dependency to test time 
> dependency
> # Upgraded log4j, slf4j-log4j12  and slf4j-api versions.
> Here is the component wise version change
> #* (zookeeper)ivy.xml
> log4j: 1.2.15 -->1.7.5
> #* src\contrib\loggraph\ivy.xml
> slf4j-api: 1.6.1 -->1.7.5
> slf4j-log4j12:  1.6.1 -->1.7.5
> log4j: 1.2.15 -->1.7.5
> #* src\contrib\rest\ivy.xml
> slf4j-api: 1.6.1 -->1.7.5
> slf4j-log4j12:  1.6.1 -->1.7.5
> log4j: 1.2.15 -->1.7.5
> #* src\contrib\zooinspector\ivy.xml
> slf4j-api: 1.6.1 -->1.7.5
> slf4j-log4j12:  1.6.1 -->1.7.5
> log4j: 1.2.15 -->1.7.5
> The major problem with ZOOKEEPER-1371 change is that it removed run time 
> dependency. For more detail refer ZOOKEEPER-2342 discussion
> Now as part of this jira revert back only run time dependency, #2, on log4j 
> and slf4j-log4j12.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

ZooKeeper_branch34_jdk7 - Build # 1024 - Failure

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch34_jdk7/1024/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 222714 lines...]
[junit] 2016-03-16 15:13:32,202 [myid:] - INFO  
[main:PrepRequestProcessor@767] - Shutting down
[junit] 2016-03-16 15:13:32,202 [myid:] - INFO  
[main:SyncRequestProcessor@209] - Shutting down
[junit] 2016-03-16 15:13:32,202 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2016-03-16 15:13:32,203 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@187] - SyncRequestProcessor exited!
[junit] 2016-03-16 15:13:32,203 [myid:] - INFO  
[main:FinalRequestProcessor@415] - shutdown of request processor complete
[junit] 2016-03-16 15:13:32,204 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-03-16 15:13:32,205 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-03-16 15:13:32,206 [myid:] - INFO  [main:ClientBase@443] - 
STARTING server
[junit] 2016-03-16 15:13:32,207 [myid:] - INFO  [main:ClientBase@364] - 
CREATING server instance 127.0.0.1:11221
[junit] 2016-03-16 15:13:32,207 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2016-03-16 15:13:32,207 [myid:] - INFO  [main:ClientBase@339] - 
STARTING server instance 127.0.0.1:11221
[junit] 2016-03-16 15:13:32,208 [myid:] - INFO  [main:ZooKeeperServer@170] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/branch-3.4/build/test/tmp/test940157891092067863.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/branch-3.4/build/test/tmp/test940157891092067863.junit.dir/version-2
[junit] 2016-03-16 15:13:32,212 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-03-16 15:13:32,213 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:43099
[junit] 2016-03-16 15:13:32,213 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing 
stat command from /127.0.0.1:43099
[junit] 2016-03-16 15:13:32,214 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@663] - Stat command output
[junit] 2016-03-16 15:13:32,214 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1008] - Closed socket connection for client 
/127.0.0.1:43099 (no session established for client)
[junit] 2016-03-16 15:13:32,215 [myid:] - INFO  [main:JMXEnv@229] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-03-16 15:13:32,217 [myid:] - INFO  [main:JMXEnv@246] - 
expect:InMemoryDataTree
[junit] 2016-03-16 15:13:32,217 [myid:] - INFO  [main:JMXEnv@250] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2016-03-16 15:13:32,217 [myid:] - INFO  [main:JMXEnv@246] - 
expect:StandaloneServer_port
[junit] 2016-03-16 15:13:32,218 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2016-03-16 15:13:32,218 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 32622
[junit] 2016-03-16 15:13:32,218 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2016-03-16 15:13:32,218 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2016-03-16 15:13:32,218 [myid:] - INFO  [main:ClientBase@520] - 
tearDown starting
[junit] 2016-03-16 15:13:32,283 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x1537ffd2cfe closed
[junit] 2016-03-16 15:13:32,283 [myid:] - INFO  [main:ClientBase@490] - 
STOPPING server
[junit] 2016-03-16 15:13:32,284 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x1537ffd2cfe
[junit] 2016-03-16 15:13:32,284 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2016-03-16 15:13:32,284 [myid:] - INFO  [main:ZooKeeperServer@469] 
- shutting down
[junit] 2016-03-16 15:13:32,284 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2016-03-16 15:13:32,285 [myid:] - INFO  
[main:PrepRequestProcessor@767] - Shutting down
[junit] 2016-03-16 15:13:32,285 [myid:] - INFO  
[main:SyncRequestProcessor@209] - Shutting down
[junit] 2016-03-16 15:13:32,285 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2016-03-16 15:13:32,286 [myid:] - INFO  

[jira] [Updated] (ZOOKEEPER-2393) Revert run-time dependency on log4j and slf4j-log4j12

[Chris Nauroth (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chris Nauroth updated ZOOKEEPER-2393:
-
Priority: Blocker  (was: Major)

> Revert run-time dependency on log4j and slf4j-log4j12
> -
>
> Key: ZOOKEEPER-2393
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2393
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Reporter: Arshad Mohammad
>Assignee: Arshad Mohammad
>Priority: Blocker
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2393.patch
>
>
> Zookeeper run-time dependency on log4j and slf4j-log4j12 was removed as part 
> of ZOOKEEPER-1371 jira work.
> Following things were done as part of ZOOKEEPER-1371
> # Removed direct log4j API use from the code, instead used slf4j-api
> # Changed  log4j  and slf4j-log4j12 run time dependency to test time 
> dependency
> # Upgraded log4j, slf4j-log4j12  and slf4j-api versions.
> Here is the component wise version change
> #* (zookeeper)ivy.xml
> log4j: 1.2.15 -->1.7.5
> #* src\contrib\loggraph\ivy.xml
> slf4j-api: 1.6.1 -->1.7.5
> slf4j-log4j12:  1.6.1 -->1.7.5
> log4j: 1.2.15 -->1.7.5
> #* src\contrib\rest\ivy.xml
> slf4j-api: 1.6.1 -->1.7.5
> slf4j-log4j12:  1.6.1 -->1.7.5
> log4j: 1.2.15 -->1.7.5
> #* src\contrib\zooinspector\ivy.xml
> slf4j-api: 1.6.1 -->1.7.5
> slf4j-log4j12:  1.6.1 -->1.7.5
> log4j: 1.2.15 -->1.7.5
> The major problem with ZOOKEEPER-1371 change is that it removed run time 
> dependency. For more detail refer ZOOKEEPER-2342 discussion
> Now as part of this jira revert back only run time dependency, #2, on log4j 
> and slf4j-log4j12.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: ZOOKEEPER-2364: "ant docs" fails on branch-3.5 due to missing releasenotes.xml.

[Patrick Hunt]

I had to dig a bit deeper into forrest to understand this. Urg. I
attached a new patch to the jira for your consideration.

Patrick

On Sat, Mar 19, 2016 at 4:34 PM, Patrick Hunt  wrote:
> It's very likely I changed/broke this originally. I've been meaning to
> get back to the jira you created. I'll see what I can do.
>
> Patrick
>
> On Sat, Mar 19, 2016 at 2:58 PM, Chris Nauroth  
> wrote:
>> Could someone please help review ZOOKEEPER-2364?  I consider this a blocker 
>> for 3.5.2-alpha, because it blocks our ability to update the docs, and we 
>> have several documentation patches to ship in 3.5.2-alpha.  Thank you.
>>
>> --Chris Nauroth

[jira] [Commented] (ZOOKEEPER-2364) "ant docs" fails on branch-3.5 due to missing releasenotes.xml.

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15203053#comment-15203053
 ] 

Hadoop QA commented on ZOOKEEPER-2364:
--

+1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12794383/ZOOKEEPER-2364.patch
  against trunk revision 1735820.

+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 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 2.0.3) 
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-Build/3111//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3111//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3111//console

This message is automatically generated.

> "ant docs" fails on branch-3.5 due to missing releasenotes.xml.
> ---
>
> Key: ZOOKEEPER-2364
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2364
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: build, documentation
>Reporter: Chris Nauroth
>Assignee: Chris Nauroth
>Priority: Blocker
> Fix For: 3.5.2
>
> Attachments: ZOOKEEPER-2364-branch-3.5.001.patch, 
> ZOOKEEPER-2364-branch-3.5.002.patch, ZOOKEEPER-2364.002.patch, 
> ZOOKEEPER-2364.patch
>
>
> "ant docs" is failing on branch-3.5.  (Both trunk and branch-3.4 are fine.)  
> The root cause appears
> to be a missing file on branch-3.5: 
> src/docs/src/documentation/content/xdocs/releasenotes.xml.
>  This causes Forrest to report a failure due to broken hyperlinks targeting 
> releasenotes.html.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-1467) Server principal on client side is derived using hostname.

[Flavio Junqueira (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199142#comment-15199142
 ] 

Flavio Junqueira commented on ZOOKEEPER-1467:
-

Not sure why we have it marked as a blocker, it doesn't look like a blocker to 
me.

> Server principal on client side is derived using hostname.
> --
>
> Key: ZOOKEEPER-1467
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1467
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.4.3, 3.4.4, 3.5.0, 4.0.0
>Reporter: Laxman
>Assignee: Eugene Koontz
>Priority: Blocker
>  Labels: Security, client, kerberos, sasl
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-1467.patch, ZOOKEEPER-1467.patch
>
>
> Server principal on client side is derived using hostname.
> org.apache.zookeeper.ClientCnxn.SendThread.startConnect()
> {code}
>try {
> zooKeeperSaslClient = new 
> ZooKeeperSaslClient("zookeeper/"+addr.getHostName());
> }
> {code}
> This may have problems when admin wanted some customized principals like 
> zookeeper/cluste...@hadoop.com where clusterid is the cluster identifier but 
> not the host name.
> IMO, server principal also should be configurable as hadoop is doing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Success: ZOOKEEPER-2364 PreCommit Build #3111

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2364
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3111/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 386502 lines...]
 [exec]   
http://issues.apache.org/jira/secure/attachment/12794383/ZOOKEEPER-2364.patch
 [exec]   against trunk revision 1735820.
 [exec] 
 [exec] +1 @author.  The patch does not contain any @author tags.
 [exec] 
 [exec] +0 tests included.  The patch appears to be a documentation 
patch that doesn't require 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 2.0.3) 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-Build/3111//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3111//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3111//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] 9ebd78de1aabb9397e6048550d2cda96cee879a8 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 

BUILD SUCCESSFUL
Total time: 21 minutes 42 seconds
Archiving artifacts
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Recording test results
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
[description-setter] Description set: ZOOKEEPER-2364
Email was triggered for: Success
Sending email for trigger: Success
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7



###
## FAILED TESTS (if any) 
##
All tests passed

[jira] [Comment Edited] (ZOOKEEPER-2364) "ant docs" fails on branch-3.5 due to missing releasenotes.xml.

[Patrick Hunt (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15203047#comment-15203047
 ] 

Patrick Hunt edited comment on ZOOKEEPER-2364 at 3/20/16 1:58 AM:
--

[~cnauroth] can you give my patch a try? It turns out that "api" was working 
because of some special setup in the default forrest config. Took me about 4 
hours to figure this out. Arg! See 
https://forrest.apache.org/docs_0_90/faq.html#cli-xconf for more details.

Once I figured out why api was special it was easy to fix - I added an exclude 
for releasenotes in the cli.xconf file and pulled the default into our forrest 
subdir.

With this patch we should remove releasenotes from the src/docs/... directory 
and use the HTML directly from Jira (my original intent but I only got half way 
there).


was (Author: phunt):
[~cnauroth] can you give my patch a try? It turns out that "api" was working 
because of some special setup in the default forrest config. Took me about 4 
hours to figure this out. Arg! See 
https://forrest.apache.org/docs_0_90/faq.html#cli-xconf for more details.

With this patch we should remove releasenotes from the src/docs/... directory 
and use the HTML directly from Jira (my original intent but I only got half way 
there).

> "ant docs" fails on branch-3.5 due to missing releasenotes.xml.
> ---
>
> Key: ZOOKEEPER-2364
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2364
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: build, documentation
>Reporter: Chris Nauroth
>Assignee: Chris Nauroth
>Priority: Blocker
> Fix For: 3.5.2
>
> Attachments: ZOOKEEPER-2364-branch-3.5.001.patch, 
> ZOOKEEPER-2364-branch-3.5.002.patch, ZOOKEEPER-2364.002.patch, 
> ZOOKEEPER-2364.patch
>
>
> "ant docs" is failing on branch-3.5.  (Both trunk and branch-3.4 are fine.)  
> The root cause appears
> to be a missing file on branch-3.5: 
> src/docs/src/documentation/content/xdocs/releasenotes.xml.
>  This causes Forrest to report a failure due to broken hyperlinks targeting 
> releasenotes.html.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2382) Make fsync.warningthresholdms property configurable through zoo.cfg

[Biju Nair (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199320#comment-15199320
 ] 

Biju Nair commented on ZOOKEEPER-2382:
--

[~phunt] looking at 
[QuorumPeerConfig.java|https://github.com/apache/zookeeper/blob/trunk/src/java/main/org/apache/zookeeper/server/quorum/QuorumPeerConfig.java#L216-L288]
 "fsync.warningthresholdms" is not a property read from the zoo.cfg file. Also 
the [admin 
guide|https://zookeeper.apache.org/doc/trunk/zookeeperAdmin.html#sc_advancedConfiguration]
 mentions that "fsync.warningthresholdms" can only be set as a system property.

> Make fsync.warningthresholdms property configurable through zoo.cfg
> ---
>
> Key: ZOOKEEPER-2382
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2382
> Project: ZooKeeper
>  Issue Type: Improvement
>Reporter: Biju Nair
>Assignee: Biju Nair
>Priority: Minor
> Attachments: ZOOKEEPER-2382-DRAFT.patch
>
>
> Currently {{fsync.warningthresholdms}} property can be set as a Java system 
> property. But it would help if this property can be made configurable through 
> {{zoo.cfg}} so that configuration management tools can leverage it. Also the 
> Java system property name should be standardized (refer ZOOKEEPER-2316) so 
> that the property is inline with the standard followed by other properties.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: We need to prioritize getting logging fixed in trunk/3.5

[Chris Nauroth]

Hi Mohammad,

If you want to file a JIRA with a patch for the partial revert, then
please go ahead.  Feel free to notify me on the issue for code review.
Thanks!

--Chris Nauroth




On 3/17/16, 12:23 AM, "Mohammad arshad"  wrote:

>>>1. Full revert of ZOOKEEPER-1371, targeted to 3.5.2.
>Can we do partial revert instead of full
> i) revert log4j and slf4j test scoped dependency to run time dependency,
>as it we earlier before this patch was merged
> ii) revert the changes done in build.xml
>For partial revert we can create another path on top of latest code, I
>can create the patch.
>This will avoid lot of duplicate effort
> 
>>>2. Retarget ZOOKEEPER-1371 to 3.5.3 with the scope ...
>This is not required as if above is done
> 
>>> 3. Retarget ZOOKEEPER-2342 to 3.6.0 ...
>+1 for this
>
>
>-Original Message-
>From: Flavio Junqueira [mailto:f...@apache.org]
>Sent: 17 March 2016 12:21
>To: dev@zookeeper.apache.org
>Cc: Chris Nauroth
>Subject: Re: We need to prioritize getting logging fixed in trunk/3.5
>
>Agreed, sounds like a good plan, +1.
>
>Thanks, Chris!
>
>-Flavio
>
>> On 17 Mar 2016, at 06:02, Patrick Hunt  wrote:
>> 
>> That makes sense to me as well. +1. Thank you Chris!
>> 
>> Patrick
>> 
>> On Wed, Mar 16, 2016 at 9:42 AM, Raúl Gutiérrez Segalés
>> wrote:
>>> +1. This sounds like a good plan. Thanks Chris!
>>> On Mar 16, 2016 9:36 AM, "Chris Nauroth" 
>>>wrote:
>>> 
 We now have multiple binding +1's for a revert.  To finalize the
 plan, here is what I propose:
 
 1. Full revert of ZOOKEEPER-1371, targeted to 3.5.2.
 
 2. Retarget ZOOKEEPER-1371 to 3.5.3 with the scope limited to just
 the SLF4J logging API changes.  We'd omit the build changes that
 dropped the SLF4J-Log4J 1.2 binding from the distro.  This would be
 a backwards-compatible change, and I believe it was the original
 intent of ZOOKEEPER-1371.  This is not critical to complete for
 3.5.3.  I'm just pushing it ahead to the next version.
 
 3. Retarget ZOOKEEPER-2342 to 3.6.0 for tracking Log4J 2 migration.
 This will have to happen someday since Log4J 1 is end of life, but
 it will likely be backwards-incompatible, and the change provides no
 value add to justify it for the 3.5 line.
 
 I'll wait 24 hours before proceeding with a revert in case anyone
 else wants to comment.
 
 --Chris Nauroth
 
 
 
 
 On 3/16/16, 6:47 AM, "Camille Fournier"  wrote:
 
> I'm a strong +1 to get this fixed even if it requires reverting the
> original patch. Broken logging is huge. Let's do whatever is
> expedient and sensible to fix it.
> 
> On Tue, Mar 15, 2016 at 7:27 PM, Chris Nauroth
> 
> wrote:
> 
>> Yes, that's basically my assessment too.  Copy-pasting my earlier
>> comment from ZOOKEEPER-1371:
>> 
>> "After this patch, ZooKeeper no longer produces any logging,
>> because there is no SLF4J binding jar available on the runtime
>> classpath."
>> 
>> 
>> There is no compatibility problem with switching to SLF4J
>> exclusively as our API of choice for logging instead of calling
>> the Log4J API.  The incompatible part is that the distro isn't
>> shipping with any SLF4J binding included.  Perhaps we can do a
>> partial revert of just that part of ZOOKEEPER-1371.
>> 
>> --Chris Nauroth
>> 
>> 
>> 
>> 
>> On 3/15/16, 11:54 AM, "Patrick Hunt"  wrote:
>> 
>>> Hm, I started looking at the original patch in more depth:
>>> 
>> 
>> 
 https://issues.apache.org/jira/secure/attachment/12773684/ZOOKEEPER-
 1371-
>> 0
>>> 5.patch
>>> 
>>> is the real root issue 2342 is trying to address the following
>>> line
>>> change:
>>> 
>>> ->> transitive="false"/>
>>> +>> transitive="false" conf="test->default"/>
>>> 
>>> Specifically that we changed from runtime to test only for this
>>> dependency? Perhaps we just need to revert that? I see some other
>>> magic happening in the build.xml file that I don't quite
>>> understand - adding a new target and NoLog4j... references.
>>> 
>>> Raul perhaps you can give more insight since it seems like you
>>> worked on 1371 most recently?
>>> 
>>> Patrick
>>> 
>>> 
>>> On Tue, Mar 15, 2016 at 11:41 AM, Chris Nauroth
>>>  wrote:
 I agree.  Even if we don't fully understand every minute
 technical detail of Log4J 2 vs. Log4J 1, I think we've learned
 enough from my work-in-progress patch to declare that a
 migration is too risky for
>> the
 3.5 line.  Reverting ZOOKEEPER-1371 (the earlier
>> backwards-incompatible
 logging change) is the better 

[jira] [Updated] (ZOOKEEPER-2364) "ant docs" fails on branch-3.5 due to missing releasenotes.xml.

[Patrick Hunt (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Patrick Hunt updated ZOOKEEPER-2364:

Attachment: ZOOKEEPER-2364.patch

[~cnauroth] can you give my patch a try? It turns out that "api" was working 
because of some special setup in the default forrest config. Took me about 4 
hours to figure this out. Arg! See 
https://forrest.apache.org/docs_0_90/faq.html#cli-xconf for more details.

With this patch we should remove releasenotes from the src/docs/... directory 
and use the HTML directly from Jira (my original intent but I only got half way 
there).

> "ant docs" fails on branch-3.5 due to missing releasenotes.xml.
> ---
>
> Key: ZOOKEEPER-2364
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2364
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: build, documentation
>Reporter: Chris Nauroth
>Assignee: Chris Nauroth
>Priority: Blocker
> Fix For: 3.5.2
>
> Attachments: ZOOKEEPER-2364-branch-3.5.001.patch, 
> ZOOKEEPER-2364-branch-3.5.002.patch, ZOOKEEPER-2364.002.patch, 
> ZOOKEEPER-2364.patch
>
>
> "ant docs" is failing on branch-3.5.  (Both trunk and branch-3.4 are fine.)  
> The root cause appears
> to be a missing file on branch-3.5: 
> src/docs/src/documentation/content/xdocs/releasenotes.xml.
>  This causes Forrest to report a failure due to broken hyperlinks targeting 
> releasenotes.html.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Jenkins pre-commit running JDK 8?

[Patrick Hunt]

Gavin (infra) fixed this. We should be back in business.

Patrick

On Sat, Mar 19, 2016 at 4:33 PM, Patrick Hunt  wrote:
> ps it doesn't look like anyone has changed that job config in quite some time:
>
> https://builds.apache.org/view/S-Z/view/ZooKeeper/job/PreCommit-ZOOKEEPER-Build/jobConfigHistory/
>
> Patrick
>
>
> On Sat, Mar 19, 2016 at 4:29 PM, Patrick Hunt  wrote:
>> Hi Chris. I filed this issue earlier this morning based on failures in
>> some of our other jobs:
>>
>> https://issues.apache.org/jira/browse/INFRA-11488
>>
>> It would help if you could comment on this jira, I don't believe what
>> I saw is the same but it sounds similar.
>>
>> Patrick
>>
>> On Sat, Mar 19, 2016 at 2:37 PM, Chris Nauroth  
>> wrote:
>>> Is anyone aware of recent changes in our Jenkins jobs that would have 
>>> started using JDK 8 instead of JDK 7 for pre-commit?  We're not ready for 
>>> this, because there are some different rules about JavaDocs in JDK 8, and 
>>> the ZooKeeper codebase currently triggers warnings due to violations of 
>>> those new rules.
>>>
>>> Here are examples of pre-commit jobs than ran with JDK 8:
>>>
>>> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3108/consoleText
>>>
>>> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3109/consoleText
>>>
>>> Those 2 builds ran on different Jenkins hosts, so it's not specific to a 
>>> particular host.
>>>
>>> The strange thing is that the job appears to be configured to use JDK 7, 
>>> and the file path in the output appears that it should be JDK 7, but it 
>>> still ends up using JDK 8.
>>>
>>> /home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7/bin/java
>>> java version "1.8.0_66"
>>> Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
>>> Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)
>>>
>>> If no one is aware of changes in our jobs that would have caused this, then 
>>> perhaps we'll need to ask infrastructure for help.  Maybe something strange 
>>> happened, like an accidental installation of JDK 8 at the JDK 7 path.
>>>
>>> --Chris Nauroth

ZooKeeper_branch34 - Build # 1460 - Failure

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch34/1460/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 219598 lines...]
[junit] 2016-03-20 01:39:05,687 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2016-03-20 01:39:05,687 [myid:] - INFO  [main:ClientBase@490] - 
STOPPING server
[junit] 2016-03-20 01:39:05,687 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2016-03-20 01:39:05,688 [myid:] - INFO  [main:ZooKeeperServer@469] 
- shutting down
[junit] 2016-03-20 01:39:05,688 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2016-03-20 01:39:05,688 [myid:] - INFO  
[main:PrepRequestProcessor@767] - Shutting down
[junit] 2016-03-20 01:39:05,688 [myid:] - INFO  
[main:SyncRequestProcessor@209] - Shutting down
[junit] 2016-03-20 01:39:05,689 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@187] - SyncRequestProcessor exited!
[junit] 2016-03-20 01:39:05,689 [myid:] - INFO  
[main:FinalRequestProcessor@415] - shutdown of request processor complete
[junit] 2016-03-20 01:39:05,690 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-03-20 01:39:05,690 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-03-20 01:39:05,691 [myid:] - INFO  [main:ClientBase@443] - 
STARTING server
[junit] 2016-03-20 01:39:05,692 [myid:] - INFO  [main:ClientBase@364] - 
CREATING server instance 127.0.0.1:11221
[junit] 2016-03-20 01:39:05,692 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2016-03-20 01:39:05,693 [myid:] - INFO  [main:ClientBase@339] - 
STARTING server instance 127.0.0.1:11221
[junit] 2016-03-20 01:39:05,693 [myid:] - INFO  [main:ZooKeeperServer@170] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/branch-3.4/build/test/tmp/test2582699139395028512.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/branch-3.4/build/test/tmp/test2582699139395028512.junit.dir/version-2
[junit] 2016-03-20 01:39:05,694 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2016-03-20 01:39:05,698 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-03-20 01:39:05,699 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:37101
[junit] 2016-03-20 01:39:05,699 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing 
stat command from /127.0.0.1:37101
[junit] 2016-03-20 01:39:05,700 [myid:] - INFO  
[Thread-5:NIOServerCnxn$StatCommand@663] - Stat command output
[junit] 2016-03-20 01:39:05,700 [myid:] - INFO  
[Thread-5:NIOServerCnxn@1008] - Closed socket connection for client 
/127.0.0.1:37101 (no session established for client)
[junit] 2016-03-20 01:39:05,700 [myid:] - INFO  [main:JMXEnv@229] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-03-20 01:39:05,702 [myid:] - INFO  [main:JMXEnv@246] - 
expect:InMemoryDataTree
[junit] 2016-03-20 01:39:05,703 [myid:] - INFO  [main:JMXEnv@250] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2016-03-20 01:39:05,703 [myid:] - INFO  [main:JMXEnv@246] - 
expect:StandaloneServer_port
[junit] 2016-03-20 01:39:05,703 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2016-03-20 01:39:05,704 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 31162
[junit] 2016-03-20 01:39:05,704 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2016-03-20 01:39:05,704 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2016-03-20 01:39:05,704 [myid:] - INFO  [main:ClientBase@520] - 
tearDown starting
[junit] 2016-03-20 01:39:05,767 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x15391acf840 closed
[junit] 2016-03-20 01:39:05,767 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x15391acf840
[junit] 2016-03-20 01:39:05,767 [myid:] - INFO  [main:ClientBase@490] - 
STOPPING server
[junit] 2016-03-20 01:39:05,768 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 

[jira] [Updated] (ZOOKEEPER-2391) setMin/MaxSessionTimeout of ZookeeperServer are implemented in quite a weak way

[Kazuaki Banzai (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kazuaki Banzai updated ZOOKEEPER-2391:
--
Attachment: ZOOKEEPER-2391.patch

There are two possible ways to respond to invalid parameters: Call using 
invalid parameters could be ignored, or the method could throw an exception. 
The second approach finds flawed code more proactively but may cause problems 
with existing faulty clients. The patch implements the second solution, because 
it would be better in the long term to adapt strict parameter checking.

> setMin/MaxSessionTimeout of ZookeeperServer are implemented in quite a weak 
> way
> ---
>
> Key: ZOOKEEPER-2391
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2391
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: documentation, server
>Reporter: Kazuaki Banzai
>Priority: Minor
> Attachments: ZOOKEEPER-2391.patch
>
>
> setMin/MaxSessionTimeout of ZookeeperServer are implemented in quite a weak 
> way.
> * -1 restores the default, but this is not documented.
> * values < -1 are permitted but make no sense.
> * min > max is permitted but makes not sense.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

ZooKeeper_branch35_jdk8 - Build # 17 - Failure

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch35_jdk8/17/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 388872 lines...]
 [exec] Log Message Received: [2016-03-20 
01:05:26,261:20712(0x2b3d5c0b8540):ZOO_INFO@testLogCallbackInit@993: 
testLogCallbackInit #8]
 [exec] Log Message Received: [2016-03-20 
01:05:26,261:20712(0x2b3d5c0b8540):ZOO_INFO@testLogCallbackInit@993: 
testLogCallbackInit #9]
 [exec] Log Message Received: [2016-03-20 
01:05:26,261:20712(0x2b3d5c0b8540):ZOO_INFO@zookeeper_close@3257: Closing 
zookeeper sessionId=0x101a0e9bad3000e to [127.0.0.1:22181]
 [exec] ]
 [exec]  : elapsed 1001 : OK
 [exec] Zookeeper_simpleSystem::testLogCallbackClearLog Message Received: 
[2016-03-20 01:05:26,261:20712(0x2b3d5c0b8540):ZOO_INFO@log_env@1027: Client 
environment:zookeeper.version=zookeeper C client 3.5.1]
 [exec] Log Message Received: [2016-03-20 
01:05:26,261:20712(0x2b3d5c0b8540):ZOO_INFO@log_env@1031: Client 
environment:host.name=asf910.gq1.ygridcore.net]
 [exec] Log Message Received: [2016-03-20 
01:05:26,261:20712(0x2b3d5c0b8540):ZOO_INFO@log_env@1038: Client 
environment:os.name=Linux]
 [exec] Log Message Received: [2016-03-20 
01:05:26,261:20712(0x2b3d5c0b8540):ZOO_INFO@log_env@1039: Client 
environment:os.arch=3.13.0-36-lowlatency]
 [exec] Log Message Received: [2016-03-20 
01:05:26,261:20712(0x2b3d5c0b8540):ZOO_INFO@log_env@1040: Client 
environment:os.version=#63-Ubuntu SMP PREEMPT Wed Sep 3 21:56:12 UTC 2014]
 [exec] Log Message Received: [2016-03-20 
01:05:26,262:20712(0x2b3d5c0b8540):ZOO_INFO@log_env@1048: Client 
environment:user.name=jenkins]
 [exec] Log Message Received: [2016-03-20 
01:05:26,262:20712(0x2b3d5c0b8540):ZOO_INFO@log_env@1056: Client 
environment:user.home=/home/jenkins]
 [exec] Log Message Received: [2016-03-20 
01:05:26,262:20712(0x2b3d5c0b8540):ZOO_INFO@log_env@1068: Client 
environment:user.dir=/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk8/branch-3.5/build/test/test-cppunit]
 [exec] Log Message Received: [2016-03-20 
01:05:26,262:20712(0x2b3d5c0b8540):ZOO_INFO@zookeeper_init_internal@: 
Initiating client connection, host=127.0.0.1:22181 sessionTimeout=1 
watcher=0x45d2a0 sessionId=0 sessionPasswd= context=0x7fff46cbf6d0 
flags=0]
 [exec] Log Message Received: [2016-03-20 
01:05:26,263:20712(0x2b3d5e747700):ZOO_INFO@check_events@2357: initiated 
connection to server [127.0.0.1:22181]]
 [exec] Log Message Received: [2016-03-20 
01:05:26,292:20712(0x2b3d5e747700):ZOO_INFO@check_events@2409: session 
establishment complete on server [127.0.0.1:22181], 
sessionId=0x101a0e9bad3000f, negotiated timeout=1 ]
 [exec]  : elapsed 1000 : OK
 [exec] Zookeeper_simpleSystem::testAsyncWatcherAutoReset ZooKeeper server 
started : elapsed 10524 : OK
 [exec] Zookeeper_simpleSystem::testDeserializeString : elapsed 0 : OK
 [exec] Zookeeper_simpleSystem::testFirstServerDown : elapsed 1000 : OK
 [exec] Zookeeper_simpleSystem::testNullData : elapsed 1037 : OK
 [exec] Zookeeper_simpleSystem::testIPV6 : elapsed 1022 : OK
 [exec] Zookeeper_simpleSystem::testCreate : elapsed 1028 : OK
 [exec] Zookeeper_simpleSystem::testPath : elapsed 1071 : OK
 [exec] Zookeeper_simpleSystem::testPathValidation : elapsed 1150 : OK
 [exec] Zookeeper_simpleSystem::testPing : elapsed 18141 : OK
 [exec] Zookeeper_simpleSystem::testAcl : elapsed 1025 : OK
 [exec] Zookeeper_simpleSystem::testChroot : elapsed 5099 : OK
 [exec] Zookeeper_simpleSystem::testAuth ZooKeeper server started ZooKeeper 
server started : elapsed 31079 : OK
 [exec] Zookeeper_simpleSystem::testHangingClient : elapsed 1058 : OK
 [exec] Zookeeper_simpleSystem::testWatcherAutoResetWithGlobal ZooKeeper 
server started ZooKeeper server started ZooKeeper server started : elapsed 
16161 : OK
 [exec] Zookeeper_simpleSystem::testWatcherAutoResetWithLocal ZooKeeper 
server started ZooKeeper server started ZooKeeper server started : elapsed 
16980 : OK
 [exec] Zookeeper_simpleSystem::testGetChildren2 : elapsed 1141 : OK
 [exec] Zookeeper_simpleSystem::testLastZxid : elapsed 4541 : OK
 [exec] Zookeeper_simpleSystem::testRemoveWatchers ZooKeeper server started 
: elapsed 4584 : OK
 [exec] Zookeeper_readOnly::testReadOnly : elapsed 4134 : OK
 [exec] 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk8/branch-3.5/src/c/tests/TestReconfig.cc:183:
 Assertion: equality assertion failed [Expected: 1, Actual  : 0]
 [exec] Failures !!!
 [exec] Run: 72   Failure total: 1   Failures: 1   Errors: 0
 [exec] FAIL: zktest-mt
 [exec] ==
 [exec] 1 of 2 tests failed
 [exec] Please report to u...@zookeeper.apache.org
 [exec] ==
 [exec] make[1]: 

Re: We need to prioritize getting logging fixed in trunk/3.5

[Raúl Gutiérrez Segalés]

+1. This sounds like a good plan. Thanks Chris!
On Mar 16, 2016 9:36 AM, "Chris Nauroth"  wrote:

> We now have multiple binding +1's for a revert.  To finalize the plan,
> here is what I propose:
>
> 1. Full revert of ZOOKEEPER-1371, targeted to 3.5.2.
>
> 2. Retarget ZOOKEEPER-1371 to 3.5.3 with the scope limited to just the
> SLF4J logging API changes.  We'd omit the build changes that dropped the
> SLF4J-Log4J 1.2 binding from the distro.  This would be a
> backwards-compatible change, and I believe it was the original intent of
> ZOOKEEPER-1371.  This is not critical to complete for 3.5.3.  I'm just
> pushing it ahead to the next version.
>
> 3. Retarget ZOOKEEPER-2342 to 3.6.0 for tracking Log4J 2 migration.  This
> will have to happen someday since Log4J 1 is end of life, but it will
> likely be backwards-incompatible, and the change provides no value add to
> justify it for the 3.5 line.
>
> I'll wait 24 hours before proceeding with a revert in case anyone else
> wants to comment.
>
> --Chris Nauroth
>
>
>
>
> On 3/16/16, 6:47 AM, "Camille Fournier"  wrote:
>
> >I'm a strong +1 to get this fixed even if it requires reverting the
> >original patch. Broken logging is huge. Let's do whatever is expedient and
> >sensible to fix it.
> >
> >On Tue, Mar 15, 2016 at 7:27 PM, Chris Nauroth 
> >wrote:
> >
> >> Yes, that's basically my assessment too.  Copy-pasting my earlier
> >>comment
> >> from ZOOKEEPER-1371:
> >>
> >> "After this patch, ZooKeeper no longer produces any logging, because
> >>there
> >> is no SLF4J binding jar available on the runtime classpath."
> >>
> >>
> >> There is no compatibility problem with switching to SLF4J exclusively as
> >> our API of choice for logging instead of calling the Log4J API.  The
> >> incompatible part is that the distro isn't shipping with any SLF4J
> >>binding
> >> included.  Perhaps we can do a partial revert of just that part of
> >> ZOOKEEPER-1371.
> >>
> >> --Chris Nauroth
> >>
> >>
> >>
> >>
> >> On 3/15/16, 11:54 AM, "Patrick Hunt"  wrote:
> >>
> >> >Hm, I started looking at the original patch in more depth:
> >> >
> >>
> >>
> https://issues.apache.org/jira/secure/attachment/12773684/ZOOKEEPER-1371-
> >>0
> >> >5.patch
> >> >
> >> >is the real root issue 2342 is trying to address the following line
> >> >change:
> >> >
> >> >- >> >transitive="false"/>
> >> >+ >> >transitive="false" conf="test->default"/>
> >> >
> >> >Specifically that we changed from runtime to test only for this
> >> >dependency? Perhaps we just need to revert that? I see some other
> >> >magic happening in the build.xml file that I don't quite understand -
> >> >adding a new target and NoLog4j... references.
> >> >
> >> >Raul perhaps you can give more insight since it seems like you worked
> >> >on 1371 most recently?
> >> >
> >> >Patrick
> >> >
> >> >
> >> >On Tue, Mar 15, 2016 at 11:41 AM, Chris Nauroth
> >> > wrote:
> >> >> I agree.  Even if we don't fully understand every minute technical
> >> >>detail
> >> >> of Log4J 2 vs. Log4J 1, I think we've learned enough from my
> >> >> work-in-progress patch to declare that a migration is too risky for
> >>the
> >> >> 3.5 line.  Reverting ZOOKEEPER-1371 (the earlier
> >>backwards-incompatible
> >> >> logging change) is the better choice for the interest of proceeding
> >>with
> >> >> 3.5 releases.
> >> >>
> >> >> --Chris Nauroth
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> On 3/15/16, 11:23 AM, "Patrick Hunt"  wrote:
> >> >>
> >> >>>I just commented on ZOOKEEPER-2342... not sure I fully understand all
> >> >>>the issues to be honest. Given how much we're trying to do in 3.5 it
> >> >>>seems like it would be prudent to wait on 1371 until 3.6... IMO. :-)
> >> >>>
> >> >>>Patrick
> >> >>>
> >> >>>On Tue, Mar 15, 2016 at 11:15 AM, Chris Nauroth
> >> >>> wrote:
> >>  At this point, I am +1 for a revert of the patch that introduced
> >>the
> >>  problem (ZOOKEEPER-1371).  We need more time to come up with a
> >> migration
> >>  path to Log4J 2 that minimizes impact on operators.  That will take
> >> time,
> >>  and I'd prefer that we don't hold up 3.5.2-alpha for it.
> >> 
> >>  --Chris Nauroth
> >> 
> >> 
> >> 
> >> 
> >>  On 3/15/16, 11:08 AM, "Patrick Hunt"  wrote:
> >> 
> >> >Hi folks, can we prioritize getting logging fixed? It's causing
> >>test
> >> >failures, e.g.:
> >> >
> >> https://builds.apache.org/job/ZooKeeper-trunk/2850/artifact/trunk/buil
> >> >d/
> >> >tm
> >> >p/zk.log
> >> >
> >> >This is the jira:
> >> >https://issues.apache.org/jira/browse/ZOOKEEPER-2342
> >> >
> >> >
> >> >Perhaps we should revert the change that caused this in the first
> >> >place.
> >> >
> >> >Patrick
> >> >
> >> 
> >> >>>
> >> >>
> >> >
> >>
> >>
>
>

[jira] [Updated] (ZOOKEEPER-1106) mt c client core when create node

[Patrick Hunt (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Patrick Hunt updated ZOOKEEPER-1106:

Assignee: zhang yafei

> mt c client core  when create node
> --
>
> Key: ZOOKEEPER-1106
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1106
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: c client
>Affects Versions: 3.3.2
>Reporter: jiang guangran
>Assignee: zhang yafei
> Attachments: patch.txt
>
>
> in deserialize_CreateResponse
>rc = rc ? : in->deserialize_String(in, "path", >path);
>in deserialize_String
>   len = -1
>   so v->path is uninitialised, and free, so core
> do_io thread
> #0  0x0039fb030265 in raise () from /lib64/libc.so.6
> #1  0x0039fb031d10 in abort () from /lib64/libc.so.6
> #2  0x0039fb06a84b in __libc_message () from /lib64/libc.so.6
> #3  0x0039fb0722ef in _int_free () from /lib64/libc.so.6
> #4  0x0039fb07273b in free () from /lib64/libc.so.6
> #5  0x2b0afd755dd1 in deallocate_String (s=0x5a490f40) at 
> src/recordio.c:29
> #6  0x2b0afd754ade in zookeeper_process (zh=0x131e3870, events= optimized out>) at src/zookeeper.c:2071
> #7  0x2b0afd75b2ef in do_io (v=) at 
> src/mt_adaptor.c:310
> #8  0x0039fb8064a7 in start_thread () from /lib64/libpthread.so.0
> #9  0x0039fb0d3c2d in clone () from /lib64/libc.so.6
> create_node thread
> #0  0x0039fb80ab99 in pthread_cond_wait@@GLIBC_2.3.2 () from 
> /lib64/libpthread.so.0
> #1  0x2b0afd75af5c in wait_sync_completion (sc=0x131e4c90) at 
> src/mt_adaptor.c:82
> #2  0x2b0afd751750 in zoo_create (zh=0x131e3870, path=0x13206fa8 
> "/jsq/zr2/hb/10.250.8.139:8102", 
> value=0x131e86a8 
> "\n\021\061\060.250.8.139:8102\022\035/home/shaoqiang/workdir2/qrs/\030\001 
> \001*%\n\020\n", 
> valuelen=102, acl=0x2b0afd961700, flags=1, path_buffer=0x0, 
> path_buffer_len=0) at src/zookeeper.c:3028



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

ZooKeeper_branch35_jdk7 - Build # 451 - Failure

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch35_jdk7/451/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 382615 lines...]
 [exec] Log Message Received: [2016-03-19 
23:46:09,456:6111(0x2ab9bd914540):ZOO_INFO@testLogCallbackInit@993: 
testLogCallbackInit #8]
 [exec] Log Message Received: [2016-03-19 
23:46:09,456:6111(0x2ab9bd914540):ZOO_INFO@testLogCallbackInit@993: 
testLogCallbackInit #9]
 [exec] Log Message Received: [2016-03-19 
23:46:09,456:6111(0x2ab9bd914540):ZOO_INFO@zookeeper_close@3257: Closing 
zookeeper sessionId=0x100ea245632000e to [127.0.0.1:22181]
 [exec] ]
 [exec]  : elapsed 1001 : OK
 [exec] Zookeeper_simpleSystem::testLogCallbackClearLog Message Received: 
[2016-03-19 23:46:09,456:6111(0x2ab9bd914540):ZOO_INFO@log_env@1027: Client 
environment:zookeeper.version=zookeeper C client 3.5.1]
 [exec] Log Message Received: [2016-03-19 
23:46:09,456:6111(0x2ab9bd914540):ZOO_INFO@log_env@1031: Client 
environment:host.name=proserpina.apache.org]
 [exec] Log Message Received: [2016-03-19 
23:46:09,456:6111(0x2ab9bd914540):ZOO_INFO@log_env@1038: Client 
environment:os.name=Linux]
 [exec] Log Message Received: [2016-03-19 
23:46:09,456:6111(0x2ab9bd914540):ZOO_INFO@log_env@1039: Client 
environment:os.arch=3.13.0-36-lowlatency]
 [exec] Log Message Received: [2016-03-19 
23:46:09,456:6111(0x2ab9bd914540):ZOO_INFO@log_env@1040: Client 
environment:os.version=#63-Ubuntu SMP PREEMPT Wed Sep 3 21:56:12 UTC 2014]
 [exec] Log Message Received: [2016-03-19 
23:46:09,456:6111(0x2ab9bd914540):ZOO_INFO@log_env@1048: Client 
environment:user.name=jenkins]
 [exec] Log Message Received: [2016-03-19 
23:46:09,456:6111(0x2ab9bd914540):ZOO_INFO@log_env@1056: Client 
environment:user.home=/home/jenkins]
 [exec] Log Message Received: [2016-03-19 
23:46:09,456:6111(0x2ab9bd914540):ZOO_INFO@log_env@1068: Client 
environment:user.dir=/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7/branch-3.5/build/test/test-cppunit]
 [exec] Log Message Received: [2016-03-19 
23:46:09,456:6111(0x2ab9bd914540):ZOO_INFO@zookeeper_init_internal@: 
Initiating client connection, host=127.0.0.1:22181 sessionTimeout=1 
watcher=0x45d2a0 sessionId=0 sessionPasswd= context=0x7fff12770130 
flags=0]
 [exec] Log Message Received: [2016-03-19 
23:46:09,457:6111(0x2ab9bffa3700):ZOO_INFO@check_events@2357: initiated 
connection to server [127.0.0.1:22181]]
 [exec] Log Message Received: [2016-03-19 
23:46:09,483:6111(0x2ab9bffa3700):ZOO_INFO@check_events@2409: session 
establishment complete on server [127.0.0.1:22181], 
sessionId=0x100ea245632000f, negotiated timeout=1 ]
 [exec]  : elapsed 1001 : OK
 [exec] Zookeeper_simpleSystem::testAsyncWatcherAutoReset ZooKeeper server 
started : elapsed 10253 : OK
 [exec] Zookeeper_simpleSystem::testDeserializeString : elapsed 0 : OK
 [exec] Zookeeper_simpleSystem::testFirstServerDown : elapsed 1001 : OK
 [exec] Zookeeper_simpleSystem::testNullData : elapsed 1043 : OK
 [exec] Zookeeper_simpleSystem::testIPV6 : elapsed 1018 : OK
 [exec] Zookeeper_simpleSystem::testCreate : elapsed 1019 : OK
 [exec] Zookeeper_simpleSystem::testPath : elapsed 1049 : OK
 [exec] Zookeeper_simpleSystem::testPathValidation : elapsed 1149 : OK
 [exec] Zookeeper_simpleSystem::testPing : elapsed 17659 : OK
 [exec] Zookeeper_simpleSystem::testAcl : elapsed 1026 : OK
 [exec] Zookeeper_simpleSystem::testChroot : elapsed 4111 : OK
 [exec] Zookeeper_simpleSystem::testAuth ZooKeeper server started ZooKeeper 
server started : elapsed 30616 : OK
 [exec] Zookeeper_simpleSystem::testHangingClient : elapsed 1049 : OK
 [exec] Zookeeper_simpleSystem::testWatcherAutoResetWithGlobal ZooKeeper 
server started ZooKeeper server started ZooKeeper server started : elapsed 
15006 : OK
 [exec] Zookeeper_simpleSystem::testWatcherAutoResetWithLocal ZooKeeper 
server started ZooKeeper server started ZooKeeper server started : elapsed 
15143 : OK
 [exec] Zookeeper_simpleSystem::testGetChildren2 : elapsed 1059 : OK
 [exec] Zookeeper_simpleSystem::testLastZxid : elapsed 4523 : OK
 [exec] Zookeeper_simpleSystem::testRemoveWatchers ZooKeeper server started 
: elapsed 4591 : OK
 [exec] Zookeeper_readOnly::testReadOnly : elapsed 4170 : OK
 [exec] OK (72)
 [exec] *** Error in `./zktest-mt': corrupted double-linked list: 
0x00c531b0 ***
 [exec] FAIL: zktest-mt
 [exec] ==
 [exec] 1 of 2 tests failed
 [exec] Please report to u...@zookeeper.apache.org
 [exec] ==
 [exec] make[1]: Leaving directory 
`/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7/branch-3.5/build/test/test-cppunit'
 [exec] /bin/bash: line 5:  6111 Aborted 

Failed: ZOOKEEPER-2393 PreCommit Build #3110

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2393
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3110/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 2378 lines...]
 [exec] PATCH APPLICATION FAILED
 [exec] 
 [exec] 
 [exec] 
 [exec] 
 [exec] -1 overall.  Here are the results of testing the latest attachment 
 [exec]   
http://issues.apache.org/jira/secure/attachment/12794306/ZOOKEEPER-2393.patch
 [exec]   against trunk revision 1735820.
 [exec] 
 [exec] +1 @author.  The patch does not contain any @author tags.
 [exec] 
 [exec] -1 tests included.  The patch doesn't appear to include any new 
or modified tests.
 [exec] Please justify why no new tests are needed 
for this patch.
 [exec] Also please list what manual steps were 
performed to verify this patch.
 [exec] 
 [exec] -1 patch.  The patch command could not apply the patch.
 [exec] 
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3110//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] 32c6b5f481f62480a64653975df9c12799501139 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1605:
 exec returned: 1

Total time: 57 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Recording test results
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
[description-setter] Description set: ZOOKEEPER-2393
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7



###
## FAILED TESTS (if any) 
##
No tests ran.

[jira] [Commented] (ZOOKEEPER-2393) Revert run-time dependency on log4j and slf4j-log4j12

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15203011#comment-15203011
 ] 

Hadoop QA commented on ZOOKEEPER-2393:
--

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12794306/ZOOKEEPER-2393.patch
  against trunk revision 1735820.

+1 @author.  The patch does not contain any @author tags.

-1 tests included.  The patch doesn't appear to include any new or modified 
tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

-1 patch.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3110//console

This message is automatically generated.

> Revert run-time dependency on log4j and slf4j-log4j12
> -
>
> Key: ZOOKEEPER-2393
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2393
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Reporter: Arshad Mohammad
>Assignee: Arshad Mohammad
>Priority: Blocker
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2393.patch, ZOOKEEPER-2393.patch
>
>
> Zookeeper run-time dependency on log4j and slf4j-log4j12 was removed as part 
> of ZOOKEEPER-1371 jira work.
> Following things were done as part of ZOOKEEPER-1371
> # Removed direct log4j API use from the code, instead used slf4j-api
> # Changed  log4j  and slf4j-log4j12 run time dependency to test time 
> dependency
> # Upgraded log4j, slf4j-log4j12  and slf4j-api versions.
> Here is the component wise version change
> #* (zookeeper)ivy.xml
> log4j: 1.2.15 -->1.7.5
> #* src\contrib\loggraph\ivy.xml
> slf4j-api: 1.6.1 -->1.7.5
> slf4j-log4j12:  1.6.1 -->1.7.5
> log4j: 1.2.15 -->1.7.5
> #* src\contrib\rest\ivy.xml
> slf4j-api: 1.6.1 -->1.7.5
> slf4j-log4j12:  1.6.1 -->1.7.5
> log4j: 1.2.15 -->1.7.5
> #* src\contrib\zooinspector\ivy.xml
> slf4j-api: 1.6.1 -->1.7.5
> slf4j-log4j12:  1.6.1 -->1.7.5
> log4j: 1.2.15 -->1.7.5
> The major problem with ZOOKEEPER-1371 change is that it removed run time 
> dependency. For more detail refer ZOOKEEPER-2342 discussion
> Now as part of this jira revert back only run time dependency, #2, on log4j 
> and slf4j-log4j12.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: ZOOKEEPER-2364: "ant docs" fails on branch-3.5 due to missing releasenotes.xml.

[Patrick Hunt]

It's very likely I changed/broke this originally. I've been meaning to
get back to the jira you created. I'll see what I can do.

Patrick

On Sat, Mar 19, 2016 at 2:58 PM, Chris Nauroth  wrote:
> Could someone please help review ZOOKEEPER-2364?  I consider this a blocker 
> for 3.5.2-alpha, because it blocks our ability to update the docs, and we 
> have several documentation patches to ship in 3.5.2-alpha.  Thank you.
>
> --Chris Nauroth

Re: Jenkins pre-commit running JDK 8?

[Patrick Hunt]

ps it doesn't look like anyone has changed that job config in quite some time:

https://builds.apache.org/view/S-Z/view/ZooKeeper/job/PreCommit-ZOOKEEPER-Build/jobConfigHistory/

Patrick


On Sat, Mar 19, 2016 at 4:29 PM, Patrick Hunt  wrote:
> Hi Chris. I filed this issue earlier this morning based on failures in
> some of our other jobs:
>
> https://issues.apache.org/jira/browse/INFRA-11488
>
> It would help if you could comment on this jira, I don't believe what
> I saw is the same but it sounds similar.
>
> Patrick
>
> On Sat, Mar 19, 2016 at 2:37 PM, Chris Nauroth  
> wrote:
>> Is anyone aware of recent changes in our Jenkins jobs that would have 
>> started using JDK 8 instead of JDK 7 for pre-commit?  We're not ready for 
>> this, because there are some different rules about JavaDocs in JDK 8, and 
>> the ZooKeeper codebase currently triggers warnings due to violations of 
>> those new rules.
>>
>> Here are examples of pre-commit jobs than ran with JDK 8:
>>
>> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3108/consoleText
>>
>> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3109/consoleText
>>
>> Those 2 builds ran on different Jenkins hosts, so it's not specific to a 
>> particular host.
>>
>> The strange thing is that the job appears to be configured to use JDK 7, and 
>> the file path in the output appears that it should be JDK 7, but it still 
>> ends up using JDK 8.
>>
>> /home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7/bin/java
>> java version "1.8.0_66"
>> Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
>> Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)
>>
>> If no one is aware of changes in our jobs that would have caused this, then 
>> perhaps we'll need to ask infrastructure for help.  Maybe something strange 
>> happened, like an accidental installation of JDK 8 at the JDK 7 path.
>>
>> --Chris Nauroth

Re: Jenkins pre-commit running JDK 8?

[Patrick Hunt]

Hi Chris. I filed this issue earlier this morning based on failures in
some of our other jobs:

https://issues.apache.org/jira/browse/INFRA-11488

It would help if you could comment on this jira, I don't believe what
I saw is the same but it sounds similar.

Patrick

On Sat, Mar 19, 2016 at 2:37 PM, Chris Nauroth  wrote:
> Is anyone aware of recent changes in our Jenkins jobs that would have started 
> using JDK 8 instead of JDK 7 for pre-commit?  We're not ready for this, 
> because there are some different rules about JavaDocs in JDK 8, and the 
> ZooKeeper codebase currently triggers warnings due to violations of those new 
> rules.
>
> Here are examples of pre-commit jobs than ran with JDK 8:
>
> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3108/consoleText
>
> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3109/consoleText
>
> Those 2 builds ran on different Jenkins hosts, so it's not specific to a 
> particular host.
>
> The strange thing is that the job appears to be configured to use JDK 7, and 
> the file path in the output appears that it should be JDK 7, but it still 
> ends up using JDK 8.
>
> /home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7/bin/java
> java version "1.8.0_66"
> Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
> Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)
>
> If no one is aware of changes in our jobs that would have caused this, then 
> perhaps we'll need to ask infrastructure for help.  Maybe something strange 
> happened, like an accidental installation of JDK 8 at the JDK 7 path.
>
> --Chris Nauroth

[jira] [Updated] (ZOOKEEPER-2392) Update netty to 3.7.1.Final

[Patrick Hunt (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Patrick Hunt updated ZOOKEEPER-2392:

Assignee: Hendy Irawan

> Update netty to 3.7.1.Final
> ---
>
> Key: ZOOKEEPER-2392
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2392
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 3.4.6, 3.5.1
>Reporter: Hendy Irawan
>Assignee: Hendy Irawan
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2128) zoo_aremove_watchers API is incorrect

[Patrick Hunt (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Patrick Hunt updated ZOOKEEPER-2128:

Fix Version/s: 3.6.0
   3.5.2

> zoo_aremove_watchers API is incorrect
> -
>
> Key: ZOOKEEPER-2128
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2128
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.6.0
>Reporter: Dave Gosselin
>Assignee: Dave Gosselin
> Fix For: 3.5.2, 3.6.0
>
>
> The C API for zoo_aremove_watchers incorrectly specifies the seventh argument 
> as a pointer to a function pointer.  It should be simply a function pointer 
> only.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Success: ZOOKEEPER-2290 PreCommit Build #3107

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2290
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3107/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 384529 lines...]
 [exec]   
http://issues.apache.org/jira/secure/attachment/12766278/ZOOKEEPER-2290-v5.patch
 [exec]   against trunk revision 1735646.
 [exec] 
 [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 2.0.3) 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-Build/3107//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3107//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3107//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] 772e8a727799937996dbdfa5ddc74684f60931f5 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 

BUILD SUCCESSFUL
Total time: 17 minutes 19 seconds
Archiving artifacts
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Recording test results
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
[description-setter] Description set: ZOOKEEPER-2290
Email was triggered for: Success
Sending email for trigger: Success
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7



###
## FAILED TESTS (if any) 
##
All tests passed

[jira] [Commented] (ZOOKEEPER-2392) Update netty to 3.7.1.Final

[Patrick Hunt (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15198843#comment-15198843
 ] 

Patrick Hunt commented on ZOOKEEPER-2392:
-

No apologies necessary. :-) Thanks!

> Update netty to 3.7.1.Final
> ---
>
> Key: ZOOKEEPER-2392
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2392
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 3.4.6, 3.5.1
>Reporter: Hendy Irawan
>Assignee: Hendy Irawan
>Priority: Minor
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2392.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

ZooKeeper_branch35_jdk7 - Build # 446 - Failure

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch35_jdk7/446/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 381065 lines...]
 [exec] Log Message Received: [2016-03-16 
13:38:18,724:18382(0x2abd561b6480):ZOO_INFO@testLogCallbackInit@993: 
testLogCallbackInit #8]
 [exec] Log Message Received: [2016-03-16 
13:38:18,724:18382(0x2abd561b6480):ZOO_INFO@testLogCallbackInit@993: 
testLogCallbackInit #9]
 [exec] Log Message Received: [2016-03-16 
13:38:18,725:18382(0x2abd561b6480):ZOO_INFO@zookeeper_close@3257: Closing 
zookeeper sessionId=0x17c5f2e to [127.0.0.1:22181]
 [exec] ]
 [exec]  : elapsed 1001 : OK
 [exec] Zookeeper_simpleSystem::testLogCallbackClearLog Message Received: 
[2016-03-16 13:38:18,725:18382(0x2abd561b6480):ZOO_INFO@log_env@1027: Client 
environment:zookeeper.version=zookeeper C client 3.5.1]
 [exec] Log Message Received: [2016-03-16 
13:38:18,725:18382(0x2abd561b6480):ZOO_INFO@log_env@1031: Client 
environment:host.name=jenkins-ubuntu-1404-4gb-5bb]
 [exec] Log Message Received: [2016-03-16 
13:38:18,725:18382(0x2abd561b6480):ZOO_INFO@log_env@1038: Client 
environment:os.name=Linux]
 [exec] Log Message Received: [2016-03-16 
13:38:18,725:18382(0x2abd561b6480):ZOO_INFO@log_env@1039: Client 
environment:os.arch=3.13.0-30-generic]
 [exec] Log Message Received: [2016-03-16 
13:38:18,725:18382(0x2abd561b6480):ZOO_INFO@log_env@1040: Client 
environment:os.version=#54-Ubuntu SMP Mon Jun 9 22:45:01 UTC 2014]
 [exec] Log Message Received: [2016-03-16 
13:38:18,725:18382(0x2abd561b6480):ZOO_INFO@log_env@1048: Client 
environment:user.name=jenkins]
 [exec] Log Message Received: [2016-03-16 
13:38:18,725:18382(0x2abd561b6480):ZOO_INFO@log_env@1056: Client 
environment:user.home=/home/jenkins]
 [exec] Log Message Received: [2016-03-16 
13:38:18,725:18382(0x2abd561b6480):ZOO_INFO@log_env@1068: Client 
environment:user.dir=/jenkins/workspace/ZooKeeper_branch35_jdk7/branch-3.5/build/test/test-cppunit]
 [exec] Log Message Received: [2016-03-16 
13:38:18,725:18382(0x2abd561b6480):ZOO_INFO@zookeeper_init_internal@: 
Initiating client connection, host=127.0.0.1:22181 sessionTimeout=1 
watcher=0x45d2f0 sessionId=0 sessionPasswd= context=0x7fffb292eeb0 
flags=0]
 [exec] Log Message Received: [2016-03-16 
13:38:18,725:18382(0x2abd588ad700):ZOO_INFO@check_events@2357: initiated 
connection to server [127.0.0.1:22181]]
 [exec] Log Message Received: [2016-03-16 
13:38:18,730:18382(0x2abd588ad700):ZOO_INFO@check_events@2409: session 
establishment complete on server [127.0.0.1:22181], 
sessionId=0x17c5f2f, negotiated timeout=1 ]
 [exec]  : elapsed 1001 : OK
 [exec] Zookeeper_simpleSystem::testAsyncWatcherAutoReset ZooKeeper server 
started : elapsed 10593 : OK
 [exec] Zookeeper_simpleSystem::testDeserializeString : elapsed 0 : OK
 [exec] Zookeeper_simpleSystem::testFirstServerDown : elapsed 1002 : OK
 [exec] Zookeeper_simpleSystem::testNullData : elapsed 1028 : OK
 [exec] Zookeeper_simpleSystem::testIPV6 : elapsed 1005 : OK
 [exec] Zookeeper_simpleSystem::testCreate : elapsed 1009 : OK
 [exec] Zookeeper_simpleSystem::testPath : elapsed 1015 : OK
 [exec] Zookeeper_simpleSystem::testPathValidation : elapsed 1051 : OK
 [exec] Zookeeper_simpleSystem::testPing : elapsed 17244 : OK
 [exec] Zookeeper_simpleSystem::testAcl : elapsed 1016 : OK
 [exec] Zookeeper_simpleSystem::testChroot : elapsed 3037 : OK
 [exec] Zookeeper_simpleSystem::testAuth ZooKeeper server started ZooKeeper 
server started : elapsed 31160 : OK
 [exec] Zookeeper_simpleSystem::testHangingClient : elapsed 1032 : OK
 [exec] Zookeeper_simpleSystem::testWatcherAutoResetWithGlobal ZooKeeper 
server started ZooKeeper server started ZooKeeper server started : elapsed 
15696 : OK
 [exec] Zookeeper_simpleSystem::testWatcherAutoResetWithLocal ZooKeeper 
server started ZooKeeper server started ZooKeeper server started : elapsed 
15780 : OK
 [exec] Zookeeper_simpleSystem::testGetChildren2 : elapsed 1035 : OK
 [exec] Zookeeper_simpleSystem::testLastZxid : elapsed 4515 : OK
 [exec] Zookeeper_simpleSystem::testRemoveWatchers ZooKeeper server started 
: elapsed 4722 : OK
 [exec] Zookeeper_readOnly::testReadOnly : elapsed 4332 : OK
 [exec] 
/jenkins/workspace/ZooKeeper_branch35_jdk7/branch-3.5/src/c/tests/TestReconfig.cc:183:
 Assertion: equality assertion failed [Expected: 1, Actual  : 0]
 [exec] Failures !!!
 [exec] Run: 72   Failure total: 1   Failures: 1   Errors: 0
 [exec] FAIL: zktest-mt
 [exec] make[1]: *** [check-TESTS] Error 1
 [exec] make: *** [check-am] Error 2
 [exec] ==
 [exec] 1 of 2 tests failed
 [exec] Please report to u...@zookeeper.apache.org
 [exec] 

ZooKeeper-trunk - Build # 2858 - Failure

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper-trunk/2858/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 387506 lines...]
jdk1.7.0_80/db/LICENSE
jdk1.7.0_80/db/RELEASE-NOTES.html
jdk1.7.0_80/db/lib/
jdk1.7.0_80/db/lib/derbyLocale_zh_CN.jar
jdk1.7.0_80/db/lib/derbynet.jar
jdk1.7.0_80/db/lib/derbyLocale_ja_JP.jar
jdk1.7.0_80/db/lib/derbyLocale_ru.jar
jdk1.7.0_80/db/lib/derbyLocale_es.jar
jdk1.7.0_80/db/lib/derbyLocale_it.jar
jdk1.7.0_80/db/lib/derby.jar
jdk1.7.0_80/db/lib/derbytools.jar
jdk1.7.0_80/db/lib/derbyLocale_hu.jar
jdk1.7.0_80/db/lib/derby.war
jdk1.7.0_80/db/lib/derbyrun.jar
jdk1.7.0_80/db/lib/derbyLocale_zh_TW.jar
jdk1.7.0_80/db/lib/derbyLocale_fr.jar
jdk1.7.0_80/db/lib/derbyclient.jar
jdk1.7.0_80/db/lib/derbyLocale_cs.jar
jdk1.7.0_80/db/lib/derbyLocale_pl.jar
jdk1.7.0_80/db/lib/derbyLocale_de_DE.jar
jdk1.7.0_80/db/lib/derbyLocale_ko_KR.jar
jdk1.7.0_80/db/lib/derbyLocale_pt_BR.jar
jdk1.7.0_80/db/3RDPARTY
jdk1.7.0_80/db/bin/
jdk1.7.0_80/db/bin/setNetworkClientCP.bat
jdk1.7.0_80/db/bin/dblook
jdk1.7.0_80/db/bin/NetworkServerControl
jdk1.7.0_80/db/bin/setEmbeddedCP
jdk1.7.0_80/db/bin/stopNetworkServer.bat
jdk1.7.0_80/db/bin/NetworkServerControl.bat
jdk1.7.0_80/db/bin/sysinfo
jdk1.7.0_80/db/bin/ij
jdk1.7.0_80/db/bin/setNetworkServerCP
jdk1.7.0_80/db/bin/setEmbeddedCP.bat
jdk1.7.0_80/db/bin/ij.bat
jdk1.7.0_80/db/bin/dblook.bat
jdk1.7.0_80/db/bin/sysinfo.bat
jdk1.7.0_80/db/bin/setNetworkClientCP
jdk1.7.0_80/db/bin/derby_common.bat
jdk1.7.0_80/db/bin/startNetworkServer.bat
jdk1.7.0_80/db/bin/startNetworkServer
jdk1.7.0_80/db/bin/setNetworkServerCP.bat
jdk1.7.0_80/db/bin/stopNetworkServer
jdk1.7.0_80/db/README-JDK.html
jdk1.7.0_80/db/NOTICE
jdk1.7.0_80/README.html
jdk1.7.0_80/THIRDPARTYLICENSEREADME.txt
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Recording fingerprints
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Updating ZOOKEEPER-2393
Recording test results
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Publishing Javadoc
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7



###
## FAILED TESTS (if any) 
##
All tests passed

[jira] [Commented] (ZOOKEEPER-2393) Revert run-time dependency on log4j and slf4j-log4j12

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15202993#comment-15202993
 ] 

Hudson commented on ZOOKEEPER-2393:
---

FAILURE: Integrated in ZooKeeper-trunk #2858 (See 
[https://builds.apache.org/job/ZooKeeper-trunk/2858/])
ZOOKEEPER-2393: Revert run-time dependency on log4j and slf4j-log4j12 (Arshad 
Mohammad via cnauroth) (cnauroth: 
[http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN=rev=1735820])
* trunk/CHANGES.txt
* trunk/build.xml
* trunk/docs/index.pdf
* trunk/docs/javaExample.pdf
* trunk/docs/linkmap.pdf
* trunk/docs/recipes.pdf
* trunk/docs/zookeeperAdmin.html
* trunk/docs/zookeeperAdmin.pdf
* trunk/docs/zookeeperHierarchicalQuorums.pdf
* trunk/docs/zookeeperInternals.pdf
* trunk/docs/zookeeperJMX.pdf
* trunk/docs/zookeeperObservers.pdf
* trunk/docs/zookeeperOver.pdf
* trunk/docs/zookeeperProgrammers.pdf
* trunk/docs/zookeeperQuotas.pdf
* trunk/docs/zookeeperReconfig.pdf
* trunk/docs/zookeeperStarted.pdf
* trunk/docs/zookeeperTutorial.pdf
* trunk/ivy.xml
* trunk/src/contrib/loggraph/ivy.xml
* trunk/src/contrib/rest/ivy.xml
* trunk/src/contrib/zooinspector/ivy.xml
* trunk/src/docs/src/documentation/content/xdocs/zookeeperAdmin.xml
* trunk/src/java/lib/log4j-1.2.16.LICENSE.txt
* trunk/src/java/lib/log4j-1.2.17.LICENSE.txt


> Revert run-time dependency on log4j and slf4j-log4j12
> -
>
> Key: ZOOKEEPER-2393
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2393
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Reporter: Arshad Mohammad
>Assignee: Arshad Mohammad
>Priority: Blocker
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2393.patch, ZOOKEEPER-2393.patch
>
>
> Zookeeper run-time dependency on log4j and slf4j-log4j12 was removed as part 
> of ZOOKEEPER-1371 jira work.
> Following things were done as part of ZOOKEEPER-1371
> # Removed direct log4j API use from the code, instead used slf4j-api
> # Changed  log4j  and slf4j-log4j12 run time dependency to test time 
> dependency
> # Upgraded log4j, slf4j-log4j12  and slf4j-api versions.
> Here is the component wise version change
> #* (zookeeper)ivy.xml
> log4j: 1.2.15 -->1.7.5
> #* src\contrib\loggraph\ivy.xml
> slf4j-api: 1.6.1 -->1.7.5
> slf4j-log4j12:  1.6.1 -->1.7.5
> log4j: 1.2.15 -->1.7.5
> #* src\contrib\rest\ivy.xml
> slf4j-api: 1.6.1 -->1.7.5
> slf4j-log4j12:  1.6.1 -->1.7.5
> log4j: 1.2.15 -->1.7.5
> #* src\contrib\zooinspector\ivy.xml
> slf4j-api: 1.6.1 -->1.7.5
> slf4j-log4j12:  1.6.1 -->1.7.5
> log4j: 1.2.15 -->1.7.5
> The major problem with ZOOKEEPER-1371 change is that it removed run time 
> dependency. For more detail refer ZOOKEEPER-2342 discussion
> Now as part of this jira revert back only run time dependency, #2, on log4j 
> and slf4j-log4j12.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

ZOOKEEPER-2364: "ant docs" fails on branch-3.5 due to missing releasenotes.xml.

[Chris Nauroth]

Could someone please help review ZOOKEEPER-2364?  I consider this a blocker for 
3.5.2-alpha, because it blocks our ability to update the docs, and we have 
several documentation patches to ship in 3.5.2-alpha.  Thank you.

--Chris Nauroth

Jenkins pre-commit running JDK 8?

[Chris Nauroth]

Is anyone aware of recent changes in our Jenkins jobs that would have started 
using JDK 8 instead of JDK 7 for pre-commit?  We're not ready for this, because 
there are some different rules about JavaDocs in JDK 8, and the ZooKeeper 
codebase currently triggers warnings due to violations of those new rules.

Here are examples of pre-commit jobs than ran with JDK 8:

https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3108/consoleText

https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3109/consoleText

Those 2 builds ran on different Jenkins hosts, so it's not specific to a 
particular host.

The strange thing is that the job appears to be configured to use JDK 7, and 
the file path in the output appears that it should be JDK 7, but it still ends 
up using JDK 8.

/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7/bin/java
java version "1.8.0_66"
Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)

If no one is aware of changes in our jobs that would have caused this, then 
perhaps we'll need to ask infrastructure for help.  Maybe something strange 
happened, like an accidental installation of JDK 8 at the JDK 7 path.

--Chris Nauroth

[jira] [Commented] (ZOOKEEPER-2382) Make fsync.warningthresholdms property configurable through zoo.cfg

[Patrick Hunt (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15198832#comment-15198832
 ] 

Patrick Hunt commented on ZOOKEEPER-2382:
-

Once ZOOKEEPER-2195 is addressed this becomes a moot point, no? You can set 
fsync.warningthresholdms in the config file and it will be handled correctly. 
Am I missing something?

> Make fsync.warningthresholdms property configurable through zoo.cfg
> ---
>
> Key: ZOOKEEPER-2382
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2382
> Project: ZooKeeper
>  Issue Type: Improvement
>Reporter: Biju Nair
>Assignee: Biju Nair
>Priority: Minor
> Attachments: ZOOKEEPER-2382-DRAFT.patch
>
>
> Currently {{fsync.warningthresholdms}} property can be set as a Java system 
> property. But it would help if this property can be made configurable through 
> {{zoo.cfg}} so that configuration management tools can leverage it. Also the 
> Java system property name should be standardized (refer ZOOKEEPER-2316) so 
> that the property is inline with the standard followed by other properties.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2139) Support multiple ZooKeeper client, with different configurations, in a single JVM

[Arshad Mohammad (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15201331#comment-15201331
 ] 

Arshad Mohammad commented on ZOOKEEPER-2139:


This feature implementation is done. There are many use case where multiple 
ZooKeeper client with different configuration reside in same JVM.
That is why it is important feature we should target for 3.5.2 release. Please 
review
ping [~phunt] [~fpj] [~rakeshr] [~rgs] [~cnauroth]

> Support multiple ZooKeeper client, with different configurations, in a single 
> JVM
> -
>
> Key: ZOOKEEPER-2139
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2139
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: java client
>Affects Versions: 3.5.0
>Reporter: Surendra Singh Lilhore
>Assignee: Arshad Mohammad
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2139-05.patch, ZOOKEEPER-2139-06.patch, 
> ZOOKEEPER-2139-07.patch, ZOOKEEPER-2139-08.patch, ZOOKEEPER-2139.patch, 
> ZOOKEEPER-2139.patch, ZOOKEEPER-2139_1.patch, ZOOKEEPER-2139_2.patch
>
>
> I have two ZK client in one JVM, one is secure client and second is normal 
> client (For non secure cluster).
> "zookeeper.sasl.client" system property is "true" by default, because of this 
> my second client connection is failing.
> We should pass all client configurations in client constructor like HDFS 
> client.
> For example :
> {code}
> public ZooKeeper(String connectString, int sessionTimeout, Watcher watcher, 
> Configuration conf) throws IOException
>   {
>   ..
>   ..
>   }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2393) Revert run-time dependency on log4j and slf4j-log4j12

[Chris Nauroth (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chris Nauroth updated ZOOKEEPER-2393:
-
Hadoop Flags: Reviewed

bq. From build build #3108 java version "1.8.0_66" is used instead of java 
version "1.7.0_80". So java doc warnings are not because of this patch

That's strange.  I can't figure out what would have caused this.  I tried 
submitting another pre-commit run manually, and the same thing happened.  It 
was even on a different Jenkins host.  I have started a thread on the dev list 
to discuss this.

I confirmed locally that the patch does not introduce new JavaDoc warnings.

+1.  I'll commit this shortly.


> Revert run-time dependency on log4j and slf4j-log4j12
> -
>
> Key: ZOOKEEPER-2393
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2393
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Reporter: Arshad Mohammad
>Assignee: Arshad Mohammad
>Priority: Blocker
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2393.patch, ZOOKEEPER-2393.patch
>
>
> Zookeeper run-time dependency on log4j and slf4j-log4j12 was removed as part 
> of ZOOKEEPER-1371 jira work.
> Following things were done as part of ZOOKEEPER-1371
> # Removed direct log4j API use from the code, instead used slf4j-api
> # Changed  log4j  and slf4j-log4j12 run time dependency to test time 
> dependency
> # Upgraded log4j, slf4j-log4j12  and slf4j-api versions.
> Here is the component wise version change
> #* (zookeeper)ivy.xml
> log4j: 1.2.15 -->1.7.5
> #* src\contrib\loggraph\ivy.xml
> slf4j-api: 1.6.1 -->1.7.5
> slf4j-log4j12:  1.6.1 -->1.7.5
> log4j: 1.2.15 -->1.7.5
> #* src\contrib\rest\ivy.xml
> slf4j-api: 1.6.1 -->1.7.5
> slf4j-log4j12:  1.6.1 -->1.7.5
> log4j: 1.2.15 -->1.7.5
> #* src\contrib\zooinspector\ivy.xml
> slf4j-api: 1.6.1 -->1.7.5
> slf4j-log4j12:  1.6.1 -->1.7.5
> log4j: 1.2.15 -->1.7.5
> The major problem with ZOOKEEPER-1371 change is that it removed run time 
> dependency. For more detail refer ZOOKEEPER-2342 discussion
> Now as part of this jira revert back only run time dependency, #2, on log4j 
> and slf4j-log4j12.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2393) Revert run-time dependency on log4j and slf4j-log4j12

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15202980#comment-15202980
 ] 

Hadoop QA commented on ZOOKEEPER-2393:
--

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12794306/ZOOKEEPER-2393.patch
  against trunk revision 1735646.

+1 @author.  The patch does not contain any @author tags.

-1 tests included.  The patch doesn't appear to include any new or modified 
tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

-1 javadoc.  The javadoc tool appears to have generated 100 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 2.0.3) 
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-Build/3109//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3109//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3109//console

This message is automatically generated.

> Revert run-time dependency on log4j and slf4j-log4j12
> -
>
> Key: ZOOKEEPER-2393
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2393
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Reporter: Arshad Mohammad
>Assignee: Arshad Mohammad
>Priority: Blocker
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2393.patch, ZOOKEEPER-2393.patch
>
>
> Zookeeper run-time dependency on log4j and slf4j-log4j12 was removed as part 
> of ZOOKEEPER-1371 jira work.
> Following things were done as part of ZOOKEEPER-1371
> # Removed direct log4j API use from the code, instead used slf4j-api
> # Changed  log4j  and slf4j-log4j12 run time dependency to test time 
> dependency
> # Upgraded log4j, slf4j-log4j12  and slf4j-api versions.
> Here is the component wise version change
> #* (zookeeper)ivy.xml
> log4j: 1.2.15 -->1.7.5
> #* src\contrib\loggraph\ivy.xml
> slf4j-api: 1.6.1 -->1.7.5
> slf4j-log4j12:  1.6.1 -->1.7.5
> log4j: 1.2.15 -->1.7.5
> #* src\contrib\rest\ivy.xml
> slf4j-api: 1.6.1 -->1.7.5
> slf4j-log4j12:  1.6.1 -->1.7.5
> log4j: 1.2.15 -->1.7.5
> #* src\contrib\zooinspector\ivy.xml
> slf4j-api: 1.6.1 -->1.7.5
> slf4j-log4j12:  1.6.1 -->1.7.5
> log4j: 1.2.15 -->1.7.5
> The major problem with ZOOKEEPER-1371 change is that it removed run time 
> dependency. For more detail refer ZOOKEEPER-2342 discussion
> Now as part of this jira revert back only run time dependency, #2, on log4j 
> and slf4j-log4j12.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2141) ACL cache in DataTree never removes entries

[Adam Milne-Smith (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199206#comment-15199206
 ] 

Adam Milne-Smith commented on ZOOKEEPER-2141:
-

I just ran the failing test locally 5 times with the patch and 5 times without 
the patch; it succeeded every time.

> ACL cache in DataTree never removes entries
> ---
>
> Key: ZOOKEEPER-2141
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2141
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.4.6
>Reporter: Karol Dudzinski
>Assignee: Adam Milne-Smith
> Attachments: ZOOKEEPER-2141.patch, ZOOKEEPER-2141.patch, 
> ZOOKEEPER-2141.patch, ZOOKEEPER-2141.patch, ZOOKEEPER-2141.patch
>
>
> The problem and potential solutions are discussed in 
> http://mail-archives.apache.org/mod_mbox/zookeeper-user/201502.mbox/browser
> I will attach a proposed patch in due course.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Failed: ZOOKEEPER-2393 PreCommit Build #3109

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2393
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3109/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 396865 lines...]
 [exec] -1 tests included.  The patch doesn't appear to include any new 
or modified tests.
 [exec] Please justify why no new tests are needed 
for this patch.
 [exec] Also please list what manual steps were 
performed to verify this patch.
 [exec] 
 [exec] -1 javadoc.  The javadoc tool appears to have generated 100 
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 2.0.3) 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-Build/3109//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3109//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3109//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] 3b08a801a24986f137d11a783617c0f5846144a8 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1646:
 exec returned: 3

Total time: 12 minutes 34 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Recording test results
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
[description-setter] Description set: ZOOKEEPER-2393
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/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:217)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)

[jira] [Resolved] (ZOOKEEPER-2374) Can not telnet 2181 port on aws ec2 server

[Patrick Hunt (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Patrick Hunt resolved ZOOKEEPER-2374.
-
Resolution: Cannot Reproduce

Closing given there has been no response. Please reopen if you have any further 
insight. Thanks for the report!

> Can not telnet 2181 port on aws ec2 server
> --
>
> Key: ZOOKEEPER-2374
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2374
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.4.6
>Reporter: zhupengfei
>Priority: Blocker
> Fix For: 3.4.9, 3.5.2, 3.6.0
>
>
> This is the second time I faced the problem on ec2, my activemq stomp port 
> have the same problem, but tcp message port works fine.
> I have checked zookeeper.out, no error log found. And aws technical support 
> tell it maybe caused by zookeeper.
> OS Type:
> Amazon Linux AMI
> Network Test Result:
> -bash-4.1$ netstat | grep 2181
> -bash-4.1$ telnet localhost 2181
> Trying 127.0.0.1...
> ^C
> -bash-4.1$ netstat -tunpl|grep 2181
> (Not all processes could be identified, non-owned process info
>  will not be shown, you would have to be root to see it all.)
> tcp0  0 :::2181 :::*
> LISTEN  17923/java
> -bash-4.1$ netstat -an |grep 2181
> tcp0  1 172.12.10.152:60171 172.12.10.152:2181  
> SYN_SENT
> tcp0  0 :::2181 :::*
> LISTEN  
> tcp0  1 :::127.0.0.1:36032  :::127.0.0.1:2181   
> SYN_SENT



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

ZooKeeper-trunk-openjdk7 - Build # 958 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/958/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 376055 lines...]
[junit] 2016-03-19 20:40:08,631 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree]
[junit] 2016-03-19 20:40:08,632 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port11222]
[junit] 2016-03-19 20:40:08,632 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222
[junit] 2016-03-19 20:40:08,633 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-03-19 20:40:08,636 [myid:] - INFO  [main:ClientBase@460] - 
STARTING server
[junit] 2016-03-19 20:40:08,637 [myid:] - INFO  [main:ClientBase@380] - 
CREATING server instance 127.0.0.1:11222
[junit] 2016-03-19 20:40:08,637 [myid:] - INFO  
[main:NIOServerCnxnFactory@673] - Configuring NIO connection handler with 10s 
sessionless connection timeout, 1 selector thread(s), 8 worker threads, and 64 
kB direct buffers.
[junit] 2016-03-19 20:40:08,638 [myid:] - INFO  
[main:NIOServerCnxnFactory@686] - binding to port 0.0.0.0/0.0.0.0:11222
[junit] 2016-03-19 20:40:08,639 [myid:] - INFO  [main:ClientBase@355] - 
STARTING server instance 127.0.0.1:11222
[junit] 2016-03-19 20:40:08,639 [myid:] - INFO  [main:ZooKeeperServer@858] 
- minSessionTimeout set to 6000
[junit] 2016-03-19 20:40:08,640 [myid:] - INFO  [main:ZooKeeperServer@867] 
- maxSessionTimeout set to 6
[junit] 2016-03-19 20:40:08,640 [myid:] - INFO  [main:ZooKeeperServer@156] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/build/test/tmp/test7910765524828093224.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/build/test/tmp/test7910765524828093224.junit.dir/version-2
[junit] 2016-03-19 20:40:08,642 [myid:] - INFO  [main:FileSnap@83] - 
Reading snapshot 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/build/test/tmp/test7910765524828093224.junit.dir/version-2/snapshot.b
[junit] 2016-03-19 20:40:08,647 [myid:] - INFO  [main:FileTxnSnapLog@298] - 
Snapshotting: 0xb to 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/build/test/tmp/test7910765524828093224.junit.dir/version-2/snapshot.b
[junit] 2016-03-19 20:40:08,651 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222
[junit] 2016-03-19 20:40:08,653 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@296]
 - Accepted socket connection from /127.0.0.1:37082
[junit] 2016-03-19 20:40:08,654 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@485] - Processing stat command from 
/127.0.0.1:37082
[junit] 2016-03-19 20:40:08,655 [myid:] - INFO  
[NIOWorkerThread-1:StatCommand@49] - Stat command output
[junit] 2016-03-19 20:40:08,656 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@607] - Closed socket connection for client 
/127.0.0.1:37082 (no session established for client)
[junit] 2016-03-19 20:40:08,656 [myid:] - INFO  [main:JMXEnv@228] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-03-19 20:40:08,660 [myid:] - INFO  [main:JMXEnv@245] - 
expect:InMemoryDataTree
[junit] 2016-03-19 20:40:08,660 [myid:] - INFO  [main:JMXEnv@249] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree
[junit] 2016-03-19 20:40:08,660 [myid:] - INFO  [main:JMXEnv@245] - 
expect:StandaloneServer_port
[junit] 2016-03-19 20:40:08,661 [myid:] - INFO  [main:JMXEnv@249] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222
[junit] 2016-03-19 20:40:08,661 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 30281
[junit] 2016-03-19 20:40:08,662 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 23
[junit] 2016-03-19 20:40:08,662 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testQuota
[junit] 2016-03-19 20:40:08,663 [myid:] - INFO  [main:ClientBase@537] - 
tearDown starting
[junit] 2016-03-19 20:40:08,691 [myid:] - INFO  [main:ZooKeeper@1110] - 
Session: 0x10048c67f81 closed
[junit] 2016-03-19 20:40:08,692 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@543] - EventThread shut down for 
session: 0x10048c67f81
[junit] 2016-03-19 20:40:08,692 [myid:] - INFO  [main:ClientBase@507] - 
STOPPING server
[junit] 2016-03-19 20:40:08,693 [myid:] - INFO  

ZooKeeper_branch35_jdk8 - Build # 13 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch35_jdk8/13/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 383478 lines...]
[junit] 2016-03-16 21:23:14,749 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree]
[junit] 2016-03-16 21:23:14,749 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port11222]
[junit] 2016-03-16 21:23:14,750 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222
[junit] 2016-03-16 21:23:14,750 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-03-16 21:23:14,756 [myid:] - INFO  [main:ClientBase@562] - 
fdcount after test is: 50 at start it was 35
[junit] 2016-03-16 21:23:14,756 [myid:] - INFO  [main:ClientBase@564] - 
sleeping for 20 secs
[junit] 2016-03-16 21:23:14,757 [myid:] - INFO  [main:ZKTestCase$1@65] - 
SUCCEEDED testQuota
[junit] 2016-03-16 21:23:14,757 [myid:] - INFO  [main:ZKTestCase$1@60] - 
FINISHED testQuota
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.946 sec

junit.run-concurrent:

junit.run:

test-core-java:

junit.run.nolog4j:

test-core-java-nolog4j:

call-test-cppunit:

init:

check-cppunit-makefile:

create-cppunit-makefile:

init:

check-cppunit-configure:

create-cppunit-configure:
[mkdir] Created dir: 
/x1/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk8/branch-3.5/build/test/test-cppunit
 [exec] checking for doxygen... no
 [exec] checking for perl... /usr/bin/perl
 [exec] checking for dot... no
 [exec] checking for a BSD-compatible install... /usr/bin/install -c
 [exec] checking whether build environment is sane... /bin/bash: 
/x1/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk8/branch-3.5/src/c/missing:
 No such file or directory
 [exec] confiyes
 [exec] checking for a thread-safe mkdir -p... /bin/mkdir -p
 [exec] checking for gawk... no
 [exec] checking for mawk... mawk
 [exec] checking whether make sets $(MAKE)... yes
 [exec] gure: WARNING: `missing' script is too old or missing
 [exec] 
/x1/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk8/branch-3.5/src/c/configure:
 line 4907: syntax error near unexpected token `1.10.2'
 [exec] 
/x1/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk8/branch-3.5/src/c/configure:
 line 4907: `   AM_PATH_CPPUNIT(1.10.2)'

BUILD FAILED
/x1/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk8/branch-3.5/build.xml:1361:
 The following error occurred while executing this line:
/x1/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk8/branch-3.5/build.xml:1320:
 The following error occurred while executing this line:
/x1/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk8/branch-3.5/build.xml:1312:
 exec returned: 2

Total time: 71 minutes 2 seconds
Build step 'Invoke Ant' marked build as failure
Archiving artifacts
Recording test results
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
All tests passed

[jira] [Updated] (ZOOKEEPER-1106) mt c client core when create node

[Patrick Hunt (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Patrick Hunt updated ZOOKEEPER-1106:

Assignee: (was: jiang guangran)

> mt c client core  when create node
> --
>
> Key: ZOOKEEPER-1106
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1106
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: c client
>Affects Versions: 3.3.2
>Reporter: jiang guangran
> Attachments: patch.txt
>
>
> in deserialize_CreateResponse
>rc = rc ? : in->deserialize_String(in, "path", >path);
>in deserialize_String
>   len = -1
>   so v->path is uninitialised, and free, so core
> do_io thread
> #0  0x0039fb030265 in raise () from /lib64/libc.so.6
> #1  0x0039fb031d10 in abort () from /lib64/libc.so.6
> #2  0x0039fb06a84b in __libc_message () from /lib64/libc.so.6
> #3  0x0039fb0722ef in _int_free () from /lib64/libc.so.6
> #4  0x0039fb07273b in free () from /lib64/libc.so.6
> #5  0x2b0afd755dd1 in deallocate_String (s=0x5a490f40) at 
> src/recordio.c:29
> #6  0x2b0afd754ade in zookeeper_process (zh=0x131e3870, events= optimized out>) at src/zookeeper.c:2071
> #7  0x2b0afd75b2ef in do_io (v=) at 
> src/mt_adaptor.c:310
> #8  0x0039fb8064a7 in start_thread () from /lib64/libpthread.so.0
> #9  0x0039fb0d3c2d in clone () from /lib64/libc.so.6
> create_node thread
> #0  0x0039fb80ab99 in pthread_cond_wait@@GLIBC_2.3.2 () from 
> /lib64/libpthread.so.0
> #1  0x2b0afd75af5c in wait_sync_completion (sc=0x131e4c90) at 
> src/mt_adaptor.c:82
> #2  0x2b0afd751750 in zoo_create (zh=0x131e3870, path=0x13206fa8 
> "/jsq/zr2/hb/10.250.8.139:8102", 
> value=0x131e86a8 
> "\n\021\061\060.250.8.139:8102\022\035/home/shaoqiang/workdir2/qrs/\030\001 
> \001*%\n\020\n", 
> valuelen=102, acl=0x2b0afd961700, flags=1, path_buffer=0x0, 
> path_buffer_len=0) at src/zookeeper.c:3028



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Failed: ZOOKEEPER-2297 PreCommit Build #3103

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2297
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3103/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 381343 lines...]
 [exec] Please justify why no new tests are needed 
for this patch.
 [exec] Also please list what manual steps were 
performed to verify this patch.
 [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 appears to introduce 2 new Findbugs 
(version 2.0.3) 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-Build/3103//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3103//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3103//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] a71141b57542fc0066d6355fcd13fe761b5ab95c logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1646:
 exec returned: 3

Total time: 12 minutes 5 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Compressed 554.40 KB of artifacts by 34.6% relative to #3102
Recording test results
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
[description-setter] Description set: ZOOKEEPER-2297
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7



###
## FAILED TESTS (if any) 
##
1 tests failed.
FAILED:  org.apache.zookeeper.server.ZxidRolloverTest.testSimpleRolloverFollower

Error Message:
Did not connect

Stack Trace:
java.util.concurrent.TimeoutException: Did not connect
at 
org.apache.zookeeper.test.ClientBase$CountdownWatcher.waitForConnected(ClientBase.java:132)
at 
org.apache.zookeeper.server.ZxidRolloverTest.waitForClientsConnected(ZxidRolloverTest.java:80)
at 
org.apache.zookeeper.server.ZxidRolloverTest.createNodes(ZxidRolloverTest.java:237)
at 
org.apache.zookeeper.server.ZxidRolloverTest.testSimpleRolloverFollower(ZxidRolloverTest.java:263)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)

[jira] [Commented] (ZOOKEEPER-1453) corrupted logs may not be correctly identified by FileTxnIterator

[Biju Nair (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15202057#comment-15202057
 ] 

Biju Nair commented on ZOOKEEPER-1453:
--

>From the discussion looks like the issue is resolved. Can this be closed?

> corrupted logs may not be correctly identified by FileTxnIterator
> -
>
> Key: ZOOKEEPER-1453
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1453
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.3.3
>Reporter: Patrick Hunt
>Priority: Critical
> Attachments: 10.10.5.123-withPath1489.tar.gz, 10.10.5.123.tar.gz, 
> 10.10.5.42-withPath1489.tar.gz, 10.10.5.42.tar.gz, 
> 10.10.5.44-withPath1489.tar.gz, 10.10.5.44.tar.gz
>
>
> See ZOOKEEPER-1449 for background on this issue. The main problem is that 
> during server recovery 
> org.apache.zookeeper.server.persistence.FileTxnLog.FileTxnIterator.next() 
> does not indicate if the available logs are valid or not. In some cases (say 
> a truncated record and a single txnlog in the datadir) we will not detect 
> that the file is corrupt, vs reaching the end of the file.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2392) Update netty to 3.7.1.Final

[Hendy Irawan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hendy Irawan updated ZOOKEEPER-2392:

Affects Version/s: 3.5.1

> Update netty to 3.7.1.Final
> ---
>
> Key: ZOOKEEPER-2392
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2392
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 3.4.6, 3.5.1
>Reporter: Hendy Irawan
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2342) ZooKeeper cannot write logs, because there is no SLF4J binding available on the runtime classpath.

[Camille Fournier (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15197330#comment-15197330
 ] 

Camille Fournier commented on ZOOKEEPER-2342:
-

I'm +1 for reverting the breaking patch. I don't honestly see the value in that 
change that outweighs the cost of trying to make it not backward-breaking. If 
someone wants to advocate for it with some concrete examples of the pain it is 
causing, I am all ears, otherwise, let's revert.

> ZooKeeper cannot write logs, because there is no SLF4J binding available on 
> the runtime classpath.
> --
>
> Key: ZOOKEEPER-2342
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2342
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Chris Nauroth
>Assignee: Chris Nauroth
>Priority: Blocker
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2342.001.patch
>
>
> ZOOKEEPER-1371 removed our source code dependency on Log4J.  It appears that 
> this also removed the Log4J SLF4J binding jar from the runtime classpath.  
> Without any SLF4J binding jar available on the runtime classpath, the it is 
> impossible to write logs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-1898) zookeeper-cli always return "0" as exit code

[Biju Nair (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15200875#comment-15200875
 ] 

Biju Nair commented on ZOOKEEPER-1898:
--

One approach to resolve this is to change 
[here|https://github.com/apache/zookeeper/blob/e78a7036db46fb4d507bff40384f0dcd31457323/src/java/main/org/apache/zookeeper/ZooKeeperMain.java#L359]
 in ZooKeeperMain.java to
{code}
…
 if (!processCmd(cl))
System.exit(1);
…
(code}
But looking at the {{cli}} classes the {{exec()}} methods all return {{false}} 
and in some cases return the boolean value for whether the option for watcher 
was made in the request. For e.g 
[CloseCommand.exec()|https://github.com/apache/zookeeper/blob/e78a7036db46fb4d507bff40384f0dcd31457323/src/java/main/org/apache/zookeeper/cli/CloseCommand.java#L43]
 returns {{false}} while 
[LsCommand.java|https://github.com/apache/zookeeper/blob/e78a7036db46fb4d507bff40384f0dcd31457323/src/java/main/org/apache/zookeeper/cli/LsCommand.java#L83]
 returns whether option "w" was passed in the request if the {{ls}} command is 
successful. If the return values from these cli command classes reflect whether 
the actual execution result of the commands executed the proposed change will 
work. It would be good to understand why these cli classes are returning 
{{false}}. [~phunt] any pointers you can provide here will be helpful. 

> zookeeper-cli always return "0" as exit code
> 
>
> Key: ZOOKEEPER-1898
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1898
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.4.5
> Environment: CentOS 6, Claudera Hadoop 5
>Reporter: Srinath Mantripragada
>Priority: Critical
> Fix For: 3.4.9, 3.5.2
>
>
> zookeeper-cli always return "0" as exit code whether the command has been 
> successful or not.
> Ex:
> Unsuccessful:
> {code}
> -bash-4.1$ zookeeper-client aa
> Connecting to localhost:2181
> 2014-03-20 14:43:01,361 [myid:] - INFO  [main:Environment@100] - Client 
> environment:zookeeper.version=3.4.5-cdh5.0.0-beta-2--1, built on 02/07/2014 
> 18:28 GMT
> 2014-03-20 14:43:01,368 [myid:] - INFO  [main:Environment@100] - Client 
> environment:host.name=ip-172-17-0-105.redlabnet.internal
> 2014-03-20 14:43:01,369 [myid:] - INFO  [main:Environment@100] - Client 
> environment:java.version=1.7.0_51
> 2014-03-20 14:43:01,370 [myid:] - INFO  [main:Environment@100] - Client 
> environment:java.vendor=Oracle Corporation
> 2014-03-20 14:43:01,371 [myid:] - INFO  [main:Environment@100] - Client 
> environment:java.home=/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.51.x86_64/jre
> 2014-03-20 14:43:01,371 [myid:] - INFO  [main:Environment@100] - Client 
> environment:java.class.path=/usr/lib/zookeeper/bin/../build/classes:/usr/lib/zookeeper/bin/../build/lib/*.jar:/usr/lib/zookeeper/bin/../lib/slf4j-log4j12.jar:/usr/lib/zookeeper/bin/../lib/slf4j-log4j12-1.7.5.jar:/usr/lib/zookeeper/bin/../lib/slf4j-api-1.7.5.jar:/usr/lib/zookeeper/bin/../lib/netty-3.2.2.Final.jar:/usr/lib/zookeeper/bin/../lib/log4j-1.2.15.jar:/usr/lib/zookeeper/bin/../lib/jline-0.9.94.jar:/usr/lib/zookeeper/bin/../zookeeper-3.4.5-cdh5.0.0-beta-2.jar:/usr/lib/zookeeper/bin/../src/java/lib/*.jar:/etc/zookeeper/conf::/etc/zookeeper/conf:/usr/lib/zookeeper/zookeeper.jar:/usr/lib/zookeeper/zookeeper-3.4.5-cdh5.0.0-beta-2.jar:/usr/lib/zookeeper/lib/slf4j-log4j12.jar:/usr/lib/zookeeper/lib/slf4j-api-1.7.5.jar:/usr/lib/zookeeper/lib/log4j-1.2.15.jar:/usr/lib/zookeeper/lib/slf4j-log4j12-1.7.5.jar:/usr/lib/zookeeper/lib/jline-0.9.94.jar:/usr/lib/zookeeper/lib/netty-3.2.2.Final.jar
> 2014-03-20 14:43:01,372 [myid:] - INFO  [main:Environment@100] - Client 
> environment:java.library.path=/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
> 2014-03-20 14:43:01,373 [myid:] - INFO  [main:Environment@100] - Client 
> environment:java.io.tmpdir=/tmp
> 2014-03-20 14:43:01,374 [myid:] - INFO  [main:Environment@100] - Client 
> environment:java.compiler=
> 2014-03-20 14:43:01,375 [myid:] - INFO  [main:Environment@100] - Client 
> environment:os.name=Linux
> 2014-03-20 14:43:01,375 [myid:] - INFO  [main:Environment@100] - Client 
> environment:os.arch=amd64
> 2014-03-20 14:43:01,376 [myid:] - INFO  [main:Environment@100] - Client 
> environment:os.version=2.6.32-431.3.1.el6.x86_64
> 2014-03-20 14:43:01,377 [myid:] - INFO  [main:Environment@100] - Client 
> environment:user.name=hdfs
> 2014-03-20 14:43:01,377 [myid:] - INFO  [main:Environment@100] - Client 
> environment:user.home=/var/lib/hadoop-hdfs
> 2014-03-20 14:43:01,378 [myid:] - INFO  [main:Environment@100] - Client 
> environment:user.dir=/var/lib/hadoop-hdfs
> 2014-03-20 14:43:01,382 [myid:] - INFO  [main:ZooKeeper@438] - Initiating 
> client connection, connectString=localhost:2181 sessionTimeout=3 
> 

[jira] [Commented] (ZOOKEEPER-2141) ACL cache in DataTree never removes entries

[Camille Fournier (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15197318#comment-15197318
 ] 

Camille Fournier commented on ZOOKEEPER-2141:
-

It's failing in AsyncHammerTest. Not sure if this is a flaky test or not. 
[~adammilnesmith_gs] if you'll run that test locally and see if you think it 
should pass, I'll review this and get it committed. Thanks for this, nice to 
see you folks contributing!

> ACL cache in DataTree never removes entries
> ---
>
> Key: ZOOKEEPER-2141
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2141
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.4.6
>Reporter: Karol Dudzinski
>Assignee: Adam Milne-Smith
> Attachments: ZOOKEEPER-2141.patch, ZOOKEEPER-2141.patch, 
> ZOOKEEPER-2141.patch, ZOOKEEPER-2141.patch, ZOOKEEPER-2141.patch
>
>
> The problem and potential solutions are discussed in 
> http://mail-archives.apache.org/mod_mbox/zookeeper-user/201502.mbox/browser
> I will attach a proposed patch in due course.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: We need to prioritize getting logging fixed in trunk/3.5

[Patrick Hunt]

That makes sense to me as well. +1. Thank you Chris!

Patrick

On Wed, Mar 16, 2016 at 9:42 AM, Raúl Gutiérrez Segalés  wrote:
> +1. This sounds like a good plan. Thanks Chris!
> On Mar 16, 2016 9:36 AM, "Chris Nauroth"  wrote:
>
>> We now have multiple binding +1's for a revert.  To finalize the plan,
>> here is what I propose:
>>
>> 1. Full revert of ZOOKEEPER-1371, targeted to 3.5.2.
>>
>> 2. Retarget ZOOKEEPER-1371 to 3.5.3 with the scope limited to just the
>> SLF4J logging API changes.  We'd omit the build changes that dropped the
>> SLF4J-Log4J 1.2 binding from the distro.  This would be a
>> backwards-compatible change, and I believe it was the original intent of
>> ZOOKEEPER-1371.  This is not critical to complete for 3.5.3.  I'm just
>> pushing it ahead to the next version.
>>
>> 3. Retarget ZOOKEEPER-2342 to 3.6.0 for tracking Log4J 2 migration.  This
>> will have to happen someday since Log4J 1 is end of life, but it will
>> likely be backwards-incompatible, and the change provides no value add to
>> justify it for the 3.5 line.
>>
>> I'll wait 24 hours before proceeding with a revert in case anyone else
>> wants to comment.
>>
>> --Chris Nauroth
>>
>>
>>
>>
>> On 3/16/16, 6:47 AM, "Camille Fournier"  wrote:
>>
>> >I'm a strong +1 to get this fixed even if it requires reverting the
>> >original patch. Broken logging is huge. Let's do whatever is expedient and
>> >sensible to fix it.
>> >
>> >On Tue, Mar 15, 2016 at 7:27 PM, Chris Nauroth 
>> >wrote:
>> >
>> >> Yes, that's basically my assessment too.  Copy-pasting my earlier
>> >>comment
>> >> from ZOOKEEPER-1371:
>> >>
>> >> "After this patch, ZooKeeper no longer produces any logging, because
>> >>there
>> >> is no SLF4J binding jar available on the runtime classpath."
>> >>
>> >>
>> >> There is no compatibility problem with switching to SLF4J exclusively as
>> >> our API of choice for logging instead of calling the Log4J API.  The
>> >> incompatible part is that the distro isn't shipping with any SLF4J
>> >>binding
>> >> included.  Perhaps we can do a partial revert of just that part of
>> >> ZOOKEEPER-1371.
>> >>
>> >> --Chris Nauroth
>> >>
>> >>
>> >>
>> >>
>> >> On 3/15/16, 11:54 AM, "Patrick Hunt"  wrote:
>> >>
>> >> >Hm, I started looking at the original patch in more depth:
>> >> >
>> >>
>> >>
>> https://issues.apache.org/jira/secure/attachment/12773684/ZOOKEEPER-1371-
>> >>0
>> >> >5.patch
>> >> >
>> >> >is the real root issue 2342 is trying to address the following line
>> >> >change:
>> >> >
>> >> >-> >> >transitive="false"/>
>> >> >+> >> >transitive="false" conf="test->default"/>
>> >> >
>> >> >Specifically that we changed from runtime to test only for this
>> >> >dependency? Perhaps we just need to revert that? I see some other
>> >> >magic happening in the build.xml file that I don't quite understand -
>> >> >adding a new target and NoLog4j... references.
>> >> >
>> >> >Raul perhaps you can give more insight since it seems like you worked
>> >> >on 1371 most recently?
>> >> >
>> >> >Patrick
>> >> >
>> >> >
>> >> >On Tue, Mar 15, 2016 at 11:41 AM, Chris Nauroth
>> >> > wrote:
>> >> >> I agree.  Even if we don't fully understand every minute technical
>> >> >>detail
>> >> >> of Log4J 2 vs. Log4J 1, I think we've learned enough from my
>> >> >> work-in-progress patch to declare that a migration is too risky for
>> >>the
>> >> >> 3.5 line.  Reverting ZOOKEEPER-1371 (the earlier
>> >>backwards-incompatible
>> >> >> logging change) is the better choice for the interest of proceeding
>> >>with
>> >> >> 3.5 releases.
>> >> >>
>> >> >> --Chris Nauroth
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> On 3/15/16, 11:23 AM, "Patrick Hunt"  wrote:
>> >> >>
>> >> >>>I just commented on ZOOKEEPER-2342... not sure I fully understand all
>> >> >>>the issues to be honest. Given how much we're trying to do in 3.5 it
>> >> >>>seems like it would be prudent to wait on 1371 until 3.6... IMO. :-)
>> >> >>>
>> >> >>>Patrick
>> >> >>>
>> >> >>>On Tue, Mar 15, 2016 at 11:15 AM, Chris Nauroth
>> >> >>> wrote:
>> >>  At this point, I am +1 for a revert of the patch that introduced
>> >>the
>> >>  problem (ZOOKEEPER-1371).  We need more time to come up with a
>> >> migration
>> >>  path to Log4J 2 that minimizes impact on operators.  That will take
>> >> time,
>> >>  and I'd prefer that we don't hold up 3.5.2-alpha for it.
>> >> 
>> >>  --Chris Nauroth
>> >> 
>> >> 
>> >> 
>> >> 
>> >>  On 3/15/16, 11:08 AM, "Patrick Hunt"  wrote:
>> >> 
>> >> >Hi folks, can we prioritize getting logging fixed? It's causing
>> >>test
>> >> >failures, e.g.:
>> >> >
>> >> https://builds.apache.org/job/ZooKeeper-trunk/2850/artifact/trunk/buil
>> >> >d/
>> >> >tm
>> >> >p/zk.log
>> >> >
>> >> 

[jira] [Commented] (ZOOKEEPER-2382) Make fsync.warningthresholdms property configurable through zoo.cfg

[Patrick Hunt (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199575#comment-15199575
 ] 

Patrick Hunt commented on ZOOKEEPER-2382:
-

Does this comment shed any light?

https://issues.apache.org/jira/browse/ZOOKEEPER-2195?focusedCommentId=15181928=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15181928

> Make fsync.warningthresholdms property configurable through zoo.cfg
> ---
>
> Key: ZOOKEEPER-2382
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2382
> Project: ZooKeeper
>  Issue Type: Improvement
>Reporter: Biju Nair
>Assignee: Biju Nair
>Priority: Minor
> Attachments: ZOOKEEPER-2382-DRAFT.patch
>
>
> Currently {{fsync.warningthresholdms}} property can be set as a Java system 
> property. But it would help if this property can be made configurable through 
> {{zoo.cfg}} so that configuration management tools can leverage it. Also the 
> Java system property name should be standardized (refer ZOOKEEPER-2316) so 
> that the property is inline with the standard followed by other properties.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-1371) Remove dependency on log4j in the source code.

[Chris Nauroth (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15197639#comment-15197639
 ] 

Chris Nauroth commented on ZOOKEEPER-1371:
--

We now have multiple binding +1's for a revert of this patch for 3.5.2 after 
discussion on the dev list.  I will wait 24 hours before proceeding with the 
revert, just to make sure everyone has been given an opportunity to comment.

> Remove dependency on log4j in the source code.
> --
>
> Key: ZOOKEEPER-1371
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1371
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.4.0, 3.4.1, 3.4.2, 3.4.3
>Reporter: Mahadev konar
>Assignee: Arshad Mohammad
>  Labels: patch
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-1371-05.patch, ZOOKEEPER-1371.patch, 
> ZOOKEEPER-1371.patch, ZOOKEEPER-1371.patch, ZOOKEEPER-1371.patch
>
>
> ZOOKEEPER-850 added slf4j to ZK. We still depend on log4j in our codebase. We 
> should remove the dependency on log4j so that we can make logging pluggable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

ZooKeeper_branch35_solaris - Build # 30 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch35_solaris/30/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 345325 lines...]
[junit] 2016-03-18 17:03:50,853 [myid:] - INFO  [main:ZooKeeperServer@867] 
- maxSessionTimeout set to 6
[junit] 2016-03-18 17:03:50,853 [myid:] - INFO  [main:ZooKeeperServer@156] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/branch-3.5/build/test/tmp/test436727874362116745.junit.dir/version-2
 snapdir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/branch-3.5/build/test/tmp/test436727874362116745.junit.dir/version-2
[junit] 2016-03-18 17:03:50,854 [myid:] - INFO  [main:FileSnap@83] - 
Reading snapshot 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/branch-3.5/build/test/tmp/test436727874362116745.junit.dir/version-2/snapshot.b
[junit] 2016-03-18 17:03:50,855 [myid:] - INFO  [main:FileTxnSnapLog@298] - 
Snapshotting: 0xb to 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/branch-3.5/build/test/tmp/test436727874362116745.junit.dir/version-2/snapshot.b
[junit] 2016-03-18 17:03:50,857 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222
[junit] 2016-03-18 17:03:50,857 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@296]
 - Accepted socket connection from /127.0.0.1:57004
[junit] 2016-03-18 17:03:50,858 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@485] - Processing stat command from 
/127.0.0.1:57004
[junit] 2016-03-18 17:03:50,858 [myid:] - INFO  
[NIOWorkerThread-1:StatCommand@49] - Stat command output
[junit] 2016-03-18 17:03:50,859 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@607] - Closed socket connection for client 
/127.0.0.1:57004 (no session established for client)
[junit] 2016-03-18 17:03:50,859 [myid:] - INFO  [main:JMXEnv@228] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-03-18 17:03:50,860 [myid:] - INFO  [main:JMXEnv@245] - 
expect:InMemoryDataTree
[junit] 2016-03-18 17:03:50,860 [myid:] - INFO  [main:JMXEnv@249] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree
[junit] 2016-03-18 17:03:50,861 [myid:] - INFO  [main:JMXEnv@245] - 
expect:StandaloneServer_port
[junit] 2016-03-18 17:03:50,861 [myid:] - INFO  [main:JMXEnv@249] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222
[junit] 2016-03-18 17:03:50,861 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 17763
[junit] 2016-03-18 17:03:50,861 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 24
[junit] 2016-03-18 17:03:50,861 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testQuota
[junit] 2016-03-18 17:03:50,862 [myid:] - INFO  [main:ClientBase@537] - 
tearDown starting
[junit] 2016-03-18 17:03:50,942 [myid:] - INFO  [main:ZooKeeper@1110] - 
Session: 0x12007ad284f closed
[junit] 2016-03-18 17:03:50,942 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@543] - EventThread shut down for 
session: 0x12007ad284f
[junit] 2016-03-18 17:03:50,942 [myid:] - INFO  [main:ClientBase@507] - 
STOPPING server
[junit] 2016-03-18 17:03:50,943 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@219]
 - accept thread exitted run method
[junit] 2016-03-18 17:03:50,943 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2016-03-18 17:03:50,943 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2016-03-18 17:03:50,943 [myid:] - INFO  
[ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - 
ConnnectionExpirerThread interrupted
[junit] 2016-03-18 17:03:50,944 [myid:] - INFO  [main:ZooKeeperServer@498] 
- shutting down
[junit] 2016-03-18 17:03:50,944 [myid:] - INFO  
[main:SessionTrackerImpl@232] - Shutting down
[junit] 2016-03-18 17:03:50,944 [myid:] - INFO  
[main:PrepRequestProcessor@967] - Shutting down
[junit] 2016-03-18 17:03:50,944 [myid:] - INFO  
[main:SyncRequestProcessor@191] - Shutting down
[junit] 2016-03-18 17:03:50,944 [myid:] - INFO  [ProcessThread(sid:0 
cport:11222)::PrepRequestProcessor@154] - PrepRequestProcessor exited loop!
[junit] 2016-03-18 17:03:50,945 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@169] - 

[jira] [Commented] (ZOOKEEPER-2141) ACL cache in DataTree never removes entries

[Camille Fournier (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15200102#comment-15200102
 ] 

Camille Fournier commented on ZOOKEEPER-2141:
-

This one failed on a cpp test
 TestReconfigServer::testRemoveConnectedFollowerStarting zookeeper ... FAILED 
TO START

Is this test flaky? Does anyone know? I don't think I can run the cpp tests 
from my computer.

> ACL cache in DataTree never removes entries
> ---
>
> Key: ZOOKEEPER-2141
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2141
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.4.6
>Reporter: Karol Dudzinski
>Assignee: Adam Milne-Smith
> Attachments: ZOOKEEPER-2141.patch, ZOOKEEPER-2141.patch, 
> ZOOKEEPER-2141.patch, ZOOKEEPER-2141.patch, ZOOKEEPER-2141.patch
>
>
> The problem and potential solutions are discussed in 
> http://mail-archives.apache.org/mod_mbox/zookeeper-user/201502.mbox/browser
> I will attach a proposed patch in due course.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

RE: We need to prioritize getting logging fixed in trunk/3.5

[Mohammad arshad]

>>1. Full revert of ZOOKEEPER-1371, targeted to 3.5.2.
Can we do partial revert instead of full 
 i) revert log4j and slf4j test scoped dependency to run time dependency, as it 
we earlier before this patch was merged
 ii) revert the changes done in build.xml
For partial revert we can create another path on top of latest code, I can 
create the patch.
This will avoid lot of duplicate effort
 
>>2. Retarget ZOOKEEPER-1371 to 3.5.3 with the scope ...
This is not required as if above is done
 
>> 3. Retarget ZOOKEEPER-2342 to 3.6.0 ...
+1 for this


-Original Message-
From: Flavio Junqueira [mailto:f...@apache.org] 
Sent: 17 March 2016 12:21
To: dev@zookeeper.apache.org
Cc: Chris Nauroth
Subject: Re: We need to prioritize getting logging fixed in trunk/3.5

Agreed, sounds like a good plan, +1.

Thanks, Chris!

-Flavio

> On 17 Mar 2016, at 06:02, Patrick Hunt  wrote:
> 
> That makes sense to me as well. +1. Thank you Chris!
> 
> Patrick
> 
> On Wed, Mar 16, 2016 at 9:42 AM, Raúl Gutiérrez Segalés  
> wrote:
>> +1. This sounds like a good plan. Thanks Chris!
>> On Mar 16, 2016 9:36 AM, "Chris Nauroth"  wrote:
>> 
>>> We now have multiple binding +1's for a revert.  To finalize the 
>>> plan, here is what I propose:
>>> 
>>> 1. Full revert of ZOOKEEPER-1371, targeted to 3.5.2.
>>> 
>>> 2. Retarget ZOOKEEPER-1371 to 3.5.3 with the scope limited to just 
>>> the SLF4J logging API changes.  We'd omit the build changes that 
>>> dropped the SLF4J-Log4J 1.2 binding from the distro.  This would be 
>>> a backwards-compatible change, and I believe it was the original 
>>> intent of ZOOKEEPER-1371.  This is not critical to complete for 
>>> 3.5.3.  I'm just pushing it ahead to the next version.
>>> 
>>> 3. Retarget ZOOKEEPER-2342 to 3.6.0 for tracking Log4J 2 migration.  
>>> This will have to happen someday since Log4J 1 is end of life, but 
>>> it will likely be backwards-incompatible, and the change provides no 
>>> value add to justify it for the 3.5 line.
>>> 
>>> I'll wait 24 hours before proceeding with a revert in case anyone 
>>> else wants to comment.
>>> 
>>> --Chris Nauroth
>>> 
>>> 
>>> 
>>> 
>>> On 3/16/16, 6:47 AM, "Camille Fournier"  wrote:
>>> 
 I'm a strong +1 to get this fixed even if it requires reverting the 
 original patch. Broken logging is huge. Let's do whatever is 
 expedient and sensible to fix it.
 
 On Tue, Mar 15, 2016 at 7:27 PM, Chris Nauroth 
 
 wrote:
 
> Yes, that's basically my assessment too.  Copy-pasting my earlier 
> comment from ZOOKEEPER-1371:
> 
> "After this patch, ZooKeeper no longer produces any logging, 
> because there is no SLF4J binding jar available on the runtime 
> classpath."
> 
> 
> There is no compatibility problem with switching to SLF4J 
> exclusively as our API of choice for logging instead of calling 
> the Log4J API.  The incompatible part is that the distro isn't 
> shipping with any SLF4J binding included.  Perhaps we can do a 
> partial revert of just that part of ZOOKEEPER-1371.
> 
> --Chris Nauroth
> 
> 
> 
> 
> On 3/15/16, 11:54 AM, "Patrick Hunt"  wrote:
> 
>> Hm, I started looking at the original patch in more depth:
>> 
> 
> 
>>> https://issues.apache.org/jira/secure/attachment/12773684/ZOOKEEPER-
>>> 1371-
> 0
>> 5.patch
>> 
>> is the real root issue 2342 is trying to address the following 
>> line
>> change:
>> 
>> -> transitive="false"/>
>> +> transitive="false" conf="test->default"/>
>> 
>> Specifically that we changed from runtime to test only for this 
>> dependency? Perhaps we just need to revert that? I see some other 
>> magic happening in the build.xml file that I don't quite 
>> understand - adding a new target and NoLog4j... references.
>> 
>> Raul perhaps you can give more insight since it seems like you 
>> worked on 1371 most recently?
>> 
>> Patrick
>> 
>> 
>> On Tue, Mar 15, 2016 at 11:41 AM, Chris Nauroth 
>>  wrote:
>>> I agree.  Even if we don't fully understand every minute 
>>> technical detail of Log4J 2 vs. Log4J 1, I think we've learned 
>>> enough from my work-in-progress patch to declare that a 
>>> migration is too risky for
> the
>>> 3.5 line.  Reverting ZOOKEEPER-1371 (the earlier
> backwards-incompatible
>>> logging change) is the better choice for the interest of 
>>> proceeding
> with
>>> 3.5 releases.
>>> 
>>> --Chris Nauroth
>>> 
>>> 
>>> 
>>> 
>>> On 3/15/16, 11:23 AM, "Patrick Hunt"  wrote:
>>> 
 I just commented on ZOOKEEPER-2342... not sure I fully 
 understand all the issues to be honest. Given how much we're 

ZooKeeper_branch34_jdk8 - Build # 508 - Failure

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch34_jdk8/508/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 218715 lines...]
[junit] 2016-03-17 07:21:26,127 [myid:] - INFO  [main:JMXEnv@246] - 
expect:StandaloneServer_port
[junit] 2016-03-17 07:21:26,127 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2016-03-17 07:21:26,127 [myid:] - INFO  [main:ClientBase@490] - 
STOPPING server
[junit] 2016-03-17 07:21:26,127 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2016-03-17 07:21:26,128 [myid:] - INFO  [main:ZooKeeperServer@469] 
- shutting down
[junit] 2016-03-17 07:21:26,128 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2016-03-17 07:21:26,128 [myid:] - INFO  
[main:PrepRequestProcessor@767] - Shutting down
[junit] 2016-03-17 07:21:26,128 [myid:] - INFO  
[main:SyncRequestProcessor@209] - Shutting down
[junit] 2016-03-17 07:21:26,129 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2016-03-17 07:21:26,129 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@187] - SyncRequestProcessor exited!
[junit] 2016-03-17 07:21:26,129 [myid:] - INFO  
[main:FinalRequestProcessor@415] - shutdown of request processor complete
[junit] 2016-03-17 07:21:26,130 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-03-17 07:21:26,131 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-03-17 07:21:26,132 [myid:] - INFO  [main:ClientBase@443] - 
STARTING server
[junit] 2016-03-17 07:21:26,133 [myid:] - INFO  [main:ClientBase@364] - 
CREATING server instance 127.0.0.1:11221
[junit] 2016-03-17 07:21:26,133 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2016-03-17 07:21:26,133 [myid:] - INFO  [main:ClientBase@339] - 
STARTING server instance 127.0.0.1:11221
[junit] 2016-03-17 07:21:26,134 [myid:] - INFO  [main:ZooKeeperServer@170] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/jenkins/workspace/ZooKeeper_branch34_jdk8/branch-3.4/build/test/tmp/test5240672381901208353.junit.dir/version-2
 snapdir 
/jenkins/workspace/ZooKeeper_branch34_jdk8/branch-3.4/build/test/tmp/test5240672381901208353.junit.dir/version-2
[junit] 2016-03-17 07:21:26,140 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-03-17 07:21:26,140 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:48350
[junit] 2016-03-17 07:21:26,141 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing 
stat command from /127.0.0.1:48350
[junit] 2016-03-17 07:21:26,141 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@663] - Stat command output
[junit] 2016-03-17 07:21:26,142 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1008] - Closed socket connection for client 
/127.0.0.1:48350 (no session established for client)
[junit] 2016-03-17 07:21:26,142 [myid:] - INFO  [main:JMXEnv@229] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-03-17 07:21:26,144 [myid:] - INFO  [main:JMXEnv@246] - 
expect:InMemoryDataTree
[junit] 2016-03-17 07:21:26,144 [myid:] - INFO  [main:JMXEnv@250] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2016-03-17 07:21:26,145 [myid:] - INFO  [main:JMXEnv@246] - 
expect:StandaloneServer_port
[junit] 2016-03-17 07:21:26,145 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2016-03-17 07:21:26,145 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 14326
[junit] 2016-03-17 07:21:26,145 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2016-03-17 07:21:26,145 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2016-03-17 07:21:26,146 [myid:] - INFO  [main:ClientBase@520] - 
tearDown starting
[junit] 2016-03-17 07:21:26,186 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x1538373500d closed
[junit] 2016-03-17 07:21:26,186 [myid:] - INFO  [main:ClientBase@490] - 
STOPPING server
[junit] 2016-03-17 07:21:26,186 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x1538373500d
[junit] 2016-03-17 07:21:26,186 [myid:] - INFO  

[jira] [Updated] (ZOOKEEPER-1467) Server principal on client side is derived using hostname.

[Patrick Hunt (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Patrick Hunt updated ZOOKEEPER-1467:

Priority: Critical  (was: Blocker)

> Server principal on client side is derived using hostname.
> --
>
> Key: ZOOKEEPER-1467
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1467
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.4.3, 3.4.4, 3.5.0, 4.0.0
>Reporter: Laxman
>Assignee: Eugene Koontz
>Priority: Critical
>  Labels: Security, client, kerberos, sasl
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-1467.patch, ZOOKEEPER-1467.patch
>
>
> Server principal on client side is derived using hostname.
> org.apache.zookeeper.ClientCnxn.SendThread.startConnect()
> {code}
>try {
> zooKeeperSaslClient = new 
> ZooKeeperSaslClient("zookeeper/"+addr.getHostName());
> }
> {code}
> This may have problems when admin wanted some customized principals like 
> zookeeper/cluste...@hadoop.com where clusterid is the cluster identifier but 
> not the host name.
> IMO, server principal also should be configurable as hadoop is doing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2392) Update netty to 3.7.1.Final

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199404#comment-15199404
 ] 

Hadoop QA commented on ZOOKEEPER-2392:
--

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12793930/ZOOKEEPER-2392.patch
  against trunk revision 1735369.

+1 @author.  The patch does not contain any @author tags.

-1 tests included.  The patch doesn't appear to include any new or modified 
tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

+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 2.0.3) 
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-Build/3104//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3104//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3104//console

This message is automatically generated.

> Update netty to 3.7.1.Final
> ---
>
> Key: ZOOKEEPER-2392
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2392
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 3.4.6, 3.5.1
>Reporter: Hendy Irawan
>Assignee: Hendy Irawan
>Priority: Minor
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2392.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

ZooKeeper_branch34_openjdk7 - Build # 1015 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch34_openjdk7/1015/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 213404 lines...]
[junit] 2016-03-19 15:12:40,478 [myid:] - INFO  [main:JMXEnv@246] - 
expect:StandaloneServer_port
[junit] 2016-03-19 15:12:40,478 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2016-03-19 15:12:40,478 [myid:] - INFO  [main:ClientBase@490] - 
STOPPING server
[junit] 2016-03-19 15:12:40,479 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2016-03-19 15:12:40,479 [myid:] - INFO  [main:ZooKeeperServer@469] 
- shutting down
[junit] 2016-03-19 15:12:40,479 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2016-03-19 15:12:40,479 [myid:] - INFO  
[main:PrepRequestProcessor@767] - Shutting down
[junit] 2016-03-19 15:12:40,480 [myid:] - INFO  
[main:SyncRequestProcessor@209] - Shutting down
[junit] 2016-03-19 15:12:40,480 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2016-03-19 15:12:40,480 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@187] - SyncRequestProcessor exited!
[junit] 2016-03-19 15:12:40,481 [myid:] - INFO  
[main:FinalRequestProcessor@415] - shutdown of request processor complete
[junit] 2016-03-19 15:12:40,481 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-03-19 15:12:40,482 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-03-19 15:12:40,484 [myid:] - INFO  [main:ClientBase@443] - 
STARTING server
[junit] 2016-03-19 15:12:40,484 [myid:] - INFO  [main:ClientBase@364] - 
CREATING server instance 127.0.0.1:11221
[junit] 2016-03-19 15:12:40,484 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2016-03-19 15:12:40,485 [myid:] - INFO  [main:ClientBase@339] - 
STARTING server instance 127.0.0.1:11221
[junit] 2016-03-19 15:12:40,485 [myid:] - INFO  [main:ZooKeeperServer@170] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_openjdk7/branch-3.4/build/test/tmp/test6029786548793961294.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_openjdk7/branch-3.4/build/test/tmp/test6029786548793961294.junit.dir/version-2
[junit] 2016-03-19 15:12:40,490 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-03-19 15:12:40,491 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:41020
[junit] 2016-03-19 15:12:40,491 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing 
stat command from /127.0.0.1:41020
[junit] 2016-03-19 15:12:40,491 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@663] - Stat command output
[junit] 2016-03-19 15:12:40,492 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1008] - Closed socket connection for client 
/127.0.0.1:41020 (no session established for client)
[junit] 2016-03-19 15:12:40,492 [myid:] - INFO  [main:JMXEnv@229] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-03-19 15:12:40,494 [myid:] - INFO  [main:JMXEnv@246] - 
expect:InMemoryDataTree
[junit] 2016-03-19 15:12:40,494 [myid:] - INFO  [main:JMXEnv@250] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2016-03-19 15:12:40,495 [myid:] - INFO  [main:JMXEnv@246] - 
expect:StandaloneServer_port
[junit] 2016-03-19 15:12:40,495 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2016-03-19 15:12:40,495 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 32644
[junit] 2016-03-19 15:12:40,495 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2016-03-19 15:12:40,495 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2016-03-19 15:12:40,496 [myid:] - INFO  [main:ClientBase@520] - 
tearDown starting
[junit] 2016-03-19 15:12:40,561 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x1538f6f770a closed
[junit] 2016-03-19 15:12:40,561 [myid:] - INFO  [main:ClientBase@490] - 
STOPPING server
[junit] 2016-03-19 15:12:40,561 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x1538f6f770a
[junit] 2016-03-19 15:12:40,561 [myid:] - INFO 

[jira] [Updated] (ZOOKEEPER-2388) Unit tests failing on Solaris

[Arshad Mohammad (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arshad Mohammad updated ZOOKEEPER-2388:
---
Attachment: ZOOKEEPER-2388-01.patch

> Unit tests failing on Solaris
> -
>
> Key: ZOOKEEPER-2388
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2388
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 3.5.2
>Reporter: Patrick Hunt
>Assignee: Arshad Mohammad
>Priority: Blocker
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2388-01.patch
>
>
> The same two tests are failing consistently on Solaris in 3.5/trunk (I don't 
> see similar failures in 3.4, jenkins is mostly green there)
> org.apache.zookeeper.server.quorum.LocalPeerBeanTest.testClientAddress
> org.apache.zookeeper.server.quorum.QuorumPeerTest.testQuorumPeerListendOnSpecifiedClientIP



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

ZooKeeper_branch35_solaris - Build # 27 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch35_solaris/27/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 346863 lines...]
[junit] 2016-03-17 08:55:47,746 [myid:] - INFO  [main:ClientBase@460] - 
STARTING server
[junit] 2016-03-17 08:55:47,747 [myid:] - INFO  [main:ClientBase@380] - 
CREATING server instance 127.0.0.1:11222
[junit] 2016-03-17 08:55:47,747 [myid:] - INFO  
[main:NIOServerCnxnFactory@673] - Configuring NIO connection handler with 10s 
sessionless connection timeout, 2 selector thread(s), 16 worker threads, and 64 
kB direct buffers.
[junit] 2016-03-17 08:55:47,748 [myid:] - INFO  
[main:NIOServerCnxnFactory@686] - binding to port 0.0.0.0/0.0.0.0:11222
[junit] 2016-03-17 08:55:47,748 [myid:] - INFO  [main:ClientBase@355] - 
STARTING server instance 127.0.0.1:11222
[junit] 2016-03-17 08:55:47,748 [myid:] - INFO  [main:ZooKeeperServer@858] 
- minSessionTimeout set to 6000
[junit] 2016-03-17 08:55:47,749 [myid:] - INFO  [main:ZooKeeperServer@867] 
- maxSessionTimeout set to 6
[junit] 2016-03-17 08:55:47,749 [myid:] - INFO  [main:ZooKeeperServer@156] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/branch-3.5/build/test/tmp/test3666144331811057362.junit.dir/version-2
 snapdir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/branch-3.5/build/test/tmp/test3666144331811057362.junit.dir/version-2
[junit] 2016-03-17 08:55:47,749 [myid:] - INFO  [main:FileSnap@83] - 
Reading snapshot 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/branch-3.5/build/test/tmp/test3666144331811057362.junit.dir/version-2/snapshot.b
[junit] 2016-03-17 08:55:47,751 [myid:] - INFO  [main:FileTxnSnapLog@298] - 
Snapshotting: 0xb to 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/branch-3.5/build/test/tmp/test3666144331811057362.junit.dir/version-2/snapshot.b
[junit] 2016-03-17 08:55:47,753 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222
[junit] 2016-03-17 08:55:47,753 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@296]
 - Accepted socket connection from /127.0.0.1:63009
[junit] 2016-03-17 08:55:47,754 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@485] - Processing stat command from 
/127.0.0.1:63009
[junit] 2016-03-17 08:55:47,754 [myid:] - INFO  
[NIOWorkerThread-1:StatCommand@49] - Stat command output
[junit] 2016-03-17 08:55:47,755 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@607] - Closed socket connection for client 
/127.0.0.1:63009 (no session established for client)
[junit] 2016-03-17 08:55:47,755 [myid:] - INFO  [main:JMXEnv@228] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-03-17 08:55:47,756 [myid:] - INFO  [main:JMXEnv@245] - 
expect:InMemoryDataTree
[junit] 2016-03-17 08:55:47,756 [myid:] - INFO  [main:JMXEnv@249] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree
[junit] 2016-03-17 08:55:47,756 [myid:] - INFO  [main:JMXEnv@245] - 
expect:StandaloneServer_port
[junit] 2016-03-17 08:55:47,757 [myid:] - INFO  [main:JMXEnv@249] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222
[junit] 2016-03-17 08:55:47,757 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 17762
[junit] 2016-03-17 08:55:47,757 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 24
[junit] 2016-03-17 08:55:47,757 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testQuota
[junit] 2016-03-17 08:55:47,757 [myid:] - INFO  [main:ClientBase@537] - 
tearDown starting
[junit] 2016-03-17 08:55:47,832 [myid:] - INFO  [main:ZooKeeper@1110] - 
Session: 0x12000c80252 closed
[junit] 2016-03-17 08:55:47,832 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@543] - EventThread shut down for 
session: 0x12000c80252
[junit] 2016-03-17 08:55:47,832 [myid:] - INFO  [main:ClientBase@507] - 
STOPPING server
[junit] 2016-03-17 08:55:47,833 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2016-03-17 08:55:47,833 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2016-03-17 08:55:47,833 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@219]
 - accept thread exitted run method

ZooKeeper-trunk - Build # 2852 - Failure

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper-trunk/2852/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 378978 lines...]
 [exec] Log Message Received: [2016-03-17 
01:40:10,404:1045(0x2abba8ad0540):ZOO_INFO@log_env@1048: Client 
environment:user.name=jenkins]
 [exec] Log Message Received: [2016-03-17 
01:40:10,404:1045(0x2abba8ad0540):ZOO_INFO@log_env@1056: Client 
environment:user.home=/home/jenkins]
 [exec] Log Message Received: [2016-03-17 
01:40:10,404:1045(0x2abba8ad0540):ZOO_INFO@log_env@1068: Client 
environment:user.dir=/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/test/test-cppunit]
 [exec] Log Message Received: [2016-03-17 
01:40:10,404:1045(0x2abba8ad0540):ZOO_INFO@zookeeper_init_internal@: 
Initiating client connection, host=127.0.0.1:22181 sessionTimeout=1 
watcher=0x45d2a0 sessionId=0 sessionPasswd= context=0x7fff2209f730 
flags=0]
 [exec] Log Message Received: [2016-03-17 
01:40:10,405:1045(0x2abbab15f700):ZOO_INFO@check_events@2357: initiated 
connection to server [127.0.0.1:22181]]
 [exec] Log Message Received: [2016-03-17 
01:40:10,408:1045(0x2abbab15f700):ZOO_INFO@check_events@2409: session 
establishment complete on server [127.0.0.1:22181], 
sessionId=0x1018ba97eb10010, negotiated timeout=1 ]
 [exec]  : elapsed 1001 : OK
 [exec] Zookeeper_simpleSystem::testAsyncWatcherAutoReset ZooKeeper server 
started : elapsed 10118 : OK
 [exec] Zookeeper_simpleSystem::testDeserializeString : elapsed 0 : OK
 [exec] Zookeeper_simpleSystem::testFirstServerDown : elapsed 1000 : OK
 [exec] Zookeeper_simpleSystem::testNullData : elapsed 1022 : OK
 [exec] Zookeeper_simpleSystem::testIPV6 : elapsed 1003 : OK
 [exec] Zookeeper_simpleSystem::testCreate : elapsed 1007 : OK
 [exec] Zookeeper_simpleSystem::testPath : elapsed 1013 : OK
 [exec] Zookeeper_simpleSystem::testPathValidation : elapsed 1039 : OK
 [exec] Zookeeper_simpleSystem::testPing : elapsed 17174 : OK
 [exec] Zookeeper_simpleSystem::testAcl : elapsed 1012 : OK
 [exec] Zookeeper_simpleSystem::testChroot : elapsed 3030 : OK
 [exec] Zookeeper_simpleSystem::testAuth ZooKeeper server started ZooKeeper 
server started : elapsed 30137 : OK
 [exec] Zookeeper_simpleSystem::testHangingClient : elapsed 1021 : OK
 [exec] Zookeeper_simpleSystem::testWatcherAutoResetWithGlobal ZooKeeper 
server started ZooKeeper server started ZooKeeper server started : elapsed 
14292 : OK
 [exec] Zookeeper_simpleSystem::testWatcherAutoResetWithLocal ZooKeeper 
server started ZooKeeper server started ZooKeeper server started : elapsed 
14316 : OK
 [exec] Zookeeper_simpleSystem::testGetChildren2 : elapsed 1038 : OK
 [exec] Zookeeper_simpleSystem::testLastZxid : elapsed 4511 : OK
 [exec] Zookeeper_simpleSystem::testRemoveWatchers ZooKeeper server started 
: elapsed 4201 : OK
 [exec] Zookeeper_readOnly::testReadOnly : elapsed 4170 : OK
 [exec] 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/src/c/tests/TestReconfig.cc:183:
 Assertion: equality assertion failed [Expected: 1, Actual  : 0]
 [exec] Failures !!!
 [exec] Run: 72   Failure total: 1   Failures: 1   Errors: 0
 [exec] FAIL: zktest-mt
 [exec] ==
 [exec] 1 of 2 tests failed
 [exec] Please report to u...@zookeeper.apache.org
 [exec] ==
 [exec] make[1]: Leaving directory 
`/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/test/test-cppunit'
 [exec] make[1]: *** [check-TESTS] Error 1
 [exec] make: *** [check-am] Error 2

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build.xml:1361: The 
following error occurred while executing this line:
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build.xml:1321: The 
following error occurred while executing this line:
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build.xml:1331: 
exec returned: 2

Total time: 11 minutes 21 seconds
Build step 'Execute shell' marked build as failure
[FINDBUGS] Skipping publisher since build result is FAILURE
[WARNINGS] Skipping publisher since build result is FAILURE
Archiving artifacts
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Recording fingerprints
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Recording test results
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Publishing Javadoc
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 

[jira] [Commented] (ZOOKEEPER-2195) fsync.warningthresholdms in zoo.cfg not working

[Biju Nair (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15198314#comment-15198314
 ] 

Biju Nair commented on ZOOKEEPER-2195:
--

[~dryabkov] [~phunt] attached a new patch. Please review.

> fsync.warningthresholdms in zoo.cfg not working
> ---
>
> Key: ZOOKEEPER-2195
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2195
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: quorum
>Affects Versions: 3.4.6, 3.5.0
>Reporter: David Fan
>Assignee: Biju Nair
>Priority: Trivial
> Fix For: 3.4.9, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2195-1.patch, ZOOKEEPER-2195-DOC.patch, 
> ZOOKEEPER-2195.patch
>
>
> Config fsync.warningthresholdms in zoo.cfg does not work.
> I find QuorumPeerConfig.parseProperties give fsync.warningthresholdms a 
> prefix like "zookeeper.fsync.warningthresholdms".  But in class FileTxnLog 
> where fsync.warningthresholdms is used, code is 
> :Long.getLong("fsync.warningthresholdms", 1000),without prefix "zookeeper.", 
> therefore can not get fsync.warningthresholdms's value.
> I wonder the speed of fsync, need this config to see whether the speed is 
> good enough.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2391) setMin/MaxSessionTimeout of ZookeeperServer are implemented in quite a weak way

[Flavio Junqueira (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flavio Junqueira updated ZOOKEEPER-2391:

Assignee: Kazuaki Banzai

> setMin/MaxSessionTimeout of ZookeeperServer are implemented in quite a weak 
> way
> ---
>
> Key: ZOOKEEPER-2391
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2391
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: documentation, server
>Reporter: Kazuaki Banzai
>Assignee: Kazuaki Banzai
>Priority: Minor
> Attachments: ZOOKEEPER-2391.patch
>
>
> setMin/MaxSessionTimeout of ZookeeperServer are implemented in quite a weak 
> way.
> * -1 restores the default, but this is not documented.
> * values < -1 are permitted but make no sense.
> * min > max is permitted but makes not sense.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2392) Update netty to 3.7.1.Final

[Patrick Hunt (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15198837#comment-15198837
 ] 

Patrick Hunt commented on ZOOKEEPER-2392:
-

Hi [~ceefour] - we don't accept patches via pull request. Please submit using 
our process as defined here:
https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToContribute
(basically by attaching a patch file and hitting the "submit" button above)
Thanks!

> Update netty to 3.7.1.Final
> ---
>
> Key: ZOOKEEPER-2392
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2392
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 3.4.6, 3.5.1
>Reporter: Hendy Irawan
>Assignee: Hendy Irawan
>Priority: Minor
> Fix For: 3.5.2, 3.6.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2014) Only admin should be allowed to reconfig a cluster

[Patrick Hunt (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15198842#comment-15198842
 ] 

Patrick Hunt commented on ZOOKEEPER-2014:
-

We can't (or at least promise we won't) change the api in a non b/w compatible 
way once it's post-alpha. As such I believe at a minimum we need to clean up 
the API (should be simple - move it out of ZooKeeper class) and ensure there 
are no security issues.

> Only admin should be allowed to reconfig a cluster
> --
>
> Key: ZOOKEEPER-2014
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2014
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.5.0
>Reporter: Raul Gutierrez Segales
>Assignee: Raul Gutierrez Segales
>Priority: Blocker
> Fix For: 3.5.2
>
> Attachments: ZOOKEEPER-2014.patch
>
>
> ZOOKEEPER-107 introduces reconfiguration support via the reconfig() call. We 
> should, at the very least, ensure that only the Admin can reconfigure a 
> cluster. Perhaps restricting access to /zookeeper/config as well, though this 
> is debatable. Surely one could ensure Admin only access via an ACL, but that 
> would leave everyone who doesn't use ACLs unprotected. We could also force a 
> default ACL to make it a bit more consistent (maybe).
> Finally, making reconfig() only available to Admins means they have to run 
> with zookeeper.DigestAuthenticationProvider.superDigest (which I am not sure 
> if everyone does, or how would it work with other authentication providers). 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Failed: ZOOKEEPER-2141 PreCommit Build #3105

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2141
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3105/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 380049 lines...]
 [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 2.0.3) 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-Build/3105//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3105//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3105//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] b0cf4f3e9aba30e1189899e56283d9e4e8161564 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1646:
 exec returned: 1

Total time: 10 minutes 52 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Recording test results
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
[description-setter] Description set: ZOOKEEPER-2141
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7



###
## FAILED TESTS (if any) 
##
All tests passed

[jira] [Commented] (ZOOKEEPER-2383) Startup race in ZooKeeperServer

[Jason Rosenberg (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15198781#comment-15198781
 ] 

Jason Rosenberg commented on ZOOKEEPER-2383:


I've run into similar issues, with the register call causing an AssertionError, 
which is not caught anywhere, which results in test failures (especially if you 
have multiple QuorumPeers running in the same jvm during tests).  JMX 
registration gets confused if you have individual nodes starting and stopping.  
 (Asserts are only enabled for us during testing/ci, so it doesn't affect 
production).
I worked around it be calling {code}MBeanRegistry.setInstance(new 
FakeMBeanRegistry()){code}.  Where {code}FakeMBeanRegistry{code} looks like:

{code}
  public static class FakeMBeanRegistry extends MBeanRegistry {
@Override public void register(ZKMBeanInfo bean, ZKMBeanInfo parent) throws 
JMException {}
@Override public void unregister(ZKMBeanInfo bean) {}
@Override public void unregisterAll() {}
  }
{code}

Maybe there should be a flag to disable all JMX registrations (e.g. for most 
tests), and it could be handled with something like this fake class.

> Startup race in ZooKeeperServer
> ---
>
> Key: ZOOKEEPER-2383
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2383
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: jmx, server
>Affects Versions: 3.4.8
>Reporter: Steve Rowe
>Priority: Blocker
> Fix For: 3.4.9
>
> Attachments: TestZkStandaloneJMXRegistrationRaceConcurrent.java, 
> release-3.4.8-extra-logging.patch, zk-3.4.8-MBeanRegistry.log, 
> zk-3.4.8-NPE.log
>
>
> In attempting to upgrade Solr's ZooKeeper dependency from 3.4.6 to 3.4.8 
> (SOLR-8724) I ran into test failures where attempts to create a node in a 
> newly started standalone ZooKeeperServer were failing because of an assertion 
> in MBeanRegistry.
> ZooKeeperServer.startup() first sets up its request processor chain then 
> registers itself in JMX, but if a connection comes in before the server's JMX 
> registration happens, registration of the connection will fail because it 
> trips the assertion that (effectively) its parent (the server) has already 
> registered itself.
> {code:java|title=ZooKeeperServer.java}
> public synchronized void startup() {
> if (sessionTracker == null) {
> createSessionTracker();
> }
> startSessionTracker();
> setupRequestProcessors();
> registerJMX();
> state = State.RUNNING;
> notifyAll();
> }
> {code}
> {code:java|title=MBeanRegistry.java}
> public void register(ZKMBeanInfo bean, ZKMBeanInfo parent)
> throws JMException
> {
> assert bean != null;
> String path = null;
> if (parent != null) {
> path = mapBean2Path.get(parent);
> assert path != null;
> }
> {code}
> This problem appears to be new with ZK 3.4.8 - AFAIK Solr never had this 
> issue with ZK 3.4.6. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

ZooKeeper-trunk-jdk8 - Build # 531 - Failure

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper-trunk-jdk8/531/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 1467 lines...]
[ivy:retrieve]  found org.mortbay.jetty#jetty-util;6.1.26 in maven2
[ivy:retrieve]  found org.mortbay.jetty#servlet-api;2.5-20081211 in maven2
[ivy:retrieve]  found org.codehaus.jackson#jackson-mapper-asl;1.9.11 in maven2
[ivy:retrieve]  found org.codehaus.jackson#jackson-core-asl;1.9.11 in maven2
[ivy:retrieve]  found org.slf4j#slf4j-api;1.7.5 in maven2
[ivy:retrieve]  found commons-cli#commons-cli;1.2 in maven2
[ivy:retrieve]  found io.netty#netty;3.7.1.Final in maven2
[ivy:retrieve]  found net.java.dev.javacc#javacc;5.0 in maven2
[ivy:retrieve] downloading 
http://repo1.maven.org/maven2/io/netty/netty/3.7.1.Final/netty-3.7.1.Final.jar 
...
[ivy:retrieve] .. 
(1181kB)
[ivy:retrieve] .. (0kB)
[ivy:retrieve]  [SUCCESSFUL ] io.netty#netty;3.7.1.Final!netty.jar (360ms)
[ivy:retrieve] :: resolution report :: resolve 1323ms :: artifacts dl 378ms
-
|  |modules||   artifacts   |
|   conf   | number| search|dwnlded|evicted|| number|dwnlded|
-
|  default |   10  |   1   |   1   |   0   ||   10  |   1   |
-
[ivy:retrieve] :: retrieving :: org.apache.zookeeper#zookeeper
[ivy:retrieve]  confs: [default]
[ivy:retrieve]  10 artifacts copied, 0 already retrieved (3562kB/68ms)

clover.setup:

clover.info:

clover:

generate_jute_parser:
[mkdir] Created dir: 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/build/jute_compiler/org/apache/jute/compiler/generated
[ivy:artifactproperty] DEPRECATED: 'ivy.conf.file' is deprecated, use 
'ivy.settings.file' instead
[ivy:artifactproperty] :: loading settings :: file = 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/ivysettings.xml
 [move] Moving 1 file to 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/build/lib
   [javacc] Java Compiler Compiler Version 5.0 (Parser Generator)
   [javacc] (type "javacc" with no arguments for help)
   [javacc] Reading from file 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/src/java/main/org/apache/jute/compiler/generated/rcc.jj
 . . .
   [javacc] File "TokenMgrError.java" does not exist.  Will create one.
   [javacc] File "ParseException.java" does not exist.  Will create one.
   [javacc] File "Token.java" does not exist.  Will create one.
   [javacc] File "SimpleCharStream.java" does not exist.  Will create one.
   [javacc] Parser generated successfully.

jute:
[javac] Compiling 39 source files to 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/build/classes
[javac] javac: invalid target release: 1.8
[javac] Usage: javac  
[javac] use -help for a list of possible options

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/build.xml:280: 
Compile failed; see the compiler error output for details.

Total time: 4 seconds
Build step 'Invoke Ant' marked build as failure
[WARNINGS] Skipping publisher since build result is 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.

ZooKeeper_branch35_solaris - Build # 31 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch35_solaris/31/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 347061 lines...]
[junit] 2016-03-18 18:11:52,514 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-03-18 18:11:52,515 [myid:] - INFO  [main:ClientBase@460] - 
STARTING server
[junit] 2016-03-18 18:11:52,515 [myid:] - INFO  [main:ClientBase@380] - 
CREATING server instance 127.0.0.1:11222
[junit] 2016-03-18 18:11:52,515 [myid:] - INFO  
[main:NIOServerCnxnFactory@673] - Configuring NIO connection handler with 10s 
sessionless connection timeout, 2 selector thread(s), 16 worker threads, and 64 
kB direct buffers.
[junit] 2016-03-18 18:11:52,516 [myid:] - INFO  
[main:NIOServerCnxnFactory@686] - binding to port 0.0.0.0/0.0.0.0:11222
[junit] 2016-03-18 18:11:52,517 [myid:] - INFO  [main:ClientBase@355] - 
STARTING server instance 127.0.0.1:11222
[junit] 2016-03-18 18:11:52,517 [myid:] - INFO  [main:ZooKeeperServer@858] 
- minSessionTimeout set to 6000
[junit] 2016-03-18 18:11:52,517 [myid:] - INFO  [main:ZooKeeperServer@867] 
- maxSessionTimeout set to 6
[junit] 2016-03-18 18:11:52,517 [myid:] - INFO  [main:ZooKeeperServer@156] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/branch-3.5/build/test/tmp/test6548658896370746051.junit.dir/version-2
 snapdir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/branch-3.5/build/test/tmp/test6548658896370746051.junit.dir/version-2
[junit] 2016-03-18 18:11:52,518 [myid:] - INFO  [main:FileSnap@83] - 
Reading snapshot 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/branch-3.5/build/test/tmp/test6548658896370746051.junit.dir/version-2/snapshot.b
[junit] 2016-03-18 18:11:52,520 [myid:] - INFO  [main:FileTxnSnapLog@298] - 
Snapshotting: 0xb to 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/branch-3.5/build/test/tmp/test6548658896370746051.junit.dir/version-2/snapshot.b
[junit] 2016-03-18 18:11:52,521 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222
[junit] 2016-03-18 18:11:52,522 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@296]
 - Accepted socket connection from /127.0.0.1:37329
[junit] 2016-03-18 18:11:52,523 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@485] - Processing stat command from 
/127.0.0.1:37329
[junit] 2016-03-18 18:11:52,523 [myid:] - INFO  
[NIOWorkerThread-1:StatCommand@49] - Stat command output
[junit] 2016-03-18 18:11:52,523 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@607] - Closed socket connection for client 
/127.0.0.1:37329 (no session established for client)
[junit] 2016-03-18 18:11:52,531 [myid:] - INFO  [main:JMXEnv@228] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-03-18 18:11:52,532 [myid:] - INFO  [main:JMXEnv@245] - 
expect:InMemoryDataTree
[junit] 2016-03-18 18:11:52,532 [myid:] - INFO  [main:JMXEnv@249] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree
[junit] 2016-03-18 18:11:52,532 [myid:] - INFO  [main:JMXEnv@245] - 
expect:StandaloneServer_port
[junit] 2016-03-18 18:11:52,532 [myid:] - INFO  [main:JMXEnv@249] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222
[junit] 2016-03-18 18:11:52,533 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 17771
[junit] 2016-03-18 18:11:52,533 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 24
[junit] 2016-03-18 18:11:52,533 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testQuota
[junit] 2016-03-18 18:11:52,533 [myid:] - INFO  [main:ClientBase@537] - 
tearDown starting
[junit] 2016-03-18 18:11:52,602 [myid:] - INFO  [main:ZooKeeper@1110] - 
Session: 0x12007eb71c7 closed
[junit] 2016-03-18 18:11:52,602 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@543] - EventThread shut down for 
session: 0x12007eb71c7
[junit] 2016-03-18 18:11:52,602 [myid:] - INFO  [main:ClientBase@507] - 
STOPPING server
[junit] 2016-03-18 18:11:52,603 [myid:] - INFO  
[ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - 
ConnnectionExpirerThread interrupted
[junit] 2016-03-18 18:11:52,603 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2016-03-18 18:11:52,603 [myid:] - INFO  

ZooKeeper-trunk-openjdk7 - Build # 956 - Failure

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/956/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 392576 lines...]
[junit] 2016-03-17 22:01:06,433 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port11222]
[junit] 2016-03-17 22:01:06,433 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222
[junit] 2016-03-17 22:01:06,434 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-03-17 22:01:06,435 [myid:] - INFO  [main:ClientBase@460] - 
STARTING server
[junit] 2016-03-17 22:01:06,435 [myid:] - INFO  [main:ClientBase@380] - 
CREATING server instance 127.0.0.1:11222
[junit] 2016-03-17 22:01:06,436 [myid:] - INFO  
[main:NIOServerCnxnFactory@673] - Configuring NIO connection handler with 10s 
sessionless connection timeout, 2 selector thread(s), 32 worker threads, and 64 
kB direct buffers.
[junit] 2016-03-17 22:01:06,436 [myid:] - INFO  
[main:NIOServerCnxnFactory@686] - binding to port 0.0.0.0/0.0.0.0:11222
[junit] 2016-03-17 22:01:06,437 [myid:] - INFO  [main:ClientBase@355] - 
STARTING server instance 127.0.0.1:11222
[junit] 2016-03-17 22:01:06,437 [myid:] - INFO  [main:ZooKeeperServer@858] 
- minSessionTimeout set to 6000
[junit] 2016-03-17 22:01:06,438 [myid:] - INFO  [main:ZooKeeperServer@867] 
- maxSessionTimeout set to 6
[junit] 2016-03-17 22:01:06,438 [myid:] - INFO  [main:ZooKeeperServer@156] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/build/test/tmp/test8408528878128575875.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/build/test/tmp/test8408528878128575875.junit.dir/version-2
[junit] 2016-03-17 22:01:06,440 [myid:] - INFO  [main:FileSnap@83] - 
Reading snapshot 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/build/test/tmp/test8408528878128575875.junit.dir/version-2/snapshot.b
[junit] 2016-03-17 22:01:06,443 [myid:] - INFO  [main:FileTxnSnapLog@298] - 
Snapshotting: 0xb to 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/build/test/tmp/test8408528878128575875.junit.dir/version-2/snapshot.b
[junit] 2016-03-17 22:01:06,446 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222
[junit] 2016-03-17 22:01:06,447 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@296]
 - Accepted socket connection from /127.0.0.1:56242
[junit] 2016-03-17 22:01:06,449 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@485] - Processing stat command from 
/127.0.0.1:56242
[junit] 2016-03-17 22:01:06,450 [myid:] - INFO  
[NIOWorkerThread-1:StatCommand@49] - Stat command output
[junit] 2016-03-17 22:01:06,450 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@607] - Closed socket connection for client 
/127.0.0.1:56242 (no session established for client)
[junit] 2016-03-17 22:01:06,450 [myid:] - INFO  [main:JMXEnv@228] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-03-17 22:01:06,452 [myid:] - INFO  [main:JMXEnv@245] - 
expect:InMemoryDataTree
[junit] 2016-03-17 22:01:06,453 [myid:] - INFO  [main:JMXEnv@249] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree
[junit] 2016-03-17 22:01:06,454 [myid:] - INFO  [main:JMXEnv@245] - 
expect:StandaloneServer_port
[junit] 2016-03-17 22:01:06,454 [myid:] - INFO  [main:JMXEnv@249] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222
[junit] 2016-03-17 22:01:06,455 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 85838
[junit] 2016-03-17 22:01:06,455 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 24
[junit] 2016-03-17 22:01:06,455 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testQuota
[junit] 2016-03-17 22:01:06,455 [myid:] - INFO  [main:ClientBase@537] - 
tearDown starting
[junit] 2016-03-17 22:01:06,498 [myid:] - INFO  [main:ZooKeeper@1110] - 
Session: 0x1019006d2b6 closed
[junit] 2016-03-17 22:01:06,498 [myid:] - INFO  [main:ClientBase@507] - 
STOPPING server
[junit] 2016-03-17 22:01:06,498 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@543] - EventThread shut down for 
session: 0x1019006d2b6
[junit] 2016-03-17 22:01:06,499 [myid:] - INFO  
[ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - 
ConnnectionExpirerThread interrupted
[junit] 2016-03-17 22:01:06,499 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] 

[jira] [Commented] (ZOOKEEPER-2290) Add read/write qps metrics in monitor cmd

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15202098#comment-15202098
 ] 

Hadoop QA commented on ZOOKEEPER-2290:
--

+1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12766278/ZOOKEEPER-2290-v5.patch
  against trunk revision 1735646.

+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 2.0.3) 
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-Build/3107//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3107//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3107//console

This message is automatically generated.

> Add read/write qps metrics in monitor cmd
> -
>
> Key: ZOOKEEPER-2290
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2290
> Project: ZooKeeper
>  Issue Type: Improvement
>Affects Versions: 3.4.6
>Reporter: Liu Shaohui
>Assignee: Liu Shaohui
>Priority: Minor
>  Labels: monitor
> Fix For: 3.6.0
>
> Attachments: ZOOKEEPER-2290-v1.patch, ZOOKEEPER-2290-v2.patch, 
> ZOOKEEPER-2290-v3.patch, ZOOKEEPER-2290-v4.patch, ZOOKEEPER-2290-v5.patch
>
>
> Read/write qps are important metrics to show the pressure of the cluster. We 
> can also use it to alert about some abuse of zookeeper.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ZOOKEEPER-2391) setMin/MaxSessionTimeout of ZookeeperServer are implemented in quite a weak way

[Kazuaki Banzai (JIRA)]

Kazuaki Banzai created ZOOKEEPER-2391:
-

 Summary: setMin/MaxSessionTimeout of ZookeeperServer are 
implemented in quite a weak way
 Key: ZOOKEEPER-2391
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2391
 Project: ZooKeeper
  Issue Type: Bug
  Components: documentation, server
Reporter: Kazuaki Banzai
Priority: Minor


setMin/MaxSessionTimeout of ZookeeperServer are implemented in quite a weak way.
* -1 restores the default, but this is not documented.
* values < -1 are permitted but make no sense.
* min > max is permitted but makes not sense.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ZOOKEEPER-2392) Update netty to 3.7.1.Final

[Hendy Irawan (JIRA)]

Hendy Irawan created ZOOKEEPER-2392:
---

 Summary: Update netty to 3.7.1.Final
 Key: ZOOKEEPER-2392
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2392
 Project: ZooKeeper
  Issue Type: Improvement
  Components: build
Affects Versions: 3.4.6
Reporter: Hendy Irawan
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2014) Only admin should be allowed to reconfig a cluster

[Alexander Shraer (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15198757#comment-15198757
 ] 

Alexander Shraer commented on ZOOKEEPER-2014:
-

[~rgs], does your patch solve the issue ? if not, what is still missing ? If I 
remember correctly my concern was that I'd like getConfig to be available to 
regular clients, not only admin, so they can react to configuration changes.

If this JIRA is what's blocking 3.5 perhaps we could reconsider the approach 
and go with something
simpler to start with, such as relying on ACLs. Or setting default ACLs for the 
config znode and requiring
client admins to have these permissions.

> Only admin should be allowed to reconfig a cluster
> --
>
> Key: ZOOKEEPER-2014
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2014
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.5.0
>Reporter: Raul Gutierrez Segales
>Assignee: Raul Gutierrez Segales
>Priority: Blocker
> Fix For: 3.5.2
>
> Attachments: ZOOKEEPER-2014.patch
>
>
> ZOOKEEPER-107 introduces reconfiguration support via the reconfig() call. We 
> should, at the very least, ensure that only the Admin can reconfigure a 
> cluster. Perhaps restricting access to /zookeeper/config as well, though this 
> is debatable. Surely one could ensure Admin only access via an ACL, but that 
> would leave everyone who doesn't use ACLs unprotected. We could also force a 
> default ACL to make it a bit more consistent (maybe).
> Finally, making reconfig() only available to Admins means they have to run 
> with zookeeper.DigestAuthenticationProvider.superDigest (which I am not sure 
> if everyone does, or how would it work with other authentication providers). 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

ZooKeeper_branch35_solaris - Build # 28 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch35_solaris/28/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 345122 lines...]
[junit] 2016-03-17 15:28:27,369 [myid:] - INFO  [main:ZooKeeperServer@867] 
- maxSessionTimeout set to 6
[junit] 2016-03-17 15:28:27,369 [myid:] - INFO  [main:ZooKeeperServer@156] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/branch-3.5/build/test/tmp/test9080496151591745431.junit.dir/version-2
 snapdir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/branch-3.5/build/test/tmp/test9080496151591745431.junit.dir/version-2
[junit] 2016-03-17 15:28:27,370 [myid:] - INFO  [main:FileSnap@83] - 
Reading snapshot 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/branch-3.5/build/test/tmp/test9080496151591745431.junit.dir/version-2/snapshot.b
[junit] 2016-03-17 15:28:27,372 [myid:] - INFO  [main:FileTxnSnapLog@298] - 
Snapshotting: 0xb to 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/branch-3.5/build/test/tmp/test9080496151591745431.junit.dir/version-2/snapshot.b
[junit] 2016-03-17 15:28:27,373 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222
[junit] 2016-03-17 15:28:27,374 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@296]
 - Accepted socket connection from /127.0.0.1:62819
[junit] 2016-03-17 15:28:27,375 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@485] - Processing stat command from 
/127.0.0.1:62819
[junit] 2016-03-17 15:28:27,375 [myid:] - INFO  
[NIOWorkerThread-1:StatCommand@49] - Stat command output
[junit] 2016-03-17 15:28:27,375 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@607] - Closed socket connection for client 
/127.0.0.1:62819 (no session established for client)
[junit] 2016-03-17 15:28:27,375 [myid:] - INFO  [main:JMXEnv@228] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-03-17 15:28:27,377 [myid:] - INFO  [main:JMXEnv@245] - 
expect:InMemoryDataTree
[junit] 2016-03-17 15:28:27,377 [myid:] - INFO  [main:JMXEnv@249] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree
[junit] 2016-03-17 15:28:27,377 [myid:] - INFO  [main:JMXEnv@245] - 
expect:StandaloneServer_port
[junit] 2016-03-17 15:28:27,377 [myid:] - INFO  [main:JMXEnv@249] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222
[junit] 2016-03-17 15:28:27,377 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 17770
[junit] 2016-03-17 15:28:27,378 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 24
[junit] 2016-03-17 15:28:27,378 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testQuota
[junit] 2016-03-17 15:28:27,378 [myid:] - INFO  [main:ClientBase@537] - 
tearDown starting
[junit] 2016-03-17 15:28:27,452 [myid:] - INFO  [main:ZooKeeper@1110] - 
Session: 0x120022f7fdb closed
[junit] 2016-03-17 15:28:27,452 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@543] - EventThread shut down for 
session: 0x120022f7fdb
[junit] 2016-03-17 15:28:27,452 [myid:] - INFO  [main:ClientBase@507] - 
STOPPING server
[junit] 2016-03-17 15:28:27,452 [myid:] - INFO  
[ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - 
ConnnectionExpirerThread interrupted
[junit] 2016-03-17 15:28:27,452 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@219]
 - accept thread exitted run method
[junit] 2016-03-17 15:28:27,452 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2016-03-17 15:28:27,453 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2016-03-17 15:28:27,453 [myid:] - INFO  [main:ZooKeeperServer@498] 
- shutting down
[junit] 2016-03-17 15:28:27,454 [myid:] - INFO  
[main:SessionTrackerImpl@232] - Shutting down
[junit] 2016-03-17 15:28:27,454 [myid:] - INFO  
[main:PrepRequestProcessor@967] - Shutting down
[junit] 2016-03-17 15:28:27,454 [myid:] - INFO  
[main:SyncRequestProcessor@191] - Shutting down
[junit] 2016-03-17 15:28:27,454 [myid:] - INFO  [ProcessThread(sid:0 
cport:11222)::PrepRequestProcessor@154] - PrepRequestProcessor exited loop!
[junit] 2016-03-17 15:28:27,454 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@169] 

ZooKeeper_branch35_openjdk7 - Build # 12 - Failure

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch35_openjdk7/12/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 383374 lines...]
[junit] 2016-03-17 18:35:54,978 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port11222]
[junit] 2016-03-17 18:35:54,978 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222
[junit] 2016-03-17 18:35:54,979 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-03-17 18:35:54,982 [myid:] - INFO  [main:ClientBase@562] - 
fdcount after test is: 54 at start it was 43
[junit] 2016-03-17 18:35:54,982 [myid:] - INFO  [main:ClientBase@564] - 
sleeping for 20 secs
[junit] 2016-03-17 18:35:54,983 [myid:] - INFO  [main:ZKTestCase$1@65] - 
SUCCEEDED testQuota
[junit] 2016-03-17 18:35:54,983 [myid:] - INFO  [main:ZKTestCase$1@60] - 
FINISHED testQuota
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.758 sec

junit.run-concurrent:

junit.run:

test-core-java:

junit.run.nolog4j:

test-core-java-nolog4j:

call-test-cppunit:

init:

check-cppunit-makefile:

create-cppunit-makefile:

init:

check-cppunit-configure:

create-cppunit-configure:
[mkdir] Created dir: 
/x1/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_openjdk7/branch-3.5/build/test/test-cppunit
 [exec] checking for doxygen... no
 [exec] checking for perl... /usr/bin/perl
 [exec] checking for dot... no
 [exec] checking for a BSD-compatible install... /usr/bin/install -c
 [exec] checking whether build environment is sane... 
 [exec] yes
 [exec] checking for a thread-safe mkdir -p... /bin/mkdir -p
 [exec] checking for gawk... no
 [exec] checking for mawk... mawk
 [exec] checking whether make sets $(MAKE)... yes
 [exec] /bin/bash: 
/x1/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_openjdk7/branch-3.5/src/c/missing:
 No such file or directory
 [exec] configure: WARNING: `missing' script is too old or missing
 [exec] 
/x1/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_openjdk7/branch-3.5/src/c/configure:
 line 4907: syntax error near unexpected token `1.10.2'
 [exec] 
/x1/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_openjdk7/branch-3.5/src/c/configure:
 line 4907: `   AM_PATH_CPPUNIT(1.10.2)'

BUILD FAILED
/x1/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_openjdk7/branch-3.5/build.xml:1361:
 The following error occurred while executing this line:
/x1/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_openjdk7/branch-3.5/build.xml:1320:
 The following error occurred while executing this line:
/x1/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_openjdk7/branch-3.5/build.xml:1312:
 exec returned: 2

Total time: 61 minutes 58 seconds
Build step 'Invoke Ant' marked build as failure
Archiving artifacts
Recording test results
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
All tests passed

[jira] [Commented] (ZOOKEEPER-2387) Attempt to gracefully stop the

[Patrick Hunt (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15198855#comment-15198855
 ] 

Patrick Hunt commented on ZOOKEEPER-2387:
-

bq. how does the shutdown hook conceal any exceptions due to corner cases which 
may occur

It's not really about that at all, it's not specifically exceptions that might 
occur during the shutdown hook.

It's more about ZK itself, overall, being robust to unexpected failures. Today 
without graceful shutdown we make every shutdown non-graceful. It's stressing 
the system every time we shut down rather than only stressing the system when 
an unexpected failure happens. This causes code which normally (with graceful 
shutdown) would only be tested in rare situations be tested more frequently. So 
whether it's the log recovery code, or the snapshot recovery code, or the 
communication between servers, we tend to stress these code paths more 
frequently as a result (granted it's not every time, because we might not be 
writing out a wal, etc... during process shutdown but hopefully you see it's 
more likely).

> Attempt to gracefully stop the 
> ---
>
> Key: ZOOKEEPER-2387
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2387
> Project: ZooKeeper
>  Issue Type: Improvement
>Reporter: Biju Nair
>Assignee: Biju Nair
> Attachments: ZOOKEEPER-2387-1.patch
>
>
> To stop ZooKeeper service, {{kill}} is issued against the ZK process. It will 
> be good to gracefully stop all the subcomponents.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2392) Update netty to 3.7.1.Final

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15202151#comment-15202151
 ] 

Hudson commented on ZOOKEEPER-2392:
---

SUCCESS: Integrated in ZooKeeper-trunk #2855 (See 
[https://builds.apache.org/job/ZooKeeper-trunk/2855/])
ZOOKEEPER-2392 Update netty to 3.7.1.Final (Hendy Irawan via phunt) (phunt: 
[http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN=rev=1735646])
* trunk/CHANGES.txt
* trunk/ivy.xml


> Update netty to 3.7.1.Final
> ---
>
> Key: ZOOKEEPER-2392
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2392
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 3.4.6, 3.5.1
>Reporter: Hendy Irawan
>Assignee: Hendy Irawan
>Priority: Minor
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2392.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-1582) EndOfStreamException: Unable to read additional data from client

[Vishal (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199222#comment-15199222
 ] 

Vishal commented on ZOOKEEPER-1582:
---

Same issue with Hbase-1.1.1 & Zk-3.4.6

> EndOfStreamException: Unable to read additional data from client
> 
>
> Key: ZOOKEEPER-1582
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1582
> Project: ZooKeeper
>  Issue Type: Bug
> Environment: windows 7
> jdk 7
>Reporter: zhouyanming
>Priority: Blocker
>
> 1.download zookeeper-3.4.4.tar.gz and unzip
> 2.rename conf/zoo_sample.cfg to zoo.cfg
> 3.click zkServer.cmd
> 4.click zkCli.cmd
> zkCli can not connect to zkServer,it blocked
> zkServer console print
> 2012-11-13 17:28:05,302 [myid:] - WARN  
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of 
> stream exception
> EndOfStreamException: Unable to read additional data from client sessionid 
> 0x13af9131eee, likely client has closed socket
> at 
> org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:220)
> at 
> org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:208)
> at java.lang.Thread.run(Thread.java:722)
> 2012-11-13 17:28:05,308 [myid:] - INFO  
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed 
> socket connection for client /127.0.0.1:54810 which had sessionid 
> 0x13af9131eee 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2392) Update netty to 3.7.1.Final

[Hendy Irawan (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199472#comment-15199472
 ] 

Hendy Irawan commented on ZOOKEEPER-2392:
-

new tests are not needed because this is a minor version update of dependency

> Update netty to 3.7.1.Final
> ---
>
> Key: ZOOKEEPER-2392
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2392
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 3.4.6, 3.5.1
>Reporter: Hendy Irawan
>Assignee: Hendy Irawan
>Priority: Minor
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2392.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] zookeeper pull request: fix zerror return unknown error to ZNOWATC...

[shinya1020]

GitHub user shinya1020 opened a pull request:

https://github.com/apache/zookeeper/pull/58

fix zerror return unknown error to ZNOWATCHER



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/shinya1020/zookeeper fix/zerror

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zookeeper/pull/58.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 #58


commit c0e37cac68f92888fa5d17d8a5479ed51de25852
Author: Shinya Kawano 
Date:   2016-03-17T09:15:31Z

fix zerror return unknown error to ZNOWATCHER




---
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-2297) NPE is thrown while creating "key manager" and "trust manager"

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199238#comment-15199238
 ] 

Hadoop QA commented on ZOOKEEPER-2297:
--

-1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12785213/ZOOKEEPER-2355-05.patch
  against trunk revision 1735369.

+1 @author.  The patch does not contain any @author tags.

-1 tests included.  The patch doesn't appear to include any new or modified 
tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

+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 appears to introduce 2 new Findbugs (version 2.0.3) 
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-Build/3103//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3103//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3103//console

This message is automatically generated.

> NPE is thrown while creating "key manager" and "trust manager" 
> ---
>
> Key: ZOOKEEPER-2297
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2297
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.5.1
> Environment: Suse 11 sp 3
>Reporter: Anushri
>Assignee: Arshad Mohammad
>Priority: Blocker
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2297-01.patch, ZOOKEEPER-2297-02.patch, 
> ZOOKEEPER-2297-03.patch, ZOOKEEPER-2297-04.patch, ZOOKEEPER-2355-05.patch
>
>
> NPE is thrown while creating "key manager" and "trust manager" , even though 
> the zk setup is in non-secure mode
> bq. 2015-10-19 12:54:12,278 [myid:2] - ERROR [ProcessThread(sid:2 
> cport:-1)::X509AuthenticationProvider@78] - Failed to create key manager
> bq. org.apache.zookeeper.common.X509Exception$KeyManagerException: 
> java.lang.NullPointerException
> at org.apache.zookeeper.common.X509Util.createKeyManager(X509Util.java:129)
> at 
> org.apache.zookeeper.server.auth.X509AuthenticationProvider.(X509AuthenticationProvider.java:75)
> at 
> org.apache.zookeeper.server.auth.ProviderRegistry.initialize(ProviderRegistry.java:42)
> at 
> org.apache.zookeeper.server.auth.ProviderRegistry.getProvider(ProviderRegistry.java:68)
> at 
> org.apache.zookeeper.server.PrepRequestProcessor.fixupACL(PrepRequestProcessor.java:952)
> at 
> org.apache.zookeeper.server.PrepRequestProcessor.pRequest2Txn(PrepRequestProcessor.java:379)
> at 
> org.apache.zookeeper.server.PrepRequestProcessor.pRequest(PrepRequestProcessor.java:716)
> at 
> org.apache.zookeeper.server.PrepRequestProcessor.run(PrepRequestProcessor.java:144)
> Caused by: java.lang.NullPointerException
> at org.apache.zookeeper.common.X509Util.createKeyManager(X509Util.java:113)
> ... 7 more
> bq. 2015-10-19 12:54:12,279 [myid:2] - ERROR [ProcessThread(sid:2 
> cport:-1)::X509AuthenticationProvider@90] - Failed to create trust manager
> bq.  org.apache.zookeeper.common.X509Exception$TrustManagerException: 
> java.lang.NullPointerException
> at org.apache.zookeeper.common.X509Util.createTrustManager(X509Util.java:158)
> at 
> org.apache.zookeeper.server.auth.X509AuthenticationProvider.(X509AuthenticationProvider.java:87)
> at 
> org.apache.zookeeper.server.auth.ProviderRegistry.initialize(ProviderRegistry.java:42)
> at 
> org.apache.zookeeper.server.auth.ProviderRegistry.getProvider(ProviderRegistry.java:68)
> at 
> org.apache.zookeeper.server.PrepRequestProcessor.fixupACL(PrepRequestProcessor.java:952)
> at 
> org.apache.zookeeper.server.PrepRequestProcessor.pRequest2Txn(PrepRequestProcessor.java:379)
> at 
> org.apache.zookeeper.server.PrepRequestProcessor.pRequest(PrepRequestProcessor.java:716)
> at 
> org.apache.zookeeper.server.PrepRequestProcessor.run(PrepRequestProcessor.java:144)
> Caused by: java.lang.NullPointerException
> at org.apache.zookeeper.common.X509Util.createTrustManager(X509Util.java:143)
> ... 7 more



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2195) fsync.warningthresholdms in zoo.cfg not working

[Biju Nair (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199298#comment-15199298
 ] 

Biju Nair commented on ZOOKEEPER-2195:
--

[~phunt] updated patch attached.

> fsync.warningthresholdms in zoo.cfg not working
> ---
>
> Key: ZOOKEEPER-2195
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2195
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: quorum
>Affects Versions: 3.4.6, 3.5.0
>Reporter: David Fan
>Assignee: Biju Nair
>Priority: Trivial
> Fix For: 3.4.9, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2195-1.patch, ZOOKEEPER-2195-2.patch, 
> ZOOKEEPER-2195-DOC.patch, ZOOKEEPER-2195.patch
>
>
> Config fsync.warningthresholdms in zoo.cfg does not work.
> I find QuorumPeerConfig.parseProperties give fsync.warningthresholdms a 
> prefix like "zookeeper.fsync.warningthresholdms".  But in class FileTxnLog 
> where fsync.warningthresholdms is used, code is 
> :Long.getLong("fsync.warningthresholdms", 1000),without prefix "zookeeper.", 
> therefore can not get fsync.warningthresholdms's value.
> I wonder the speed of fsync, need this config to see whether the speed is 
> good enough.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2342) ZooKeeper cannot write logs, because there is no SLF4J binding available on the runtime classpath.

[Alan Scherger (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15197495#comment-15197495
 ] 

Alan Scherger commented on ZOOKEEPER-2342:
--

[~fournc] so this is somewhat a bummer for me because I was hoping that with us 
adopting a new logger I'd finally have a solution for the old SyslogAppender 
exception-newline problem. for example: 
http://stackoverflow.com/questions/33177076/escape-newlines-in-zookeeper-logs-using-log4j-1-2-syslogappender
 

I understand the backwards compatibility issues, they're valid, and we probably 
should revert this patch -- it just begs the question though, what's the plan 
to rip the bandaid off?

> ZooKeeper cannot write logs, because there is no SLF4J binding available on 
> the runtime classpath.
> --
>
> Key: ZOOKEEPER-2342
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2342
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Chris Nauroth
>Assignee: Chris Nauroth
>Priority: Blocker
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2342.001.patch
>
>
> ZOOKEEPER-1371 removed our source code dependency on Log4J.  It appears that 
> this also removed the Log4J SLF4J binding jar from the runtime classpath.  
> Without any SLF4J binding jar available on the runtime classpath, the it is 
> impossible to write logs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2388) Unit tests failing on Solaris

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199119#comment-15199119
 ] 

Hudson commented on ZOOKEEPER-2388:
---

SUCCESS: Integrated in ZooKeeper-trunk #2853 (See 
[https://builds.apache.org/job/ZooKeeper-trunk/2853/])
ZOOKEEPER-2388 Unit tests failing on Solaris (Arshad Mohammad via phunt) 
(phunt: 
[http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN=rev=1735369])
* trunk/CHANGES.txt
* trunk/src/java/test/org/apache/zookeeper/server/quorum/LocalPeerBeanTest.java
* trunk/src/java/test/org/apache/zookeeper/server/quorum/QuorumPeerTest.java


> Unit tests failing on Solaris
> -
>
> Key: ZOOKEEPER-2388
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2388
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 3.5.2
>Reporter: Patrick Hunt
>Assignee: Arshad Mohammad
>Priority: Blocker
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2388-01.patch
>
>
> The same two tests are failing consistently on Solaris in 3.5/trunk (I don't 
> see similar failures in 3.4, jenkins is mostly green there)
> org.apache.zookeeper.server.quorum.LocalPeerBeanTest.testClientAddress
> org.apache.zookeeper.server.quorum.QuorumPeerTest.testQuorumPeerListendOnSpecifiedClientIP



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2342) Migrate to Log4J 2.

[Chris Nauroth (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15202345#comment-15202345
 ] 

Chris Nauroth commented on ZOOKEEPER-2342:
--

[~flyinprogrammer], sorry to disappoint.  From discussion on the related JIRAs 
and the dev mailing list, we think our best path forward is to remain on Log4J 
1 to unblock the upcoming 3.5.2 release.  Since Log4J 1 is end of life, we do 
need to migrate to Log4J 2 someday ("rip the bandaid off" as you said), but 
we'll have to wait until 3.6.0 to consider that.

> Migrate to Log4J 2.
> ---
>
> Key: ZOOKEEPER-2342
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2342
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Chris Nauroth
>Assignee: Chris Nauroth
> Fix For: 3.6.0
>
> Attachments: ZOOKEEPER-2342.001.patch
>
>
> ZOOKEEPER-1371 removed our source code dependency on Log4J.  It appears that 
> this also removed the Log4J SLF4J binding jar from the runtime classpath.  
> Without any SLF4J binding jar available on the runtime classpath, it is 
> impossible to write logs.
> This JIRA investigated migration to Log4J 2 as a possible path towards 
> resolving the bug introduced by ZOOKEEPER-1371.  At this point, we know this 
> is not feasible short-term.  This JIRA remains open to track long-term 
> migration to Log4J 2.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2195) fsync.warningthresholdms in zoo.cfg not working

[Biju Nair (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Biju Nair updated ZOOKEEPER-2195:
-
Attachment: ZOOKEEPER-2195-1.patch

> fsync.warningthresholdms in zoo.cfg not working
> ---
>
> Key: ZOOKEEPER-2195
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2195
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: quorum
>Affects Versions: 3.4.6, 3.5.0
>Reporter: David Fan
>Assignee: Biju Nair
>Priority: Trivial
> Fix For: 3.4.9, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2195-1.patch, ZOOKEEPER-2195-DOC.patch, 
> ZOOKEEPER-2195.patch
>
>
> Config fsync.warningthresholdms in zoo.cfg does not work.
> I find QuorumPeerConfig.parseProperties give fsync.warningthresholdms a 
> prefix like "zookeeper.fsync.warningthresholdms".  But in class FileTxnLog 
> where fsync.warningthresholdms is used, code is 
> :Long.getLong("fsync.warningthresholdms", 1000),without prefix "zookeeper.", 
> therefore can not get fsync.warningthresholdms's value.
> I wonder the speed of fsync, need this config to see whether the speed is 
> good enough.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)