date:20161214

[jira] [Created] (ZOOKEEPER-2645) If embedded QuorumPeerMain is started with Properties no backupOldConfig should be done

2016-12-14 Thread Tom Pijl (JIRA)

Tom Pijl created ZOOKEEPER-2645:
---

 Summary: If embedded QuorumPeerMain is started with Properties no 
backupOldConfig should be done
 Key: ZOOKEEPER-2645
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2645
 Project: ZooKeeper
  Issue Type: Bug
  Components: server
Affects Versions: 3.5.2
Reporter: Tom Pijl
Priority: Blocker


When starting an embedded _QuorumPeerMain_ by executing the _runFromConfig()_ 
and providing _QuorumPeerConfig_ properties:
{code}standaloneEnabled=false
initLimit=5
syncLimit=2
clientPort=4101
server.1=nlbantpijl01.infor.com:2101:3101:participant;4101
dataDir=/Storage/zookeeper/server001{code}
an NullPointerException is thrown in the _QuorumPeerConfig_ class in the method 
_backupOldConfig()_ because the property configFileStr is null.

A check must be made at the start of the method _backupOldConfig()_ if the 
property _configFileStr_ is null. If so just exit the method. In the embedded 
mode there is no config file, so no need to create a backup.



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

ZooKeeper-trunk-WinVS2008 - Build # 2360 - Still Failing

2016-12-14 Thread Apache Jenkins Server

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 78 lines...]

ivy-retrieve:
[ivy:retrieve] :: Apache Ivy 2.4.0 - 20141213170938 :: 
http://ant.apache.org/ivy/ ::
[ivy:retrieve] :: loading settings :: file = 
f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\ivysettings.xml
[ivy:retrieve] :: resolving dependencies :: 
org.apache.zookeeper#zookeeper;3.6.0-SNAPSHOT
[ivy:retrieve]  confs: [default]
[ivy:retrieve]  found jline#jline;2.11 in maven2
[ivy:retrieve]  found org.eclipse.jetty#jetty-server;9.2.18.v20160721 in maven2
[ivy:retrieve]  found javax.servlet#javax.servlet-api;3.1.0 in maven2
[ivy:retrieve]  found org.eclipse.jetty#jetty-http;9.2.18.v20160721 in maven2
[ivy:retrieve]  found org.eclipse.jetty#jetty-util;9.2.18.v20160721 in maven2
[ivy:retrieve]  found org.eclipse.jetty#jetty-io;9.2.18.v20160721 in maven2
[ivy:retrieve]  found org.eclipse.jetty#jetty-servlet;9.2.18.v20160721 in maven2
[ivy:retrieve]  found org.eclipse.jetty#jetty-security;9.2.18.v20160721 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 org.slf4j#slf4j-log4j12;1.7.5 in maven2
[ivy:retrieve]  found commons-cli#commons-cli;1.2 in maven2
[ivy:retrieve]  found log4j#log4j;1.2.17 in maven2
[ivy:retrieve]  found io.netty#netty;3.10.5.Final in maven2
[ivy:retrieve]  found net.java.dev.javacc#javacc;5.0 in maven2
[ivy:retrieve] :: resolution report :: resolve 406ms :: artifacts dl 32ms
-
|  |modules||   artifacts   |
|   conf   | number| search|dwnlded|evicted|| number|dwnlded|
-
|  default |   16  |   0   |   0   |   0   ||   16  |   0   |
-
[ivy:retrieve] :: retrieving :: org.apache.zookeeper#zookeeper
[ivy:retrieve]  confs: [default]
[ivy:retrieve]  16 artifacts copied, 0 already retrieved (4635kB/31ms)

generate_jute_parser:
[mkdir] Created dir: 
f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\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 = 
f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\ivysettings.xml
 [move] Moving 1 file to 
f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\build\lib
   [javacc] Java Compiler Compiler Version 5.0 (Parser Generator)
   [javacc] (type "javacc" with no arguments for help)
   [javacc] Reading from file 
f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\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:

BUILD FAILED
f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\build.xml:273: 
Unable to find a javac compiler;
com.sun.tools.javac.Main is not on the classpath.
Perhaps JAVA_HOME does not point to the JDK.
It is currently set to "C:\Program Files\Java\jre1.8.0_92"

Total time: 3 seconds
Build step 'Invoke Ant' marked build as failure
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



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

[GitHub] zookeeper pull request #119: ZOOKEEPER-2251:Add Client side packet response ...

2016-12-14 Thread hanm

Github user hanm commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/119#discussion_r92530333
  
--- Diff: src/java/main/org/apache/zookeeper/ClientCnxn.java ---
@@ -1495,10 +1504,21 @@ public ReplyHeader submitRequest(RequestHeader h, 
Record request,
 Packet packet = queuePacket(h, r, request, response, null, null, 
null,
 null, watchRegistration, watchDeregistration);
 synchronized (packet) {
+long waitStartTime = System.currentTimeMillis();
 while (!packet.finished) {
-packet.wait();
+packet.wait(requestTimeout);
+if (!packet.finished && ((System.currentTimeMillis()
--- End diff --

Yes, and actually we have a Time class which we can use here that uses 
nanoTime internally for exact same reason. 


---
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-2251) Add Client side packet response timeout to avoid infinite wait.

2016-12-14 Thread Michael Han (JIRA)


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

Michael Han commented on ZOOKEEPER-2251:


Thanks for the info, [~m.martinez]. 

On a side note about sharing ZK with other processes: it is generally advised 
to have ZK deployed on dedicated resource - sometimes you might even want to 
have dedicated device for storing transaction log files. 

> Add Client side packet response timeout to avoid infinite wait.
> ---
>
> Key: ZOOKEEPER-2251
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2251
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.4.9, 3.5.2
>Reporter: nijel
>Assignee: Arshad Mohammad
>Priority: Critical
>  Labels: fault
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2251-01.patch, ZOOKEEPER-2251-02.patch, 
> ZOOKEEPER-2251-03.patch, ZOOKEEPER-2251-04.patch
>
>
> I came across one issue related to Client side packet response timeout In my 
> cluster many packet drops happened for some time.
> One observation is the zookeeper client got hanged. As per the thread dump it 
> is waiting for the response/ACK for the operation performed (synchronous API 
> used here).
> I am using 
> zookeeper.serverCnxnFactory=org.apache.zookeeper.server.NIOServerCnxnFactory
> Since only few packets missed there is no DISCONNECTED event occurred.
> Need add a "response time out" for the operations or packets.
> *Comments from [~rakeshr]*
> My observation about the problem:-
> * Can use tools like 'Wireshark' to simulate the artificial packet loss.
> * Assume there is only one packet in the 'outgoingQueue' and unfortunately 
> the server response packet lost. Now, client will enter into infinite 
> waiting. 
> https://github.com/apache/zookeeper/blob/trunk/src/java/main/org/apache/zookeeper/ClientCnxn.java#L1515
> * Probably we can discuss more about this problem and possible solutions(add 
> packet ACK timeout or another better approach) in the jira.



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

[jira] [Commented] (ZOOKEEPER-2470) ServerConfig#parse(String[]) ignores tickTime

2016-12-14 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on ZOOKEEPER-2470:
---

Github user eribeiro commented on the issue:

https://github.com/apache/zookeeper/pull/125
  
+1, the fix is quite trivial, but I am gonna add an unit test to guard 
against regressions, for example. 


> ServerConfig#parse(String[])  ignores tickTime
> --
>
> Key: ZOOKEEPER-2470
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2470
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.4.7, 3.5.1
>Reporter: Alexander Shraer
>Assignee: Edward Ribeiro
>Priority: Trivial
> Fix For: 3.4.10, 3.5.3
>
> Attachments: ZOOKEEPER-2470.patch
>
>
> Based on bug report from ykgarfield:
> ServerConfig#parse(String[]) method has the following code:
> public void parse(String[] args) {
> ...
> if (args.length == 3) {
> tickTime = Integer.parseInt(args[2]);
> }
> if (args.length == 4) {
> maxClientCnxns = Integer.parseInt(args[3]);
> }
> }
> ```
> So if args.length == 4 tickTime isn't parsed.



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

[GitHub] zookeeper issue #125: ZOOKEEPER-2470: ServerConfig#parse(String[]) ignores t...

2016-12-14 Thread eribeiro

Github user eribeiro commented on the issue:

https://github.com/apache/zookeeper/pull/125
  
+1, the fix is quite trivial, but I am gonna add an unit test to guard 
against regressions, for example. 


---
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-2470) ServerConfig#parse(String[]) ignores tickTime

2016-12-14 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on ZOOKEEPER-2470:
---

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/125
  
patch looks good, it would be great if there is also a test (though the fix 
is pretty obvious..).


> ServerConfig#parse(String[])  ignores tickTime
> --
>
> Key: ZOOKEEPER-2470
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2470
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.4.7, 3.5.1
>Reporter: Alexander Shraer
>Assignee: Edward Ribeiro
>Priority: Trivial
> Fix For: 3.4.10, 3.5.3
>
> Attachments: ZOOKEEPER-2470.patch
>
>
> Based on bug report from ykgarfield:
> ServerConfig#parse(String[]) method has the following code:
> public void parse(String[] args) {
> ...
> if (args.length == 3) {
> tickTime = Integer.parseInt(args[2]);
> }
> if (args.length == 4) {
> maxClientCnxns = Integer.parseInt(args[3]);
> }
> }
> ```
> So if args.length == 4 tickTime isn't parsed.



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

[GitHub] zookeeper issue #125: ZOOKEEPER-2470: ServerConfig#parse(String[]) ignores t...

2016-12-14 Thread hanm

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/125
  
patch looks good, it would be great if there is also a test (though the fix 
is pretty obvious..).


---
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-1364) Add orthogonal fault injection mechanism/framework

2016-12-14 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on ZOOKEEPER-1364:
---

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/123
  
Good initiative, @eribeiro! This will be a valuable addition to the 
project. Please keep driving this forward.

Regarding dependency between ZOOKEEPER-2549 and ZOOKEEPER-1364, the mock 
stuff ZOOKEEPER-2549 introduced is localized so it shouldn't take a lot effort 
to replace that with what to be done in ZOOKEEPER-1364. Since ZOOKEEPER-2549 is 
in relative good shape to be merged in my opinion here is to get ZOOKEEPER-2549 
in first then start iterating on ZOOKEEPER-1364.


> Add orthogonal fault injection mechanism/framework
> --
>
> Key: ZOOKEEPER-1364
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1364
> Project: ZooKeeper
>  Issue Type: Test
>  Components: tests
>Reporter: Andrei Savu
>Assignee: Andrei Savu
>
> Hadoop has a mechanism for doing fault injection (HDFS-435). I think it would 
> be useful if something similar would be available for ZooKeeper. 



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

[GitHub] zookeeper issue #123: ZOOKEEPER-1364: Add orthogonal fault injection mechani...

2016-12-14 Thread hanm

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/123
  
Good initiative, @eribeiro! This will be a valuable addition to the 
project. Please keep driving this forward.

Regarding dependency between ZOOKEEPER-2549 and ZOOKEEPER-1364, the mock 
stuff ZOOKEEPER-2549 introduced is localized so it shouldn't take a lot effort 
to replace that with what to be done in ZOOKEEPER-1364. Since ZOOKEEPER-2549 is 
in relative good shape to be merged in my opinion here is to get ZOOKEEPER-2549 
in first then start iterating on ZOOKEEPER-1364.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

ZooKeeper-trunk - Build # 3193 - Failure

2016-12-14 Thread Apache Jenkins Server

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 438601 lines...]
[junit] 2016-12-14 23:29:18,186 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x101901639d5
[junit] 2016-12-14 23:29:18,187 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 169776
[junit] 2016-12-14 23:29:18,187 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 1642
[junit] 2016-12-14 23:29:18,187 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testWatcherAutoResetWithLocal
[junit] 2016-12-14 23:29:18,187 [myid:] - INFO  [main:ClientBase@543] - 
tearDown starting
[junit] 2016-12-14 23:29:18,187 [myid:] - INFO  [main:ClientBase@513] - 
STOPPING server
[junit] 2016-12-14 23:29:18,187 [myid:] - INFO  
[main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:27624
[junit] 2016-12-14 23:29:18,191 [myid:] - INFO  [main:ZooKeeperServer@534] 
- shutting down
[junit] 2016-12-14 23:29:18,191 [myid:] - ERROR [main:ZooKeeperServer@506] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2016-12-14 23:29:18,191 [myid:] - INFO  
[main:SessionTrackerImpl@232] - Shutting down
[junit] 2016-12-14 23:29:18,191 [myid:] - INFO  
[main:PrepRequestProcessor@1009] - Shutting down
[junit] 2016-12-14 23:29:18,191 [myid:] - INFO  
[main:SyncRequestProcessor@191] - Shutting down
[junit] 2016-12-14 23:29:18,192 [myid:] - INFO  [ProcessThread(sid:0 
cport:27624)::PrepRequestProcessor@157] - PrepRequestProcessor exited loop!
[junit] 2016-12-14 23:29:18,192 [myid:] - INFO  
[main:FinalRequestProcessor@481] - shutdown of request processor complete
[junit] 2016-12-14 23:29:18,192 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited!
[junit] 2016-12-14 23:29:18,192 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port27624,name1=InMemoryDataTree]
[junit] 2016-12-14 23:29:18,192 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port27624]
[junit] 2016-12-14 23:29:18,193 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 27624
[junit] 2016-12-14 23:29:18,193 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-12-14 23:29:18,197 [myid:] - INFO  [main:ClientBase@568] - 
fdcount after test is: 4828 at start it was 4828
[junit] 2016-12-14 23:29:18,197 [myid:] - INFO  [main:ZKTestCase$1@65] - 
SUCCEEDED testWatcherAutoResetWithLocal
[junit] 2016-12-14 23:29:18,197 [myid:] - INFO  [main:ZKTestCase$1@60] - 
FINISHED testWatcherAutoResetWithLocal
[junit] Tests run: 101, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
527.16 sec, Thread: 7, Class: org.apache.zookeeper.test.NioNettySuiteTest
[junit] 2016-12-14 23:29:18,293 [myid:127.0.0.1:27501] - INFO  
[main-SendThread(127.0.0.1:27501):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:27501. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2016-12-14 23:29:18,293 [myid:127.0.0.1:27501] - WARN  
[main-SendThread(127.0.0.1:27501):ClientCnxn$SendThread@1235] - Session 
0x1019012f74a for server 127.0.0.1/127.0.0.1:27501, unexpected error, 
closing socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2016-12-14 23:29:18,441 [myid:127.0.0.1:27507] - INFO  
[main-SendThread(127.0.0.1:27507):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:27507. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2016-12-14 23:29:18,442 [myid:127.0.0.1:27507] - WARN  
[main-SendThread(127.0.0.1:27507):ClientCnxn$SendThread@1235] - Session 
0x3019012f74f for server 127.0.0.1/127.0.0.1:27507, unexpected error, 
closing socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit]

[jira] [Commented] (ZOOKEEPER-2642) ZOOKEEPER-2014 breaks existing clients for little benefit

2016-12-14 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on ZOOKEEPER-2642:
---

Github user eribeiro commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/122#discussion_r92507667
  
--- Diff: src/java/main/org/apache/zookeeper/ZooKeeper.java ---
@@ -2910,4 +2923,49 @@ private ClientCnxnSocket getClientCnxnSocket() 
throws IOException {
 throw ioe;
 }
 }
+
+protected byte[] internalReconfig(String joiningServers, String 
leavingServers, String newMembers, long fromConfig, Stat stat) throws 
KeeperException, InterruptedException
+{
--- End diff --

nit: inconsistent brace style for method names from line onwards.


> ZOOKEEPER-2014 breaks existing clients for little benefit
> -
>
> Key: ZOOKEEPER-2642
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2642
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: c client, java client
>Affects Versions: 3.5.2
>Reporter: Jordan Zimmerman
>Assignee: Jordan Zimmerman
>Priority: Blocker
> Attachments: ZOOKEEPER-2642.patch, ZOOKEEPER-2642.patch, 
> ZOOKEEPER-2642.patch
>
>
> ZOOKEEPER-2014 moved the reconfig() methods into a new class, ZooKeeperAdmin. 
> It appears this was done to document that these are methods have access 
> restrictions. However, this change breaks Apache Curator (and possibly other 
> clients). Curator APIs will have to be changed and/or special methods need to 
> be added. A breaking change of this kind should only be done when the benefit 
> is overwhelming. In this case, the same information can be conveyed with 
> documentation and possibly a deprecation notice.
> Revert the creation of the ZooKeeperAdmin class and move the reconfig() 
> methods back to the ZooKeeper class with additional documentation.



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

[GitHub] zookeeper pull request #122: [ZOOKEEPER-2642] Resurrect the reconfig() metho...

2016-12-14 Thread eribeiro

Github user eribeiro commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/122#discussion_r92507667
  
--- Diff: src/java/main/org/apache/zookeeper/ZooKeeper.java ---
@@ -2910,4 +2923,49 @@ private ClientCnxnSocket getClientCnxnSocket() 
throws IOException {
 throw ioe;
 }
 }
+
+protected byte[] internalReconfig(String joiningServers, String 
leavingServers, String newMembers, long fromConfig, Stat stat) throws 
KeeperException, InterruptedException
+{
--- End diff --

nit: inconsistent brace style for method names from line onwards.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

2016-12-14 Thread Apache Jenkins Server

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

###
## LAST 60 LINES OF THE CONSOLE 
###
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H12 (ubuntu) in workspace 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url git://git.apache.org/zookeeper.git # timeout=10
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
Resetting working tree
 > git reset --hard # timeout=10
 > git clean -fdx # timeout=10
Fetching upstream changes from git://git.apache.org/zookeeper.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > git://git.apache.org/zookeeper.git +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision cd0e323831c8b4cde64976325bfc79bb53cdd9b7 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f cd0e323831c8b4cde64976325bfc79bb53cdd9b7
 > git rev-list cd0e323831c8b4cde64976325bfc79bb53cdd9b7 # timeout=10
No emails were triggered.
[ZooKeeper-trunk-openjdk7] $ /home/jenkins/tools/ant/latest/bin/ant 
-Dtest.output=yes -Dtest.junit.threads=8 -Dtest.junit.output.format=xml 
-Djavac.target=1.7 clean test-core-java
Error: JAVA_HOME is not defined correctly.
  We cannot execute /usr/lib/jvm/java-7-openjdk-amd64//bin/java
Build step 'Invoke Ant' marked build as failure
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



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

[jira] [Commented] (ZOOKEEPER-2470) ServerConfig#parse(String[]) ignores tickTime

2016-12-14 Thread Edward Ribeiro (JIRA)


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

Edward Ribeiro commented on ZOOKEEPER-2470:
---

I had an email chat with @shralex and he said I could get this issue to push 
forward. Even though the issue is *quite trivial*, I've got in touch with him 
because it would be really important to have this bug fixed for 3.4, 3.5 and 
master branches asap.


> ServerConfig#parse(String[])  ignores tickTime
> --
>
> Key: ZOOKEEPER-2470
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2470
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.4.7, 3.5.1
>Reporter: Alexander Shraer
>Assignee: Edward Ribeiro
>Priority: Trivial
> Fix For: 3.4.10, 3.5.3
>
> Attachments: ZOOKEEPER-2470.patch
>
>
> Based on bug report from ykgarfield:
> ServerConfig#parse(String[]) method has the following code:
> public void parse(String[] args) {
> ...
> if (args.length == 3) {
> tickTime = Integer.parseInt(args[2]);
> }
> if (args.length == 4) {
> maxClientCnxns = Integer.parseInt(args[3]);
> }
> }
> ```
> So if args.length == 4 tickTime isn't parsed.



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

[jira] [Assigned] (ZOOKEEPER-2470) ServerConfig#parse(String[]) ignores tickTime

2016-12-14 Thread Edward Ribeiro (JIRA)


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

Edward Ribeiro reassigned ZOOKEEPER-2470:
-

Assignee: Edward Ribeiro  (was: Alexander Shraer)

> ServerConfig#parse(String[])  ignores tickTime
> --
>
> Key: ZOOKEEPER-2470
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2470
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.4.7, 3.5.1
>Reporter: Alexander Shraer
>Assignee: Edward Ribeiro
>Priority: Trivial
> Fix For: 3.4.10, 3.5.3
>
> Attachments: ZOOKEEPER-2470.patch
>
>
> Based on bug report from ykgarfield:
> ServerConfig#parse(String[]) method has the following code:
> public void parse(String[] args) {
> ...
> if (args.length == 3) {
> tickTime = Integer.parseInt(args[2]);
> }
> if (args.length == 4) {
> maxClientCnxns = Integer.parseInt(args[3]);
> }
> }
> ```
> So if args.length == 4 tickTime isn't parsed.



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

Failed: ZOOKEEPER- PreCommit Build #120

2016-12-14 Thread Apache Jenkins Server

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/120/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 25 lines...]
  Getting sizes
Done: 9
  Compressing objects
Done: 0
  Writing objects
Done: 10
  remote: Updating references
Merging refs/tags/changes/120
 > git rev-parse refs/tags/changes/120^{commit} # timeout=10
 > git merge 6d4545704b1f13788a5785e6ab190714c3b6d333 # timeout=10
 > git rev-parse branch-3.4^{commit} # timeout=10
Checking out Revision 6d4545704b1f13788a5785e6ab190714c3b6d333 (branch-3.4)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 6d4545704b1f13788a5785e6ab190714c3b6d333
 > git rev-parse origin/branch-3.4^{commit} # timeout=10
 > git rev-list 9d89dd1134e43c9a4d5e76e2314557e889f2a171 # timeout=10
No emails were triggered.
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[PreCommit-ZOOKEEPER-github-pr-build] $ /bin/bash 
/tmp/hudson6606148225560516943.sh
/home/jenkins/tools/java/latest1.7/bin/java
java version "1.7.0_80"
Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)
core file size  (blocks, -c) 0
data seg size   (kbytes, -d) unlimited
scheduling priority (-e) 0
file size   (blocks, -f) unlimited
pending signals (-i) 386178
max locked memory   (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files  (-n) 6
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 8192
cpu time   (seconds, -t) unlimited
max user processes  (-u) 10240
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited
Buildfile: 
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build.xml

BUILD FAILED
Target "qa-test-pullrequest" does not exist in the project "ZooKeeper". 

Total time: 0 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
[description-setter] Could not determine description.
Putting comment on the pull request
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



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

[jira] [Commented] (ZOOKEEPER-2470) ServerConfig#parse(String[]) ignores tickTime

2016-12-14 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on ZOOKEEPER-2470:
---

GitHub user eribeiro opened a pull request:

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

ZOOKEEPER-2470: ServerConfig#parse(String[]) ignores tickTime



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

$ git pull https://github.com/eribeiro/zookeeper ZOOKEEPER-2470

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

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


commit 6d4545704b1f13788a5785e6ab190714c3b6d333
Author: Edward Ribeiro 
Date:   2016-12-14T19:23:07Z

ZOOKEEPER-2470: ServerConfig#parse(String[]) ignores tickTime




> ServerConfig#parse(String[])  ignores tickTime
> --
>
> Key: ZOOKEEPER-2470
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2470
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.4.7, 3.5.1
>Reporter: Alexander Shraer
>Assignee: Alexander Shraer
>Priority: Trivial
> Fix For: 3.4.10, 3.5.3
>
> Attachments: ZOOKEEPER-2470.patch
>
>
> Based on bug report from ykgarfield:
> ServerConfig#parse(String[]) method has the following code:
> public void parse(String[] args) {
> ...
> if (args.length == 3) {
> tickTime = Integer.parseInt(args[2]);
> }
> if (args.length == 4) {
> maxClientCnxns = Integer.parseInt(args[3]);
> }
> }
> ```
> So if args.length == 4 tickTime isn't parsed.



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

[GitHub] zookeeper pull request #125: ZOOKEEPER-2470: ServerConfig#parse(String[]) ig...

2016-12-14 Thread eribeiro

GitHub user eribeiro opened a pull request:

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

ZOOKEEPER-2470: ServerConfig#parse(String[]) ignores tickTime



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

$ git pull https://github.com/eribeiro/zookeeper ZOOKEEPER-2470

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

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


commit 6d4545704b1f13788a5785e6ab190714c3b6d333
Author: Edward Ribeiro 
Date:   2016-12-14T19:23:07Z

ZOOKEEPER-2470: ServerConfig#parse(String[]) ignores tickTime




---
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-2251) Add Client side packet response timeout to avoid infinite wait.

2016-12-14 Thread Mel Martinez (JIRA)


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

Mel Martinez commented on ZOOKEEPER-2251:
-

Unfortunately I don't have a simple deterministic test.  But we had an 
environment where two of our zookeeper servers were sharing their nodes with 
another cpu & memory (& thread) hungry process and this seemed to result in a 
lot of zookeepertimeoutexceptions at the client as well as unfortunately 
frequent hits on this particular deadlock (which does get caught in jvisualvm 
thread dumps).   We could not run more than a day or two on our sustained 
ingest tests without hitting this.

We've moved the two zookeepers to dedicated nodes  (the third already was on 
it's own node) and things have looked stable so far (on this particular issue), 
but my management is rightfully concerned that we should have this fix in place.

We would be perfectly fine with a parameterized wait time option and a default 
of the current indefinite wait.

> Add Client side packet response timeout to avoid infinite wait.
> ---
>
> Key: ZOOKEEPER-2251
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2251
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.4.9, 3.5.2
>Reporter: nijel
>Assignee: Arshad Mohammad
>Priority: Critical
>  Labels: fault
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2251-01.patch, ZOOKEEPER-2251-02.patch, 
> ZOOKEEPER-2251-03.patch, ZOOKEEPER-2251-04.patch
>
>
> I came across one issue related to Client side packet response timeout In my 
> cluster many packet drops happened for some time.
> One observation is the zookeeper client got hanged. As per the thread dump it 
> is waiting for the response/ACK for the operation performed (synchronous API 
> used here).
> I am using 
> zookeeper.serverCnxnFactory=org.apache.zookeeper.server.NIOServerCnxnFactory
> Since only few packets missed there is no DISCONNECTED event occurred.
> Need add a "response time out" for the operations or packets.
> *Comments from [~rakeshr]*
> My observation about the problem:-
> * Can use tools like 'Wireshark' to simulate the artificial packet loss.
> * Assume there is only one packet in the 'outgoingQueue' and unfortunately 
> the server response packet lost. Now, client will enter into infinite 
> waiting. 
> https://github.com/apache/zookeeper/blob/trunk/src/java/main/org/apache/zookeeper/ClientCnxn.java#L1515
> * Probably we can discuss more about this problem and possible solutions(add 
> packet ACK timeout or another better approach) in the jira.



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

Failed: ZOOKEEPER- PreCommit Build #119

2016-12-14 Thread Apache Jenkins Server

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/119/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 25 lines...]
  Getting sizes
Done: 3
  Compressing objects
Done: 0
  Writing objects
Done: 4
  remote: Updating references
Merging refs/tags/changes/119
 > git rev-parse refs/tags/changes/119^{commit} # timeout=10
 > git merge 0fd4ca143499cafc8a7090f2dea32f733ccd08d8 # timeout=10
 > git rev-parse branch-3.4^{commit} # timeout=10
Checking out Revision 0fd4ca143499cafc8a7090f2dea32f733ccd08d8 (branch-3.4)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 0fd4ca143499cafc8a7090f2dea32f733ccd08d8
 > git rev-parse origin/branch-3.4^{commit} # timeout=10
 > git rev-list 9d89dd1134e43c9a4d5e76e2314557e889f2a171 # timeout=10
No emails were triggered.
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[PreCommit-ZOOKEEPER-github-pr-build] $ /bin/bash 
/tmp/hudson3741345849396548413.sh
/home/jenkins/tools/java/latest1.7/bin/java
java version "1.7.0_80"
Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)
core file size  (blocks, -c) 0
data seg size   (kbytes, -d) unlimited
scheduling priority (-e) 0
file size   (blocks, -f) unlimited
pending signals (-i) 386178
max locked memory   (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files  (-n) 6
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 8192
cpu time   (seconds, -t) unlimited
max user processes  (-u) 10240
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited
Buildfile: 
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build.xml

BUILD FAILED
Target "qa-test-pullrequest" does not exist in the project "ZooKeeper". 

Total time: 0 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
[description-setter] Could not determine description.
Putting comment on the pull request
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



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

[jira] [Commented] (ZOOKEEPER-2552) Revisit release note doc and remove the items which are not related to the released version

2016-12-14 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on ZOOKEEPER-2552:
---

GitHub user eribeiro opened a pull request:

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

ZOOKEEPER-2552: Revisit release doc and remove the issues not covered by 
release



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

$ git pull https://github.com/eribeiro/zookeeper ZOOKEEPER-2552

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

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


commit 0fd4ca143499cafc8a7090f2dea32f733ccd08d8
Author: Edward Ribeiro 
Date:   2016-12-14T19:09:52Z

ZOOKEEPER-2552: Revisit release note doc and remove the items which are not 
related to the released version




> Revisit release note doc and remove the items which are not related to the 
> released version
> ---
>
> Key: ZOOKEEPER-2552
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2552
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Rakesh R
>Assignee: Edward Ribeiro
> Fix For: 3.4.10
>
> Attachments: ZOOKEEPER-2552.patch, closed.py
>
>
> Couple of issues listed on http://zookeeper.apache.org/
> doc/r3.4.9/releasenotes.html that are either 'Open' or 'Patch available'. For 
> example, issues were wrongly marked as "3.4.8" fix version in jira and has 
> caused the trouble.
> This jira to cross check all the jira issues present in the release note and 
> check the correctness.



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

[GitHub] zookeeper pull request #124: ZOOKEEPER-2552: Revisit release doc and remove ...

2016-12-14 Thread eribeiro

GitHub user eribeiro opened a pull request:

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

ZOOKEEPER-2552: Revisit release doc and remove the issues not covered by 
release



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

$ git pull https://github.com/eribeiro/zookeeper ZOOKEEPER-2552

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

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


commit 0fd4ca143499cafc8a7090f2dea32f733ccd08d8
Author: Edward Ribeiro 
Date:   2016-12-14T19:09:52Z

ZOOKEEPER-2552: Revisit release note doc and remove the items which are not 
related to the released version




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

ZooKeeper_branch35_solaris - Build # 351 - Still Failing

2016-12-14 Thread Apache Jenkins Server

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 537183 lines...]
[junit] 2016-12-14 17:26:31,048 [myid:] - INFO  [main:ClientBase@386] - 
CREATING server instance 127.0.0.1:11222
[junit] 2016-12-14 17:26:31,049 [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-12-14 17:26:31,049 [myid:] - INFO  
[main:NIOServerCnxnFactory@686] - binding to port 0.0.0.0/0.0.0.0:11222
[junit] 2016-12-14 17:26:31,050 [myid:] - INFO  [main:ClientBase@361] - 
STARTING server instance 127.0.0.1:11222
[junit] 2016-12-14 17:26:31,050 [myid:] - INFO  [main:ZooKeeperServer@893] 
- minSessionTimeout set to 6000
[junit] 2016-12-14 17:26:31,050 [myid:] - INFO  [main:ZooKeeperServer@902] 
- maxSessionTimeout set to 6
[junit] 2016-12-14 17:26:31,050 [myid:] - INFO  [main:ZooKeeperServer@159] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/build/test/tmp/test8046202900984478926.junit.dir/version-2
 snapdir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/build/test/tmp/test8046202900984478926.junit.dir/version-2
[junit] 2016-12-14 17:26:31,051 [myid:] - INFO  [main:FileSnap@83] - 
Reading snapshot 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/build/test/tmp/test8046202900984478926.junit.dir/version-2/snapshot.b
[junit] 2016-12-14 17:26:31,053 [myid:] - INFO  [main:FileTxnSnapLog@306] - 
Snapshotting: 0xb to 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/build/test/tmp/test8046202900984478926.junit.dir/version-2/snapshot.b
[junit] 2016-12-14 17:26:31,054 [myid:] - ERROR [main:ZooKeeperServer@505] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2016-12-14 17:26:31,054 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222
[junit] 2016-12-14 17:26:31,055 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@296]
 - Accepted socket connection from /127.0.0.1:40004
[junit] 2016-12-14 17:26:31,056 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@485] - Processing stat command from 
/127.0.0.1:40004
[junit] 2016-12-14 17:26:31,056 [myid:] - INFO  
[NIOWorkerThread-1:StatCommand@49] - Stat command output
[junit] 2016-12-14 17:26:31,056 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@607] - Closed socket connection for client 
/127.0.0.1:40004 (no session established for client)
[junit] 2016-12-14 17:26:31,056 [myid:] - INFO  [main:JMXEnv@228] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-12-14 17:26:31,058 [myid:] - INFO  [main:JMXEnv@245] - 
expect:InMemoryDataTree
[junit] 2016-12-14 17:26:31,058 [myid:] - INFO  [main:JMXEnv@249] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree
[junit] 2016-12-14 17:26:31,058 [myid:] - INFO  [main:JMXEnv@245] - 
expect:StandaloneServer_port
[junit] 2016-12-14 17:26:31,058 [myid:] - INFO  [main:JMXEnv@249] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222
[junit] 2016-12-14 17:26:31,058 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 17743
[junit] 2016-12-14 17:26:31,058 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 24
[junit] 2016-12-14 17:26:31,059 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testQuota
[junit] 2016-12-14 17:26:31,059 [myid:] - INFO  [main:ClientBase@543] - 
tearDown starting
[junit] 2016-12-14 17:26:31,142 [myid:] - INFO  [main:ZooKeeper@1311] - 
Session: 0x1257b58f112 closed
[junit] 2016-12-14 17:26:31,142 [myid:] - INFO  [main:ClientBase@513] - 
STOPPING server
[junit] 2016-12-14 17:26:31,142 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x1257b58f112
[junit] 2016-12-14 17:26:31,142 [myid:] - INFO  
[ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - 
ConnnectionExpirerThread interrupted
[junit] 2016-12-14 17:26:31,142 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2016-12-14 17:26:31,142 [myid:] - INFO

[jira] [Commented] (ZOOKEEPER-1364) Add orthogonal fault injection mechanism/framework

2016-12-14 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on ZOOKEEPER-1364:
---

Github user eribeiro commented on the issue:

https://github.com/apache/zookeeper/pull/123
  
@yufeldman Sure, totally agree about this being a separate issue! :+1: 

My only concern is that **IF** we decide to introduce this injection 
framework into ZK **after merging ZOOKEEPER-2549** then some of the mocking and 
reflection changes introduced by ZOOKEEPER-2549 for the purposes of testing 
become redundant, so basically we would have to undo parts of it (but not the 
bug fix, of course). See this PR for a concrete idea of what I am trying to say.

But you raised a very important point: **ZOOKEEPER-2549 is critical, and 
delaying its merging is gonna be bad for the project release, IMHO.** So, I am 
all for you keep going your work (congrats, btw) and run this as a future 
issue. Or whatever the committers find more suitable.  /cc @fpj @rgs1 @hanm 
@phunt



> Add orthogonal fault injection mechanism/framework
> --
>
> Key: ZOOKEEPER-1364
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1364
> Project: ZooKeeper
>  Issue Type: Test
>  Components: tests
>Reporter: Andrei Savu
>Assignee: Andrei Savu
>
> Hadoop has a mechanism for doing fault injection (HDFS-435). I think it would 
> be useful if something similar would be available for ZooKeeper. 



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

[GitHub] zookeeper issue #123: ZOOKEEPER-1364: Add orthogonal fault injection mechani...

2016-12-14 Thread eribeiro

Github user eribeiro commented on the issue:

https://github.com/apache/zookeeper/pull/123
  
@yufeldman Sure, totally agree about this being a separate issue! :+1: 

My only concern is that **IF** we decide to introduce this injection 
framework into ZK **after merging ZOOKEEPER-2549** then some of the mocking and 
reflection changes introduced by ZOOKEEPER-2549 for the purposes of testing 
become redundant, so basically we would have to undo parts of it (but not the 
bug fix, of course). See this PR for a concrete idea of what I am trying to say.

But you raised a very important point: **ZOOKEEPER-2549 is critical, and 
delaying its merging is gonna be bad for the project release, IMHO.** So, I am 
all for you keep going your work (congrats, btw) and run this as a future 
issue. Or whatever the committers find more suitable.  /cc @fpj @rgs1 @hanm 
@phunt



---
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-1364) Add orthogonal fault injection mechanism/framework

2016-12-14 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on ZOOKEEPER-1364:
---

Github user yufeldman commented on the issue:

https://github.com/apache/zookeeper/pull/123
  
@eribeiro  I am not sure that critical bug is the place to introduce 
injection framework to Zookeeper. Can't it be done as a separate JIRA?


> Add orthogonal fault injection mechanism/framework
> --
>
> Key: ZOOKEEPER-1364
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1364
> Project: ZooKeeper
>  Issue Type: Test
>  Components: tests
>Reporter: Andrei Savu
>Assignee: Andrei Savu
>
> Hadoop has a mechanism for doing fault injection (HDFS-435). I think it would 
> be useful if something similar would be available for ZooKeeper. 



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

[GitHub] zookeeper issue #123: ZOOKEEPER-1364: Add orthogonal fault injection mechani...

2016-12-14 Thread yufeldman

Github user yufeldman commented on the issue:

https://github.com/apache/zookeeper/pull/123
  
@eribeiro  I am not sure that critical bug is the place to introduce 
injection framework to Zookeeper. Can't it be done as a separate JIRA?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

ZooKeeper_branch34_openjdk7 - Build # 1307 - Still Failing

2016-12-14 Thread Apache Jenkins Server

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 196375 lines...]
[junit] 2016-12-14 15:11:25,046 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2016-12-14 15:11:25,046 [myid:] - INFO  [main:ZooKeeperServer@497] 
- shutting down
[junit] 2016-12-14 15:11:25,046 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2016-12-14 15:11:25,046 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2016-12-14 15:11:25,047 [myid:] - INFO  
[main:PrepRequestProcessor@765] - Shutting down
[junit] 2016-12-14 15:11:25,047 [myid:] - INFO  
[main:SyncRequestProcessor@208] - Shutting down
[junit] 2016-12-14 15:11:25,047 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2016-12-14 15:11:25,047 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited!
[junit] 2016-12-14 15:11:25,048 [myid:] - INFO  
[main:FinalRequestProcessor@402] - shutdown of request processor complete
[junit] 2016-12-14 15:11:25,048 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-12-14 15:11:25,049 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-12-14 15:11:25,050 [myid:] - INFO  [main:ClientBase@445] - 
STARTING server
[junit] 2016-12-14 15:11:25,050 [myid:] - INFO  [main:ClientBase@366] - 
CREATING server instance 127.0.0.1:11221
[junit] 2016-12-14 15:11:25,051 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2016-12-14 15:11:25,051 [myid:] - INFO  [main:ClientBase@341] - 
STARTING server instance 127.0.0.1:11221
[junit] 2016-12-14 15:11:25,052 [myid:] - INFO  [main:ZooKeeperServer@173] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_openjdk7/build/test/tmp/test3692162077902830418.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_openjdk7/build/test/tmp/test3692162077902830418.junit.dir/version-2
[junit] 2016-12-14 15:11:25,057 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2016-12-14 15:11:25,057 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-12-14 15:11:25,058 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:60797
[junit] 2016-12-14 15:11:25,058 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing 
stat command from /127.0.0.1:60797
[junit] 2016-12-14 15:11:25,059 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@663] - Stat command output
[junit] 2016-12-14 15:11:25,059 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1008] - Closed socket connection for client 
/127.0.0.1:60797 (no session established for client)
[junit] 2016-12-14 15:11:25,060 [myid:] - INFO  [main:JMXEnv@229] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-12-14 15:11:25,062 [myid:] - INFO  [main:JMXEnv@246] - 
expect:InMemoryDataTree
[junit] 2016-12-14 15:11:25,062 [myid:] - INFO  [main:JMXEnv@250] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2016-12-14 15:11:25,062 [myid:] - INFO  [main:JMXEnv@246] - 
expect:StandaloneServer_port
[junit] 2016-12-14 15:11:25,063 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2016-12-14 15:11:25,063 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 32716
[junit] 2016-12-14 15:11:25,063 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2016-12-14 15:11:25,063 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2016-12-14 15:11:25,064 [myid:] - INFO  [main:ClientBase@522] - 
tearDown starting
[junit] 2016-12-14 15:11:25,129 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x158fde358d3 closed
[junit] 2016-12-14 15:11:25,129 [myid:] - INFO  [main:ClientBase@492] - 
STOPPING server
[junit] 2016-12-14 15:11:25,129 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x158fde358d3
[junit] 2016-12-14

ZooKeeper_branch34_solaris - Build # 1389 - Still Failing

2016-12-14 Thread Apache Jenkins Server

See https://builds.apache.org/job/ZooKeeper_branch34_solaris/1389/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 175542 lines...]
[junit] 2016-12-14 13:57:02,094 [myid:] - INFO  [main:ZooKeeperServer@497] 
- shutting down
[junit] 2016-12-14 13:57:02,094 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2016-12-14 13:57:02,094 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2016-12-14 13:57:02,094 [myid:] - INFO  
[main:PrepRequestProcessor@765] - Shutting down
[junit] 2016-12-14 13:57:02,094 [myid:] - INFO  
[main:SyncRequestProcessor@208] - Shutting down
[junit] 2016-12-14 13:57:02,094 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2016-12-14 13:57:02,095 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited!
[junit] 2016-12-14 13:57:02,095 [myid:] - INFO  
[main:FinalRequestProcessor@402] - shutdown of request processor complete
[junit] 2016-12-14 13:57:02,095 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-12-14 13:57:02,095 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-12-14 13:57:02,096 [myid:] - INFO  [main:ClientBase@445] - 
STARTING server
[junit] 2016-12-14 13:57:02,097 [myid:] - INFO  [main:ClientBase@366] - 
CREATING server instance 127.0.0.1:11221
[junit] 2016-12-14 13:57:02,097 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2016-12-14 13:57:02,097 [myid:] - INFO  [main:ClientBase@341] - 
STARTING server instance 127.0.0.1:11221
[junit] 2016-12-14 13:57:02,098 [myid:] - INFO  [main:ZooKeeperServer@173] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/build/test/tmp/test4905240768191933681.junit.dir/version-2
 snapdir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/build/test/tmp/test4905240768191933681.junit.dir/version-2
[junit] 2016-12-14 13:57:02,100 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2016-12-14 13:57:02,101 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-12-14 13:57:02,101 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:46879
[junit] 2016-12-14 13:57:02,101 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing 
stat command from /127.0.0.1:46879
[junit] 2016-12-14 13:57:02,102 [myid:] - INFO  
[Thread-5:NIOServerCnxn$StatCommand@663] - Stat command output
[junit] 2016-12-14 13:57:02,103 [myid:] - INFO  
[Thread-5:NIOServerCnxn@1008] - Closed socket connection for client 
/127.0.0.1:46879 (no session established for client)
[junit] 2016-12-14 13:57:02,103 [myid:] - INFO  [main:JMXEnv@229] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-12-14 13:57:02,104 [myid:] - INFO  [main:JMXEnv@246] - 
expect:InMemoryDataTree
[junit] 2016-12-14 13:57:02,104 [myid:] - INFO  [main:JMXEnv@250] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2016-12-14 13:57:02,104 [myid:] - INFO  [main:JMXEnv@246] - 
expect:StandaloneServer_port
[junit] 2016-12-14 13:57:02,104 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2016-12-14 13:57:02,105 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 9048
[junit] 2016-12-14 13:57:02,105 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2016-12-14 13:57:02,105 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2016-12-14 13:57:02,105 [myid:] - INFO  [main:ClientBase@522] - 
tearDown starting
[junit] 2016-12-14 13:57:02,182 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x158fd9f3ee1 closed
[junit] 2016-12-14 13:57:02,182 [myid:] - INFO  [main:ClientBase@492] - 
STOPPING server
[junit] 2016-12-14 13:57:02,182 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x158fd9f3ee1
[junit] 2016-12-14 13:57:02,183 [myid:] - INFO  [main:ZooKeeperServer@497] 
- shutting down
[junit] 2016-12-14 13:57:02,183 [myid:] -

[jira] [Commented] (ZOOKEEPER-1364) Add orthogonal fault injection mechanism/framework

2016-12-14 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on ZOOKEEPER-1364:
---

Github user eribeiro commented on the issue:

https://github.com/apache/zookeeper/pull/123
  
@yufeldman I really like your ZOOKEEPER-2549 patch, but I think it would be 
an awesome opportunity of introducing a much needed failure injection framework 
into ZooKeeper. So, I wrote this patch with your changes **as example** to see 
what is your opinion and if we could backport those changes to your PR or at 
least discuss the introduction of Byteman. IMHO, it would save a lot of changes 
due by ZK-2549, but I am really open to hear your opinion and concerns. Cheers! 
:smiley: 



> Add orthogonal fault injection mechanism/framework
> --
>
> Key: ZOOKEEPER-1364
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1364
> Project: ZooKeeper
>  Issue Type: Test
>  Components: tests
>Reporter: Andrei Savu
>Assignee: Andrei Savu
>
> Hadoop has a mechanism for doing fault injection (HDFS-435). I think it would 
> be useful if something similar would be available for ZooKeeper. 



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

[GitHub] zookeeper issue #123: ZOOKEEPER-1364: Add orthogonal fault injection mechani...

2016-12-14 Thread eribeiro

Github user eribeiro commented on the issue:

https://github.com/apache/zookeeper/pull/123
  
@yufeldman I really like your ZOOKEEPER-2549 patch, but I think it would be 
an awesome opportunity of introducing a much needed failure injection framework 
into ZooKeeper. So, I wrote this patch with your changes **as example** to see 
what is your opinion and if we could backport those changes to your PR or at 
least discuss the introduction of Byteman. IMHO, it would save a lot of changes 
due by ZK-2549, but I am really open to hear your opinion and concerns. Cheers! 
:smiley: 



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

ZooKeeper_branch35_jdk8 - Build # 334 - Still Failing

2016-12-14 Thread Apache Jenkins Server

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 450689 lines...]
[junit] at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[junit] at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[junit] at java.lang.Thread.run(Thread.java:745)
[junit] 2016-12-14 12:16:26,485 [myid:] - WARN  [New I/O boss 
#9966:ClientCnxnSocketNetty$ZKClientHandler@439] - Exception caught: [id: 
0x46b2613c] EXCEPTION: java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:11343
[junit] java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:11343
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:152)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
[junit] at 
org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
[junit] at 
org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
[junit] at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[junit] at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[junit] at java.lang.Thread.run(Thread.java:745)
[junit] 2016-12-14 12:16:26,485 [myid:] - INFO  [New I/O boss 
#9966:ClientCnxnSocketNetty@208] - channel is told closing
[junit] 2016-12-14 12:16:26,485 [myid:127.0.0.1:11343] - INFO  
[main-SendThread(127.0.0.1:11343):ClientCnxn$SendThread@1231] - channel for 
sessionid 0x1011ceed8cb is lost, closing socket connection and attempting 
reconnect
[junit] 2016-12-14 12:16:26,524 [myid:127.0.0.1:11349] - INFO  
[main-SendThread(127.0.0.1:11349):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:11349. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2016-12-14 12:16:26,524 [myid:] - INFO  [New I/O boss 
#10032:ClientCnxnSocketNetty$1@127] - future isn't success, cause: {}
[junit] java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:11349
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:152)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
[junit] at 
org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
[junit] at 
org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
[junit] at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[junit] at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[junit] at java.lang.Thread.run(Thread.java:745)
[junit] 2016-12-14 12:16:26,561 [myid:] - WARN  [New I/O boss 
#10032:ClientCnxnSocketNetty$ZKClientHandler@439] - Exception caught: [id: 
0x71c43be2] EXCEPTION: java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:11349
[junit] java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:11349
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:152)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)

ZooKeeper-trunk-jdk8 - Build # 856 - Still Failing

2016-12-14 Thread Apache Jenkins Server

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 494057 lines...]
[junit] 2016-12-14 11:58:25,621 [myid:127.0.0.1:11346] - WARN  
[main-SendThread(127.0.0.1:11346):ClientCnxn$SendThread@1235] - Session 
0x204027bce29 for server 127.0.0.1/127.0.0.1:11346, unexpected error, 
closing socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2016-12-14 11:58:26,337 [myid:127.0.0.1:11222] - INFO  
[main-SendThread(127.0.0.1:11222):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:11222. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2016-12-14 11:58:26,338 [myid:127.0.0.1:11222] - WARN  
[main-SendThread(127.0.0.1:11222):ClientCnxn$SendThread@1235] - Session 
0x104027670e6 for server 127.0.0.1/127.0.0.1:11222, unexpected error, 
closing socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2016-12-14 12:00:06,298 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 126467
[junit] 2016-12-14 12:00:06,298 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 55
[junit] 2016-12-14 12:00:06,298 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testManyChildWatchersAutoReset
[junit] 2016-12-14 12:00:06,299 [myid:] - INFO  [main:ClientBase@543] - 
tearDown starting
[junit] 2016-12-14 12:00:06,300 [myid:] - INFO  [ProcessThread(sid:0 
cport:24690)::PrepRequestProcessor@618] - Processed session termination for 
sessionid: 0x1040274a4ae
[junit] 2016-12-14 12:00:06,307 [myid:] - INFO  [main:ZooKeeper@1313] - 
Session: 0x1040274a4ae closed
[junit] 2016-12-14 12:00:06,307 [myid:] - INFO  
[NIOWorkerThread-7:MBeanRegistry@128] - Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port24690,name1=Connections,name2=127.0.0.1,name3=0x1040274a4ae]
[junit] 2016-12-14 12:00:06,307 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x1040274a4ae
[junit] 2016-12-14 12:00:06,307 [myid:] - INFO  [ProcessThread(sid:0 
cport:24690)::PrepRequestProcessor@618] - Processed session termination for 
sessionid: 0x1040274a4ae0001
[junit] 2016-12-14 12:00:06,308 [myid:] - INFO  
[NIOWorkerThread-7:NIOServerCnxn@607] - Closed socket connection for client 
/127.0.0.1:48600 which had sessionid 0x1040274a4ae
[junit] 2016-12-14 12:00:06,364 [myid:] - INFO  [main:ZooKeeper@1313] - 
Session: 0x1040274a4ae0001 closed
[junit] 2016-12-14 12:00:06,365 [myid:] - INFO  [main:ClientBase@513] - 
STOPPING server
[junit] 2016-12-14 12:00:06,364 [myid:] - INFO  
[NIOWorkerThread-16:MBeanRegistry@128] - Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port24690,name1=Connections,name2=127.0.0.1,name3=0x1040274a4ae0001]
[junit] 2016-12-14 12:00:06,365 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x1040274a4ae0001
[junit] 2016-12-14 12:00:06,366 [myid:] - INFO  
[ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - 
ConnnectionExpirerThread interrupted
[junit] 2016-12-14 12:00:06,371 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2016-12-14 12:00:06,370 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:24690:NIOServerCnxnFactory$AcceptThread@219]
 - accept thread exitted run method
[junit] 2016-12-14 12:00:06,366 [myid:] - INFO  
[NIOWorkerThread-16:NIOServerCnxn@607] - Closed socket connection for client 
/127.0.0.1:48636 which had sessionid 0x1040274a4ae0001
[junit] 2016-12-14 12:00:06,371 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2016-12-14 12:00:06,376 [myid:] - INFO  [main:ZooKeeperServer@534] 
- shutting down

ZooKeeper_branch35_openjdk7 - Build # 331 - Still Failing

2016-12-14 Thread Apache Jenkins Server

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

###
## LAST 60 LINES OF THE CONSOLE 
###
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H16 (ubuntu) in workspace 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_openjdk7
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url git://git.apache.org/zookeeper.git # timeout=10
Fetching upstream changes from git://git.apache.org/zookeeper.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > git://git.apache.org/zookeeper.git +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/branch-3.5^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/branch-3.5^{commit} # timeout=10
Checking out Revision e99c68316ecf19a1941fbf1290f11c4a65c1e268 
(refs/remotes/origin/branch-3.5)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f e99c68316ecf19a1941fbf1290f11c4a65c1e268
 > git rev-list e99c68316ecf19a1941fbf1290f11c4a65c1e268 # timeout=10
No emails were triggered.
[ZooKeeper_branch35_openjdk7] $ /home/jenkins/tools/ant/latest/bin/ant 
-Dtest.output=yes -Dtest.junit.threads=8 -Dtest.junit.output.format=xml 
-Djavac.target=1.7 clean test-core-java
Error: JAVA_HOME is not defined correctly.
  We cannot execute /usr/lib/jvm/java-7-openjdk-amd64//bin/java
Build step 'Invoke Ant' marked build as failure
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



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

ZooKeeper_branch35_jdk7 - Build # 766 - Still Failing

2016-12-14 Thread Apache Jenkins Server

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 431881 lines...]
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2016-12-14 08:52:24,160 [myid:] - WARN  [New I/O worker 
#6635:NettyServerCnxnFactory$CnxnChannelHandler@142] - Exception caught [id: 
0xb13bccae, /127.0.0.1:59145 :> /127.0.0.1:30317] EXCEPTION: 
java.nio.channels.ClosedChannelException
[junit] java.nio.channels.ClosedChannelException
[junit] at 
sun.nio.ch.SocketChannelImpl.ensureWriteOpen(SocketChannelImpl.java:270)
[junit] at 
sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:479)
[junit] at 
org.jboss.netty.channel.socket.nio.SocketSendBufferPool$UnpooledSendBuffer.transferTo(SocketSendBufferPool.java:203)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioWorker.write0(AbstractNioWorker.java:201)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioWorker.writeFromTaskLoop(AbstractNioWorker.java:151)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioChannel$WriteTask.run(AbstractNioChannel.java:315)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioSelector.processTaskQueue(AbstractNioSelector.java:391)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:315)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89)
[junit] at 
org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
[junit] at 
org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
[junit] at 
org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
[junit] at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[junit] at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[junit] at java.lang.Thread.run(Thread.java:745)
[junit] 2016-12-14 08:52:24,160 [myid:] - INFO  
[SyncThread:0:MBeanRegistry@128] - Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port30317,name1=Connections,name2=127.0.0.1,name3=0x10114121121]
[junit] 2016-12-14 08:52:24,170 [myid:127.0.0.1:30073] - INFO  
[main-SendThread(127.0.0.1:30073):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:30073. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2016-12-14 08:52:24,170 [myid:127.0.0.1:30073] - WARN  
[main-SendThread(127.0.0.1:30073):ClientCnxn$SendThread@1235] - Session 
0x101140a3653 for server 127.0.0.1/127.0.0.1:30073, unexpected error, 
closing socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2016-12-14 08:52:24,261 [myid:] - INFO  [main:ZooKeeper@1311] - 
Session: 0x10114121121 closed
[junit] 2016-12-14 08:52:24,261 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x10114121121
[junit] 2016-12-14 08:52:24,261 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 160162
[junit] 2016-12-14 08:52:24,261 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 1643
[junit] 2016-12-14 08:52:24,261 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testWatcherAutoResetWithLocal
[junit] 2016-12-14 08:52:24,261 [myid:] - INFO  [main:ClientBase@543] - 
tearDown starting
[junit] 2016-12-14 08:52:24,262 [myid:] - INFO  [main:ClientBase@513] - 
STOPPING server
[junit] 2016-12-14 08:52:24,262 [myid:] - INFO  
[main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:30317
[junit] 2016-12-14 08:52:24,268 [myid:] - INFO  [main:ZooKeeperServer@533] 
- shutting down
[junit] 2016-12-14 08:52:24,268 [myid:] - ERROR [main:ZooKeeperServer@505] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2016-12-14 08:52:24,268 [myid:] - INFO  
[main:SessionTrackerImpl@232] - Shutting down
[junit] 2016-12-14 08:52:24,268 [myid:] - INFO  
[main:PrepRequestProcessor@974] - Shutting down
[junit] 2016-12-14 08:52:24,268 [myid:] - INFO  
[main:SyncRequestProcessor@191] - Shutting down
[junit] 2016-12-14 08:52:24,269 [myid:]

[jira] [Created] (ZOOKEEPER-2645) If embedded QuorumPeerMain is started with Properties no backupOldConfig should be done

ZooKeeper-trunk-WinVS2008 - Build # 2360 - Still Failing

[GitHub] zookeeper pull request #119: ZOOKEEPER-2251:Add Client side packet response ...

[jira] [Commented] (ZOOKEEPER-2251) Add Client side packet response timeout to avoid infinite wait.

[jira] [Commented] (ZOOKEEPER-2470) ServerConfig#parse(String[]) ignores tickTime

[GitHub] zookeeper issue #125: ZOOKEEPER-2470: ServerConfig#parse(String[]) ignores t...

[jira] [Commented] (ZOOKEEPER-2470) ServerConfig#parse(String[]) ignores tickTime

[GitHub] zookeeper issue #125: ZOOKEEPER-2470: ServerConfig#parse(String[]) ignores t...

[jira] [Commented] (ZOOKEEPER-1364) Add orthogonal fault injection mechanism/framework

[GitHub] zookeeper issue #123: ZOOKEEPER-1364: Add orthogonal fault injection mechani...

ZooKeeper-trunk - Build # 3193 - Failure

[jira] [Commented] (ZOOKEEPER-2642) ZOOKEEPER-2014 breaks existing clients for little benefit

[GitHub] zookeeper pull request #122: [ZOOKEEPER-2642] Resurrect the reconfig() metho...

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

[jira] [Commented] (ZOOKEEPER-2470) ServerConfig#parse(String[]) ignores tickTime

[jira] [Assigned] (ZOOKEEPER-2470) ServerConfig#parse(String[]) ignores tickTime

Failed: ZOOKEEPER- PreCommit Build #120

[jira] [Commented] (ZOOKEEPER-2470) ServerConfig#parse(String[]) ignores tickTime

[GitHub] zookeeper pull request #125: ZOOKEEPER-2470: ServerConfig#parse(String[]) ig...

[jira] [Commented] (ZOOKEEPER-2251) Add Client side packet response timeout to avoid infinite wait.

Failed: ZOOKEEPER- PreCommit Build #119

[jira] [Commented] (ZOOKEEPER-2552) Revisit release note doc and remove the items which are not related to the released version

[GitHub] zookeeper pull request #124: ZOOKEEPER-2552: Revisit release doc and remove ...

ZooKeeper_branch35_solaris - Build # 351 - Still Failing

[jira] [Commented] (ZOOKEEPER-1364) Add orthogonal fault injection mechanism/framework

[GitHub] zookeeper issue #123: ZOOKEEPER-1364: Add orthogonal fault injection mechani...

[jira] [Commented] (ZOOKEEPER-1364) Add orthogonal fault injection mechanism/framework

[GitHub] zookeeper issue #123: ZOOKEEPER-1364: Add orthogonal fault injection mechani...

ZooKeeper_branch34_openjdk7 - Build # 1307 - Still Failing

ZooKeeper_branch34_solaris - Build # 1389 - Still Failing

[jira] [Commented] (ZOOKEEPER-1364) Add orthogonal fault injection mechanism/framework

[GitHub] zookeeper issue #123: ZOOKEEPER-1364: Add orthogonal fault injection mechani...

ZooKeeper_branch35_jdk8 - Build # 334 - Still Failing

ZooKeeper-trunk-jdk8 - Build # 856 - Still Failing

ZooKeeper_branch35_openjdk7 - Build # 331 - Still Failing

ZooKeeper_branch35_jdk7 - Build # 766 - Still Failing

36 matches

Site Navigation

Mail list logo

Footer information