[jira] [Commented] (ZOOKEEPER-1594) TestReconfig intermittently fails

2013-01-21 Thread Alexander Shraer (JIRA) 

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

Alexander Shraer commented on ZOOKEEPER-1594:
-

Marshall, I'm wondering if the bug has something to do with the following: when 
you create a client, the second parameter to the constructor determines the 
random seed used by the client. That second parameter I think is supposed to be 
the client's id, but what is passed is clients.size(). I might be wrong here 
but I don't see where this vector of clients is cleared in between tests, so is 
it true that at some point the set size is fixed and all the seeds are the same 
?

> TestReconfig intermittently fails
> -
>
> Key: ZOOKEEPER-1594
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1594
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: c client
>Affects Versions: 3.5.0
>Reporter: Marshall McMullen
>Assignee: Marshall McMullen
>
> We've seen an intermittent failure in one of the C client tests TestReconfig 
> which was committed as part of ZOOKEEPER-1355.
> The test that is failing is failing *before* any rebalancing algorithm is 
> invoked. After inspecting this we've concluded it is a failure to properly 
> seed the random number generator properly. This same problem was seen and 
> solved on the Java client side so we just need to do something similar on the 
> C client side.
> The assertion:
> Build/trunk/src/c/tests/TestReconfig.cc:571: Assertion: assertion failed 
> [Expression: numClientsPerHost.at(i) >= 
> lowerboundClientsPerServer(numClients, numServers)]
> [exec] [exec] Failures !!!
> [exec] [exec] Run: 38 Failure total: 1 Failures: 1 Errors: 0
> [exec] [exec] make: *** [run-check] Error 1
> [exec] 
> [exec] BUILD FAILED
> [exec] 
> /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1262:
>  The following error occurred while executing this line:
> [exec] 
> /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1272:
>  exec returned: 2

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (ZOOKEEPER-1625) zkServer.sh is looking for clientPort in config file, but it may no longer be there with ZK-1411

2013-01-21 Thread Alexander Shraer (JIRA) 

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

Alexander Shraer commented on ZOOKEEPER-1625:
-

The patch includes only changes to zkServer.sh. I manually verified that it 
finds the client port in static or dynamic config file or reports an error if 
the port is not found.

> zkServer.sh is looking for clientPort in config file, but it may no longer be 
> there with ZK-1411
> 
>
> Key: ZOOKEEPER-1625
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1625
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: scripts
>Affects Versions: 3.5.0
>Reporter: Alexander Shraer
>Assignee: Alexander Shraer
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1625.patch
>
>
> zkServer.sh is currently looking for "clientPort" entry in the static 
> configuration file and uses it to contact the server. 
> With ZOOKEEPER-1411 clientPort is part of the dynamic configuration, and may 
> appear in the separate dynamic configuration file. The "clientPort" entry may 
> no longer be in the static config file. 
> With the proposed patch zkServer.sh first looks in the old (static) config 
> file, then if clientPort is not there, it figures out the id of the server by 
> looking at myid file, and then using that id finds the client port in the 
> dynamic config file. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Failed: ZOOKEEPER-1625 PreCommit Build #1352

2013-01-21 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1625
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1352/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 24 lines...]
 [exec] 
 [exec] -1 overall.  Here are the results of testing the latest attachment 
 [exec]   
http://issues.apache.org/jira/secure/attachment/12565908/ZOOKEEPER-1625.patch
 [exec]   against trunk revision 1434978.
 [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 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 1.3.9) 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/1352//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1352//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1352//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] ae74f972faf69c858b159ef3877c7a4879b4c77d 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:1623:
 exec returned: 1

Total time: 28 minutes 5 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results
Description set: ZOOKEEPER-1625
Email was triggered for: Failure
Sending email for trigger: Failure



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

[jira] [Commented] (ZOOKEEPER-1625) zkServer.sh is looking for clientPort in config file, but it may no longer be there with ZK-1411

2013-01-21 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on ZOOKEEPER-1625:
--

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

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

This message is automatically generated.

> zkServer.sh is looking for clientPort in config file, but it may no longer be 
> there with ZK-1411
> 
>
> Key: ZOOKEEPER-1625
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1625
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: scripts
>Affects Versions: 3.5.0
>Reporter: Alexander Shraer
>Assignee: Alexander Shraer
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1625.patch
>
>
> zkServer.sh is currently looking for "clientPort" entry in the static 
> configuration file and uses it to contact the server. 
> With ZOOKEEPER-1411 clientPort is part of the dynamic configuration, and may 
> appear in the separate dynamic configuration file. The "clientPort" entry may 
> no longer be in the static config file. 
> With the proposed patch zkServer.sh first looks in the old (static) config 
> file, then if clientPort is not there, it figures out the id of the server by 
> looking at myid file, and then using that id finds the client port in the 
> dynamic config file. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (ZOOKEEPER-1625) zkServer.sh is looking for clientPort in config file, but it may no longer be there with ZK-1411

2013-01-21 Thread Alexander Shraer (JIRA) 

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

Alexander Shraer updated ZOOKEEPER-1625:


Component/s: (was: server)

> zkServer.sh is looking for clientPort in config file, but it may no longer be 
> there with ZK-1411
> 
>
> Key: ZOOKEEPER-1625
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1625
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: scripts
>Affects Versions: 3.5.0
>Reporter: Alexander Shraer
>Assignee: Alexander Shraer
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1625.patch
>
>
> zkServer.sh is currently looking for "clientPort" entry in the static 
> configuration file and uses it to contact the server. 
> With ZOOKEEPER-1411 clientPort is part of the dynamic configuration, and may 
> appear in the separate dynamic configuration file. The "clientPort" entry may 
> no longer be in the static config file. 
> With the proposed patch zkServer.sh first looks in the old (static) config 
> file, then if clientPort is not there, it figures out the id of the server by 
> looking at myid file, and then using that id finds the client port in the 
> dynamic config file. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (ZOOKEEPER-1625) zkServer.sh is looking for clientPort in config file, but it may no longer be there with ZK-1411

2013-01-21 Thread Alexander Shraer (JIRA) 

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

Alexander Shraer updated ZOOKEEPER-1625:


Description: 
zkServer.sh is currently looking for "clientPort" entry in the static 
configuration file and uses it to contact the server. 

With ZOOKEEPER-1411 clientPort is part of the dynamic configuration, and may 
appear in the separate dynamic configuration file. The "clientPort" entry may 
no longer be in the static config file. 

With the proposed patch zkServer.sh first looks in the old (static) config 
file, then if clientPort is not there, it figures out the id of the server by 
looking at myid file, and then using that id finds the client port in the 
dynamic config file. 

  was:
With ZOOKEEPER-1411 clientPort is part of the dynamic configuration, and may 
appear in the separate dynamic configuration file. zkServer.sh is looking for 
"clientPort" only in the static configuration file and uses it to contact the 
server.

There are several alternatives to fix this:

1. add a parameter to zkServer.sh similarly to the parameter of zkCli.sh (for 
example -server 127.0.0.1:2792)

2. Have zkServer.sh first look in the old config file, then if clientPort is 
not there, it should figure out the id of the server by looking at myid file, 
and then using that id find the client port in the dynamic config file. 

3. Always have clientPort in the static config file. If the client port changes 
in a reconfiguration, update clientPort in the static config file in addition 
to updating the dynamic config file. This would require changes to 1411 and 
107, while the scripts would remain the same. This is a bit ugly since it 
requires updating the port in two files and breaks the separation of static and 
dynamic configs in 1411.


I'd prefer the easiest option - 1, but not sure if there are any implications 
on the people using zkServer.sh


> zkServer.sh is looking for clientPort in config file, but it may no longer be 
> there with ZK-1411
> 
>
> Key: ZOOKEEPER-1625
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1625
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: scripts, server
>Affects Versions: 3.5.0
>Reporter: Alexander Shraer
>Assignee: Alexander Shraer
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1625.patch
>
>
> zkServer.sh is currently looking for "clientPort" entry in the static 
> configuration file and uses it to contact the server. 
> With ZOOKEEPER-1411 clientPort is part of the dynamic configuration, and may 
> appear in the separate dynamic configuration file. The "clientPort" entry may 
> no longer be in the static config file. 
> With the proposed patch zkServer.sh first looks in the old (static) config 
> file, then if clientPort is not there, it figures out the id of the server by 
> looking at myid file, and then using that id finds the client port in the 
> dynamic config file. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (ZOOKEEPER-1625) zkServer.sh is looking for clientPort in config file, but it may no longer be there with ZK-1411

2013-01-21 Thread Alexander Shraer (JIRA) 

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

Alexander Shraer reassigned ZOOKEEPER-1625:
---

Assignee: Alexander Shraer

> zkServer.sh is looking for clientPort in config file, but it may no longer be 
> there with ZK-1411
> 
>
> Key: ZOOKEEPER-1625
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1625
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: scripts, server
>Affects Versions: 3.5.0
>Reporter: Alexander Shraer
>Assignee: Alexander Shraer
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1625.patch
>
>
> With ZOOKEEPER-1411 clientPort is part of the dynamic configuration, and may 
> appear in the separate dynamic configuration file. zkServer.sh is looking for 
> "clientPort" only in the static configuration file and uses it to contact the 
> server.
> There are several alternatives to fix this:
> 1. add a parameter to zkServer.sh similarly to the parameter of zkCli.sh (for 
> example -server 127.0.0.1:2792)
> 2. Have zkServer.sh first look in the old config file, then if clientPort is 
> not there, it should figure out the id of the server by looking at myid file, 
> and then using that id find the client port in the dynamic config file. 
> 3. Always have clientPort in the static config file. If the client port 
> changes in a reconfiguration, update clientPort in the static config file in 
> addition to updating the dynamic config file. This would require changes to 
> 1411 and 107, while the scripts would remain the same. This is a bit ugly 
> since it requires updating the port in two files and breaks the separation of 
> static and dynamic configs in 1411.
> I'd prefer the easiest option - 1, but not sure if there are any implications 
> on the people using zkServer.sh

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (ZOOKEEPER-1625) zkServer.sh is looking for clientPort in config file, but it may no longer be there with ZK-1411

2013-01-21 Thread Alexander Shraer (JIRA) 

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

Alexander Shraer updated ZOOKEEPER-1625:


Attachment: ZOOKEEPER-1625.patch

> zkServer.sh is looking for clientPort in config file, but it may no longer be 
> there with ZK-1411
> 
>
> Key: ZOOKEEPER-1625
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1625
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: scripts, server
>Affects Versions: 3.5.0
>Reporter: Alexander Shraer
>Assignee: Alexander Shraer
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1625.patch
>
>
> With ZOOKEEPER-1411 clientPort is part of the dynamic configuration, and may 
> appear in the separate dynamic configuration file. zkServer.sh is looking for 
> "clientPort" only in the static configuration file and uses it to contact the 
> server.
> There are several alternatives to fix this:
> 1. add a parameter to zkServer.sh similarly to the parameter of zkCli.sh (for 
> example -server 127.0.0.1:2792)
> 2. Have zkServer.sh first look in the old config file, then if clientPort is 
> not there, it should figure out the id of the server by looking at myid file, 
> and then using that id find the client port in the dynamic config file. 
> 3. Always have clientPort in the static config file. If the client port 
> changes in a reconfiguration, update clientPort in the static config file in 
> addition to updating the dynamic config file. This would require changes to 
> 1411 and 107, while the scripts would remain the same. This is a bit ugly 
> since it requires updating the port in two files and breaks the separation of 
> static and dynamic configs in 1411.
> I'd prefer the easiest option - 1, but not sure if there are any implications 
> on the people using zkServer.sh

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (ZOOKEEPER-107) Allow dynamic changes to server cluster membership

2013-01-21 Thread Marshall McMullen (JIRA) 

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

Marshall McMullen commented on ZOOKEEPER-107:
-

Awesome job Alex and Michi. Sorry I couldn't have helped with this one but way 
too much on my plate right now. Will definitely review the patch and offer 
suggestions where I can.

> Allow dynamic changes to server cluster membership
> --
>
> Key: ZOOKEEPER-107
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-107
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: server
>Reporter: Patrick Hunt
>Assignee: Alexander Shraer
> Fix For: 3.5.0
>
> Attachments: SimpleAddition.rtf, zkreconfig-usenixatc-final.pdf, 
> ZOOKEEPER-107-14-Jan.patch, ZOOKEEPER-107-14-Oct.patch, 
> ZOOKEEPER-107-15-Oct.patch, ZOOKEEPER-107-15-Oct-ver1.patch, 
> ZOOKEEPER-107-15-Oct-ver2.patch, ZOOKEEPER-107-15-Oct-ver3.patch, 
> ZOOKEEPER-107-16-Jan.patch, ZOOKEEPER-107-17-Jan.patch, 
> ZOOKEEPER-107-18-Jan.patch, ZOOKEEPER-107-18-Jan-ver2.patch, 
> ZOOKEEPER-107-1-Mar.patch, ZOOKEEPER-107-20-Jan.patch, 
> ZOOKEEPER-107-20-July.patch, ZOOKEEPER-107-21-July.patch, 
> ZOOKEEPER-107-22-Apr.patch, ZOOKEEPER-107-23-SEP.patch, 
> ZOOKEEPER-107-28-Feb.patch, ZOOKEEPER-107-28-Feb.patch, 
> ZOOKEEPER-107-28-NOV-ver2.patch, ZOOKEEPER-107-29-Feb.patch, 
> ZOOKEEPER-107-3-Oct.patch, ZOOKEEPER-107-6-NOV-2.patch, 
> ZOOKEEPER-107-7-NOV.patch, ZOOKEEPER-107-7-NOV-ver1.patch, 
> ZOOKEEPER-107-7-NOV-ver2.patch, ZOOKEEPER-107-Aug-20.patch, 
> ZOOKEEPER-107-Aug-20-ver1.patch, ZOOKEEPER-107-Aug-25.patch, 
> zookeeper-3.4.0.jar, zookeeper-dev-fatjar.jar, 
> zookeeper-reconfig-sep11.patch, zookeeper-reconfig-sep12.patch, 
> zoo_replicated1.cfg, zoo_replicated1.members
>
>
> Currently cluster membership is statically defined, adding/removing hosts 
> to/from the server cluster dynamically needs to be supported.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (ZOOKEEPER-107) Allow dynamic changes to server cluster membership

2013-01-21 Thread Michi Mutsuzaki (JIRA) 

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

Michi Mutsuzaki commented on ZOOKEEPER-107:
---

Alex and I worked on writing C tests for this. We have working skeleton. I'll 
clean up the patch, and post it here some time this week. 

--Michi

> Allow dynamic changes to server cluster membership
> --
>
> Key: ZOOKEEPER-107
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-107
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: server
>Reporter: Patrick Hunt
>Assignee: Alexander Shraer
> Fix For: 3.5.0
>
> Attachments: SimpleAddition.rtf, zkreconfig-usenixatc-final.pdf, 
> ZOOKEEPER-107-14-Jan.patch, ZOOKEEPER-107-14-Oct.patch, 
> ZOOKEEPER-107-15-Oct.patch, ZOOKEEPER-107-15-Oct-ver1.patch, 
> ZOOKEEPER-107-15-Oct-ver2.patch, ZOOKEEPER-107-15-Oct-ver3.patch, 
> ZOOKEEPER-107-16-Jan.patch, ZOOKEEPER-107-17-Jan.patch, 
> ZOOKEEPER-107-18-Jan.patch, ZOOKEEPER-107-18-Jan-ver2.patch, 
> ZOOKEEPER-107-1-Mar.patch, ZOOKEEPER-107-20-Jan.patch, 
> ZOOKEEPER-107-20-July.patch, ZOOKEEPER-107-21-July.patch, 
> ZOOKEEPER-107-22-Apr.patch, ZOOKEEPER-107-23-SEP.patch, 
> ZOOKEEPER-107-28-Feb.patch, ZOOKEEPER-107-28-Feb.patch, 
> ZOOKEEPER-107-28-NOV-ver2.patch, ZOOKEEPER-107-29-Feb.patch, 
> ZOOKEEPER-107-3-Oct.patch, ZOOKEEPER-107-6-NOV-2.patch, 
> ZOOKEEPER-107-7-NOV.patch, ZOOKEEPER-107-7-NOV-ver1.patch, 
> ZOOKEEPER-107-7-NOV-ver2.patch, ZOOKEEPER-107-Aug-20.patch, 
> ZOOKEEPER-107-Aug-20-ver1.patch, ZOOKEEPER-107-Aug-25.patch, 
> zookeeper-3.4.0.jar, zookeeper-dev-fatjar.jar, 
> zookeeper-reconfig-sep11.patch, zookeeper-reconfig-sep12.patch, 
> zoo_replicated1.cfg, zoo_replicated1.members
>
>
> Currently cluster membership is statically defined, adding/removing hosts 
> to/from the server cluster dynamically needs to be supported.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (ZOOKEEPER-1626) Zookeeper C client should be tolerant of clock adjustments

2013-01-21 Thread Patrick Hunt (JIRA) 

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

Patrick Hunt updated ZOOKEEPER-1626:


Assignee: Colin Patrick McCabe

> Zookeeper C client should be tolerant of clock adjustments 
> ---
>
> Key: ZOOKEEPER-1626
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1626
> Project: ZooKeeper
>  Issue Type: Sub-task
>Reporter: Colin Patrick McCabe
>Assignee: Colin Patrick McCabe
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1366.001.patch
>
>
> The Zookeeper C client should use monotonic time when available, in order to 
> be more tolerant of time adjustments.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Success: ZOOKEEPER-1379 PreCommit Build #1351

2013-01-21 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1379
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1351/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 265606 lines...]
 [exec] BUILD SUCCESSFUL
 [exec] Total time: 0 seconds
 [exec] 
 [exec] 
 [exec] 
 [exec] 
 [exec] +1 overall.  Here are the results of testing the latest attachment 
 [exec]   
http://issues.apache.org/jira/secure/attachment/12565863/ZOOKEEPER-1379.2.patch
 [exec]   against trunk revision 1434978.
 [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 1.3.9) 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/1351//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1351//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1351//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] daf0bf90793ff59d2fde77286f60258a0e57eb9f logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 

BUILD SUCCESSFUL
Total time: 28 minutes 8 seconds
Archiving artifacts
Recording test results
Description set: ZOOKEEPER-1379
Email was triggered for: Success
Sending email for trigger: Success



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

[jira] [Commented] (ZOOKEEPER-1379) 'printwatches, redo, history and connect '. client commands always print usage. This is not necessary

2013-01-21 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on ZOOKEEPER-1379:
--

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

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

This message is automatically generated.

> 'printwatches, redo, history and connect '. client commands always print 
> usage. This is not necessary
> -
>
> Key: ZOOKEEPER-1379
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1379
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: java client
>Affects Versions: 3.4.0, 3.5.0
>Reporter: kavita sharma
>Assignee: Edward Ribeiro
>Priority: Minor
> Fix For: 3.5.0, 3.4.6
>
> Attachments: ZOOKEEPER-1379.2.patch, ZOOKEEPER-1379.patch
>
>
> while executing the commands:
> 'printwatches, redo, history and connect usage is getting print 
> .basically we are printing usage if user has entered the command 
> wrong but in these commands case every time usage is getting print.
> eg
> {noformat}
> [zk: localhost:2181(CONNECTED) 0] printwatches
> printwatches is on
> ZooKeeper -server host:port cmd args
>   connect host:port
>   get path [watch]
>   ls path [watch]
>   set path data [version]
>   delquota [-n|-b] path
>   quit 
>   printwatches on|off
>   create [-s] [-e] path data acl
>   stat path [watch]
>   close 
>   ls2 path [watch]
>   history 
>   listquota path
>   setAcl path acl
>   getAcl path
>   sync path
>   redo cmdno
>   addauth scheme auth
>   delete path [version]
>   setquota -n|-b val path
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Review Request: Dynamic reconfiguration, see https://issues.apache.org/jira/browse/ZOOKEEPER-107

2013-01-21 Thread Alexander Shraer 


> On Dec. 16, 2012, 6:19 a.m., michim wrote:
> >

all comments are now addressed.


- Alexander


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/6707/#review13756
---


On Nov. 29, 2012, 7:12 a.m., Alexander Shraer wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/6707/
> ---
> 
> (Updated Nov. 29, 2012, 7:12 a.m.)
> 
> 
> Review request for zookeeper.
> 
> 
> Description
> ---
> 
> see https://issues.apache.org/jira/browse/ZOOKEEPER-107
> 
> 
> Diffs
> -
> 
>   /src/c/include/proto.h 1415037 
>   /src/c/include/zookeeper.h 1415037 
>   /src/c/src/cli.c 1415037 
>   /src/c/src/zookeeper.c 1415037 
>   /src/java/main/org/apache/zookeeper/KeeperException.java 1415037 
>   /src/java/main/org/apache/zookeeper/ZooDefs.java 1415037 
>   /src/java/main/org/apache/zookeeper/ZooKeeper.java 1415037 
>   /src/java/main/org/apache/zookeeper/ZooKeeperMain.java 1415037 
>   /src/java/main/org/apache/zookeeper/cli/GetConfigCommand.java PRE-CREATION 
>   /src/java/main/org/apache/zookeeper/cli/ReconfigCommand.java PRE-CREATION 
>   /src/java/main/org/apache/zookeeper/server/DataTree.java 1415037 
>   /src/java/main/org/apache/zookeeper/server/FinalRequestProcessor.java 
> 1415037 
>   /src/java/main/org/apache/zookeeper/server/NIOServerCnxnFactory.java 
> 1415037 
>   /src/java/main/org/apache/zookeeper/server/NettyServerCnxnFactory.java 
> 1415037 
>   /src/java/main/org/apache/zookeeper/server/PrepRequestProcessor.java 
> 1415037 
>   /src/java/main/org/apache/zookeeper/server/Request.java 1415037 
>   /src/java/main/org/apache/zookeeper/server/ServerCnxnFactory.java 1415037 
>   /src/java/main/org/apache/zookeeper/server/TraceFormatter.java 1415037 
>   /src/java/main/org/apache/zookeeper/server/quorum/CommitProcessor.java 
> 1415037 
>   /src/java/main/org/apache/zookeeper/server/quorum/FastLeaderElection.java 
> 1415037 
>   /src/java/main/org/apache/zookeeper/server/quorum/Follower.java 1415037 
>   
> /src/java/main/org/apache/zookeeper/server/quorum/FollowerRequestProcessor.java
>  1415037 
>   /src/java/main/org/apache/zookeeper/server/quorum/Leader.java 1415037 
>   /src/java/main/org/apache/zookeeper/server/quorum/Learner.java 1415037 
>   /src/java/main/org/apache/zookeeper/server/quorum/LearnerHandler.java 
> 1415037 
>   /src/java/main/org/apache/zookeeper/server/quorum/Observer.java 1415037 
>   
> /src/java/main/org/apache/zookeeper/server/quorum/ObserverRequestProcessor.java
>  1415037 
>   /src/java/main/org/apache/zookeeper/server/quorum/QuorumBean.java 1415037 
>   /src/java/main/org/apache/zookeeper/server/quorum/QuorumCnxManager.java 
> 1415037 
>   /src/java/main/org/apache/zookeeper/server/quorum/QuorumPeer.java 1415037 
>   /src/java/main/org/apache/zookeeper/server/quorum/QuorumPeerConfig.java 
> 1415037 
>   /src/java/main/org/apache/zookeeper/server/quorum/QuorumPeerMain.java 
> 1415037 
>   
> /src/java/main/org/apache/zookeeper/server/quorum/QuorumZooKeeperServer.java 
> 1415037 
>   
> /src/java/main/org/apache/zookeeper/server/quorum/ReadOnlyRequestProcessor.java
>  1415037 
>   
> /src/java/main/org/apache/zookeeper/server/quorum/flexible/QuorumHierarchical.java
>  1415037 
>   /src/java/main/org/apache/zookeeper/server/quorum/flexible/QuorumMaj.java 
> 1415037 
>   
> /src/java/main/org/apache/zookeeper/server/quorum/flexible/QuorumVerifier.java
>  1415037 
>   /src/java/main/org/apache/zookeeper/server/util/ConfigUtils.java 
> PRE-CREATION 
>   /src/java/main/org/apache/zookeeper/server/util/SerializeUtils.java 1415037 
>   /src/java/test/org/apache/zookeeper/server/TruncateCorruptionTest.java 
> 1415037 
>   /src/java/test/org/apache/zookeeper/server/quorum/QuorumPeerTestBase.java 
> 1415037 
>   /src/java/test/org/apache/zookeeper/server/quorum/ReconfigRecoveryTest.java 
> PRE-CREATION 
>   /src/java/test/org/apache/zookeeper/server/quorum/Zab1_0Test.java 1415037 
>   /src/java/test/org/apache/zookeeper/test/CnxManagerTest.java 1415037 
>   /src/java/test/org/apache/zookeeper/test/QuorumMajorityTest.java 
> PRE-CREATION 
>   /src/java/test/org/apache/zookeeper/test/QuorumUtil.java 1415037 
>   /src/java/test/org/apache/zookeeper/test/ReconfigTest.java PRE-CREATION 
>   /src/zookeeper.jute 1415037 
> 
> Diff: https://reviews.apache.org/r/6707/diff/
> 
> 
> Testing
> ---
> 
> New test files were added: ReconfigTest, ReconfigRecoveryTest and 
> QuorumMajorityTest. Many other tests were modified. 
> 
> 
> Thanks,
> 
> Alexander Shraer
> 
>

[jira] [Updated] (ZOOKEEPER-1379) 'printwatches, redo, history and connect '. client commands always print usage. This is not necessary

2013-01-21 Thread Edward Ribeiro (JIRA) 

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

Edward Ribeiro updated ZOOKEEPER-1379:
--

Affects Version/s: 3.5.0

> 'printwatches, redo, history and connect '. client commands always print 
> usage. This is not necessary
> -
>
> Key: ZOOKEEPER-1379
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1379
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: java client
>Affects Versions: 3.4.0, 3.5.0
>Reporter: kavita sharma
>Assignee: kavita sharma
>Priority: Minor
> Attachments: ZOOKEEPER-1379.2.patch, ZOOKEEPER-1379.patch
>
>
> while executing the commands:
> 'printwatches, redo, history and connect usage is getting print 
> .basically we are printing usage if user has entered the command 
> wrong but in these commands case every time usage is getting print.
> eg
> {noformat}
> [zk: localhost:2181(CONNECTED) 0] printwatches
> printwatches is on
> ZooKeeper -server host:port cmd args
>   connect host:port
>   get path [watch]
>   ls path [watch]
>   set path data [version]
>   delquota [-n|-b] path
>   quit 
>   printwatches on|off
>   create [-s] [-e] path data acl
>   stat path [watch]
>   close 
>   ls2 path [watch]
>   history 
>   listquota path
>   setAcl path acl
>   getAcl path
>   sync path
>   redo cmdno
>   addauth scheme auth
>   delete path [version]
>   setquota -n|-b val path
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (ZOOKEEPER-1379) 'printwatches, redo, history and connect '. client commands always print usage. This is not necessary

2013-01-21 Thread Edward Ribeiro (JIRA) 

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

Edward Ribeiro updated ZOOKEEPER-1379:
--

Attachment: ZOOKEEPER-1379.2.patch

Attaching a new version of this patch (with a simple test).

> 'printwatches, redo, history and connect '. client commands always print 
> usage. This is not necessary
> -
>
> Key: ZOOKEEPER-1379
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1379
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: java client
>Affects Versions: 3.4.0
>Reporter: kavita sharma
>Assignee: kavita sharma
>Priority: Minor
> Attachments: ZOOKEEPER-1379.2.patch, ZOOKEEPER-1379.patch
>
>
> while executing the commands:
> 'printwatches, redo, history and connect usage is getting print 
> .basically we are printing usage if user has entered the command 
> wrong but in these commands case every time usage is getting print.
> eg
> {noformat}
> [zk: localhost:2181(CONNECTED) 0] printwatches
> printwatches is on
> ZooKeeper -server host:port cmd args
>   connect host:port
>   get path [watch]
>   ls path [watch]
>   set path data [version]
>   delquota [-n|-b] path
>   quit 
>   printwatches on|off
>   create [-s] [-e] path data acl
>   stat path [watch]
>   close 
>   ls2 path [watch]
>   history 
>   listquota path
>   setAcl path acl
>   getAcl path
>   sync path
>   redo cmdno
>   addauth scheme auth
>   delete path [version]
>   setquota -n|-b val path
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Success: ZOOKEEPER-1613 PreCommit Build #1350

2013-01-21 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1613
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1350/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 261648 lines...]
 [exec] BUILD SUCCESSFUL
 [exec] Total time: 0 seconds
 [exec] 
 [exec] 
 [exec] 
 [exec] 
 [exec] +1 overall.  Here are the results of testing the latest attachment 
 [exec]   
http://issues.apache.org/jira/secure/attachment/12562738/ZOOKEEPER-1613.patch
 [exec]   against trunk revision 1434978.
 [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 1.3.9) 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/1350//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1350//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1350//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] 601e58fab794782c22cf6c0c3a1fc30923e48b42 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 

BUILD SUCCESSFUL
Total time: 28 minutes 5 seconds
Archiving artifacts
Recording test results
Description set: ZOOKEEPER-1613
Email was triggered for: Success
Sending email for trigger: Success



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

[jira] [Commented] (ZOOKEEPER-1613) The documentation still points to 2008 in the copyright notice

2013-01-21 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on ZOOKEEPER-1613:
--

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

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

This message is automatically generated.

> The documentation still points to 2008 in the copyright notice
> --
>
> Key: ZOOKEEPER-1613
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1613
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 3.4.5
>Reporter: Edward Ribeiro
>Assignee: Edward Ribeiro
>Priority: Trivial
>  Labels: newbie
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1613.patch
>
>
> While fiddling with docbook to solve the broken links of ZOOKEEPER-1488 I 
> noted that all the documentation's copyright notice still has the year 2008 
> only. I am submitting a patch a fix this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (ZOOKEEPER-1346) Handle 4lws and monitoring on separate port

2013-01-21 Thread Edward Ribeiro (JIRA) 

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

Edward Ribeiro commented on ZOOKEEPER-1346:
---

Very nice. Congratulations, Skye.

Do you mind to close the two review issues I opened at 
https://reviews.apache.org/r/8094/ as done, please? Just mark them as checked, 
because your patch is ready to ship, imo. :)


> Handle 4lws and monitoring on separate port
> ---
>
> Key: ZOOKEEPER-1346
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1346
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: server
>Reporter: Camille Fournier
>Assignee: Skye Wanderman-Milne
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1346.2.patch, ZOOKEEPER-1346.3.patch, 
> ZOOKEEPER-1346.4.patch, ZOOKEEPER-1346.6.patch, ZOOKEEPER-1346.7.patch, 
> ZOOKEEPER-1346.8.patch, ZOOKEEPER-1346_jetty.patch, ZOOKEEPER-1346.patch
>
>
> Move the 4lws to their own port, off of the client port, and support them 
> properly via long-lived sessions instead of polling. Deprecate the 4lw 
> support on the client port. Will enable us to enhance the functionality of 
> the commands via extended command syntax, address security concerns and fix 
> bugs involving the socket close being received before all of the data on the 
> client end.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Failed: ZOOKEEPER-1626 PreCommit Build #1349

2013-01-21 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1626
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1349/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 268314 lines...]
 [exec] 
 [exec] -1 overall.  Here are the results of testing the latest attachment 
 [exec]   
http://issues.apache.org/jira/secure/attachment/12565828/ZOOKEEPER-1366.001.patch
 [exec]   against trunk revision 1434978.
 [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 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 1.3.9) 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/1349//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1349//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1349//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] 4f289bd306b3ac18fea9383df570e7e9230574e8 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:1623:
 exec returned: 2

Total time: 25 minutes 50 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results
Description set: ZOOKEEPER-1626
Email was triggered for: Failure
Sending email for trigger: Failure



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

[jira] [Commented] (ZOOKEEPER-1626) Zookeeper C client should be tolerant of clock adjustments

2013-01-21 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on ZOOKEEPER-1626:
--

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

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

This message is automatically generated.

> Zookeeper C client should be tolerant of clock adjustments 
> ---
>
> Key: ZOOKEEPER-1626
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1626
> Project: ZooKeeper
>  Issue Type: Sub-task
>Reporter: Colin Patrick McCabe
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1366.001.patch
>
>
> The Zookeeper C client should use monotonic time when available, in order to 
> be more tolerant of time adjustments.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (ZOOKEEPER-1366) Zookeeper should be tolerant of clock adjustments

2013-01-21 Thread Colin Patrick McCabe (JIRA) 

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

Colin Patrick McCabe commented on ZOOKEEPER-1366:
-

bq. I think there are changes in the C client that should be made as well to 
make it more resilent to clock adjustments as well. Doesn't look like any of 
those were accounted for under this patch.

I filed ZOOKEEPER-1626 to deal with the C client changes.

> Zookeeper should be tolerant of clock adjustments
> -
>
> Key: ZOOKEEPER-1366
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1366
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Ted Dunning
>Assignee: Ted Dunning
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1366-3.3.3.patch, ZOOKEEPER-1366.patch, 
> ZOOKEEPER-1366.patch, ZOOKEEPER-1366.patch, ZOOKEEPER-1366.patch
>
>
> If you want to wreak havoc on a ZK based system just do [date -s "+1hour"] 
> and watch the mayhem as all sessions expire at once.
> This shouldn't happen.  Zookeeper could easily know handle elapsed times as 
> elapsed times rather than as differences between absolute times.  The 
> absolute times are subject to adjustment when the clock is set while a timer 
> is not subject to this problem.  In Java, System.currentTimeMillis() gives 
> you absolute time while System.nanoTime() gives you time based on a timer 
> from an arbitrary epoch.
> I have done this and have been running tests now for some tens of minutes 
> with no failures.  I will set up a test machine to redo the build again on 
> Ubuntu and post a patch here for discussion.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (ZOOKEEPER-1626) Zookeeper C client should be tolerant of clock adjustments

2013-01-21 Thread Colin Patrick McCabe (JIRA) 

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

Colin Patrick McCabe commented on ZOOKEEPER-1626:
-

To test this, I ran a single instance of {{QuorumPeerMain}} and verified that I 
could do some things from the (C-based) Zookeeper client shell.

> Zookeeper C client should be tolerant of clock adjustments 
> ---
>
> Key: ZOOKEEPER-1626
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1626
> Project: ZooKeeper
>  Issue Type: Sub-task
>Reporter: Colin Patrick McCabe
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1366.001.patch
>
>
> The Zookeeper C client should use monotonic time when available, in order to 
> be more tolerant of time adjustments.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (ZOOKEEPER-1626) Zookeeper C client should be tolerant of clock adjustments

2013-01-21 Thread Colin Patrick McCabe (JIRA) 

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

Colin Patrick McCabe updated ZOOKEEPER-1626:


Attachment: ZOOKEEPER-1366.001.patch

> Zookeeper C client should be tolerant of clock adjustments 
> ---
>
> Key: ZOOKEEPER-1626
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1626
> Project: ZooKeeper
>  Issue Type: Sub-task
>Reporter: Colin Patrick McCabe
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1366.001.patch
>
>
> The Zookeeper C client should use monotonic time when available, in order to 
> be more tolerant of time adjustments.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (ZOOKEEPER-1626) Zookeeper C client should be tolerant of clock adjustments

2013-01-21 Thread Colin Patrick McCabe (JIRA) 
Colin Patrick McCabe created ZOOKEEPER-1626:
---

 Summary: Zookeeper C client should be tolerant of clock 
adjustments 
 Key: ZOOKEEPER-1626
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1626
 Project: ZooKeeper
  Issue Type: Sub-task
Reporter: Colin Patrick McCabe
 Attachments: ZOOKEEPER-1366.001.patch

The Zookeeper C client should use monotonic time when available, in order to be 
more tolerant of time adjustments.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Subscribe

2013-01-21 Thread jferic 
New coming user, need to know the dev status of zookeeper.
 
eric.chenjf
2013.1.19

Re: Review Request: ZOOKEEPER-1346: Handle 4lws and monitoring on separate port (creating jetty server)

2013-01-21 Thread Edward Ribeiro 


> On Jan. 17, 2013, 11:53 p.m., Edward Ribeiro wrote:
> > src/java/test/org/apache/zookeeper/server/admin/JettyAdminServerTest.java, 
> > line 1
> > 
> >
> > Add Apache license (Jenkins alert).

Skye has just added the license. It's okay to close this review now.


- Edward


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/8094/#review15475
---


On Jan. 17, 2013, 2:01 a.m., Skye Wanderman-Milne wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/8094/
> ---
> 
> (Updated Jan. 17, 2013, 2:01 a.m.)
> 
> 
> Review request for zookeeper, Patrick Hunt, Camille Fournier, and Henry 
> Robinson.
> 
> 
> Description
> ---
> 
> See my comment in ZOOKEEPER-1346.
> 
> 
> This addresses bug ZOOKEEPER-1346.
> https://issues.apache.org/jira/browse/ZOOKEEPER-1346
> 
> 
> Diffs
> -
> 
>   docs/zookeeperAdmin.html bc2b331 
>   docs/zookeeperAdmin.pdf ed595d2 
>   ivy.xml fadf4f4 
>   src/docs/src/documentation/content/xdocs/zookeeperAdmin.xml 47190a8 
>   src/java/main/org/apache/zookeeper/server/DataTree.java d6c7773 
>   src/java/main/org/apache/zookeeper/server/ExpiryQueue.java 130c58e 
>   src/java/main/org/apache/zookeeper/server/NIOServerCnxnFactory.java 9422538 
>   src/java/main/org/apache/zookeeper/server/NettyServerCnxnFactory.java 
> eec2f2a 
>   src/java/main/org/apache/zookeeper/server/ServerCnxn.java 35ea301 
>   src/java/main/org/apache/zookeeper/server/ServerCnxnFactory.java 267dbdf 
>   src/java/main/org/apache/zookeeper/server/ServerStats.java aa0d93f 
>   src/java/main/org/apache/zookeeper/server/SessionTracker.java 3535e1b 
>   src/java/main/org/apache/zookeeper/server/SessionTrackerImpl.java 137862e 
>   src/java/main/org/apache/zookeeper/server/WatchManager.java 0e7c815 
>   src/java/main/org/apache/zookeeper/server/ZKDatabase.java d6c0c05 
>   src/java/main/org/apache/zookeeper/server/ZooKeeperServer.java 14e754b 
>   src/java/main/org/apache/zookeeper/server/ZooKeeperServerMain.java 369e621 
>   src/java/main/org/apache/zookeeper/server/ZooTrace.java ac14fe2 
>   src/java/main/org/apache/zookeeper/server/admin/AdminServer.java 
> PRE-CREATION 
>   src/java/main/org/apache/zookeeper/server/admin/AdminServerFactory.java 
> PRE-CREATION 
>   src/java/main/org/apache/zookeeper/server/admin/Command.java PRE-CREATION 
>   src/java/main/org/apache/zookeeper/server/admin/CommandBase.java 
> PRE-CREATION 
>   src/java/main/org/apache/zookeeper/server/admin/CommandOutputter.java 
> PRE-CREATION 
>   src/java/main/org/apache/zookeeper/server/admin/Commands.java PRE-CREATION 
>   src/java/main/org/apache/zookeeper/server/admin/DummyAdminServer.java 
> PRE-CREATION 
>   src/java/main/org/apache/zookeeper/server/admin/JettyAdminServer.java 
> PRE-CREATION 
>   src/java/main/org/apache/zookeeper/server/admin/JsonOutputter.java 
> PRE-CREATION 
>   src/java/main/org/apache/zookeeper/server/quorum/Leader.java 87ebd7b 
>   src/java/main/org/apache/zookeeper/server/quorum/Learner.java e8d548b 
>   src/java/main/org/apache/zookeeper/server/quorum/LearnerSessionTracker.java 
> 3182419 
>   src/java/main/org/apache/zookeeper/server/quorum/QuorumPeer.java 9c17f5e 
>   src/java/main/org/apache/zookeeper/server/quorum/QuorumPeerMain.java 
> deae926 
>   
> src/java/main/org/apache/zookeeper/server/quorum/ReadOnlyZooKeeperServer.java 
> d3f1492 
>   src/java/test/org/apache/zookeeper/ZKTestCase.java 6ecfe8f 
>   src/java/test/org/apache/zookeeper/server/PrepRequestProcessorTest.java 
> 8665bac 
>   src/java/test/org/apache/zookeeper/server/admin/CommandsTest.java 
> PRE-CREATION 
>   src/java/test/org/apache/zookeeper/server/admin/JettyAdminServerTest.java 
> PRE-CREATION 
>   src/java/test/org/apache/zookeeper/server/quorum/QuorumPeerMainTest.java 
> 2707c26 
>   src/java/test/org/apache/zookeeper/server/quorum/QuorumPeerTestBase.java 
> c39f4c9 
>   src/java/test/org/apache/zookeeper/server/quorum/Zab1_0Test.java f107e04 
> 
> Diff: https://reviews.apache.org/r/8094/diff/
> 
> 
> Testing
> ---
> 
> unit tests
> 
> Ran in standalone mode (only option right now) and manually tried out all the 
> commands/links
> 
> 
> Thanks,
> 
> Skye Wanderman-Milne
> 
>

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

2013-01-21 Thread Apache Jenkins Server 
See https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008/678/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 184 lines...]
(zookeeper target) -> 
  cl : Command line warning D9035: option 'Wp64' has been deprecated and will 
be removed in a future release
  .\src\zookeeper.c(502): warning C4996: 'strdup': The POSIX name for this item 
is deprecated. Instead, use the ISO C++ conformant name: _strdup. See online 
help for details.
  .\src\zookeeper.c(750): warning C4996: 'strdup': The POSIX name for this item 
is deprecated. Instead, use the ISO C++ conformant name: _strdup. See online 
help for details.
  .\src\zookeeper.c(1005): warning C4996: 'strdup': The POSIX name for this 
item is deprecated. Instead, use the ISO C++ conformant name: _strdup. See 
online help for details.
  .\src\zookeeper.c(1016): warning C4996: 'strncpy': This function or variable 
may be unsafe. Consider using strncpy_s instead. To disable deprecation, use 
_CRT_SECURE_NO_WARNINGS. See online help for details.
  .\src\zookeeper.c(1022): warning C4996: 'strdup': The POSIX name for this 
item is deprecated. Instead, use the ISO C++ conformant name: _strdup. See 
online help for details.
  .\src\zookeeper.c(1083): warning C4996: 'strdup': The POSIX name for this 
item is deprecated. Instead, use the ISO C++ conformant name: _strdup. See 
online help for details.
  .\src\zookeeper.c(1212): warning C4996: 'strdup': The POSIX name for this 
item is deprecated. Instead, use the ISO C++ conformant name: _strdup. See 
online help for details.
  .\src\zookeeper.c(1215): warning C4996: 'strcpy': This function or variable 
may be unsafe. Consider using strcpy_s instead. To disable deprecation, use 
_CRT_SECURE_NO_WARNINGS. See online help for details.
  .\src\zookeeper.c(1216): warning C4996: 'strcat': This function or variable 
may be unsafe. Consider using strcat_s instead. To disable deprecation, use 
_CRT_SECURE_NO_WARNINGS. See online help for details.
  .\src\zookeeper.c(1235): warning C4996: 'strdup': The POSIX name for this 
item is deprecated. Instead, use the ISO C++ conformant name: _strdup. See 
online help for details.
  .\src\zookeeper.c(1238): warning C4996: 'strdup': The POSIX name for this 
item is deprecated. Instead, use the ISO C++ conformant name: _strdup. See 
online help for details.
  .\src\zookeeper.c(1582): warning C4996: 'vsnprintf': This function or 
variable may be unsafe. Consider using vsnprintf_s instead. To disable 
deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
  .\src\zookeeper.c(1585): warning C4996: 'strerror': This function or variable 
may be unsafe. Consider using strerror_s instead. To disable deprecation, use 
_CRT_SECURE_NO_WARNINGS. See online help for details.
  .\src\zookeeper.c(1812): warning C4996: 'strerror': This function or variable 
may be unsafe. Consider using strerror_s instead. To disable deprecation, use 
_CRT_SECURE_NO_WARNINGS. See online help for details.
  .\src\zookeeper.c(2053): warning C4133: 'function' : incompatible types - 
from 'int *__w64 ' to 'char *'
  .\src\zookeeper.c(2293): warning C4267: '=' : conversion from 'size_t' to 
'int', possible loss of data
  .\src\zookeeper.c(2311): warning C4267: '=' : conversion from 'size_t' to 
'int', possible loss of data
  .\src\zookeeper.c(2701): warning C4996: 'strdup': The POSIX name for this 
item is deprecated. Instead, use the ISO C++ conformant name: _strdup. See 
online help for details.
  .\src\zookeeper.c(2949): warning C4267: '=' : conversion from 'size_t' to 
'int', possible loss of data
  .\src\zookeeper.c(3494): warning C4267: 'initializing' : conversion from 
'size_t' to 'int', possible loss of data
  .\src\zookeeper.c(3844): warning C4996: 'strerror': This function or variable 
may be unsafe. Consider using strerror_s instead. To disable deprecation, use 
_CRT_SECURE_NO_WARNINGS. See online help for details.
  .\src\zookeeper.c(3880): warning C4996: 'strdup': The POSIX name for this 
item is deprecated. Instead, use the ISO C++ conformant name: _strdup. See 
online help for details.
  .\src\zookeeper.c(3919): warning C4996: 'sprintf': This function or variable 
may be unsafe. Consider using sprintf_s instead. To disable deprecation, use 
_CRT_SECURE_NO_WARNINGS. See online help for details.
  .\src\zk_log.c(120): warning C4996: '_snprintf': This function or variable 
may be unsafe. Consider using _snprintf_s instead. To disable deprecation, use 
_CRT_SECURE_NO_WARNINGS. See online help for details.
  .\src\zk_log.c(134): warning C4996: 'getpid': The POSIX name for this item is 
deprecated. Instead, use the ISO C++ conformant name: _getpid. See online help 
for details.
  .\src\zk_log.c(160): warning C4996: 'vsnprintf': This function or variable 
may be unsafe. Consider using vsnprintf_s instead. To disable deprecation, use 
_CRT_SECURE_NO_WARNINGS. See online

ZooKeeper-trunk-solaris - Build # 446 - Still Failing

2013-01-21 Thread Apache Jenkins Server 
See https://builds.apache.org/job/ZooKeeper-trunk-solaris/446/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 162209 lines...]
[junit] 2013-01-21 09:43:18,786 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@397] 
- selector thread exitted run method
[junit] 2013-01-21 09:43:18,787 [myid:] - INFO  [main:ZooKeeperServer@398] 
- shutting down
[junit] 2013-01-21 09:43:18,787 [myid:] - INFO  
[main:SessionTrackerImpl@180] - Shutting down
[junit] 2013-01-21 09:43:18,787 [myid:] - INFO  
[main:PrepRequestProcessor@804] - Shutting down
[junit] 2013-01-21 09:43:18,787 [myid:] - INFO  
[main:SyncRequestProcessor@175] - Shutting down
[junit] 2013-01-21 09:43:18,787 [myid:] - INFO  [ProcessThread(sid:0 
cport:-1)::PrepRequestProcessor@144] - PrepRequestProcessor exited loop!
[junit] 2013-01-21 09:43:18,787 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@155] - SyncRequestProcessor exited!
[junit] 2013-01-21 09:43:18,787 [myid:] - INFO  
[main:FinalRequestProcessor@421] - shutdown of request processor complete
[junit] 2013-01-21 09:43:18,788 [myid:] - INFO  
[main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221
[junit] 2013-01-21 09:43:18,788 [myid:] - INFO  [main:JMXEnv@133] - 
ensureOnly:[]
[junit] 2013-01-21 09:43:18,789 [myid:] - INFO  [main:ClientBase@414] - 
STARTING server
[junit] 2013-01-21 09:43:18,789 [myid:] - INFO  [main:ZooKeeperServer@149] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test2618327617513525893.junit.dir/version-2
 snapdir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test2618327617513525893.junit.dir/version-2
[junit] 2013-01-21 09:43:18,790 [myid:] - INFO  
[main:NIOServerCnxnFactory@647] - Configuring NIO connection handler with 10s 
sessionless connection timeout, 2 selector thread(s), 16 worker threads, and 64 
kB direct buffers.
[junit] 2013-01-21 09:43:18,790 [myid:] - INFO  
[main:NIOServerCnxnFactory@660] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2013-01-21 09:43:18,791 [myid:] - INFO  [main:FileSnap@83] - 
Reading snapshot 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test2618327617513525893.junit.dir/version-2/snapshot.b
[junit] 2013-01-21 09:43:18,793 [myid:] - INFO  [main:FileTxnSnapLog@270] - 
Snapshotting: 0xb to 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test2618327617513525893.junit.dir/version-2/snapshot.b
[junit] 2013-01-21 09:43:18,794 [myid:] - INFO  
[main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221
[junit] 2013-01-21 09:43:18,794 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@274]
 - Accepted socket connection from /127.0.0.1:45384
[junit] 2013-01-21 09:43:18,795 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@829] - Processing stat command from 
/127.0.0.1:45384
[junit] 2013-01-21 09:43:18,795 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn$StatCommand@678] - Stat command output
[junit] 2013-01-21 09:43:18,795 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@1000] - Closed socket connection for client 
/127.0.0.1:45384 (no session established for client)
[junit] 2013-01-21 09:43:18,802 [myid:] - INFO  [main:JMXEnv@133] - 
ensureOnly:[InMemoryDataTree, StandaloneServer_port]
[junit] 2013-01-21 09:43:18,803 [myid:] - INFO  [main:JMXEnv@105] - 
expect:InMemoryDataTree
[junit] 2013-01-21 09:43:18,803 [myid:] - INFO  [main:JMXEnv@108] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree
[junit] 2013-01-21 09:43:18,803 [myid:] - INFO  [main:JMXEnv@105] - 
expect:StandaloneServer_port
[junit] 2013-01-21 09:43:18,803 [myid:] - INFO  [main:JMXEnv@108] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port-1
[junit] 2013-01-21 09:43:18,803 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@57] - FINISHED TEST METHOD testQuota
[junit] 2013-01-21 09:43:18,804 [myid:] - INFO  [main:ClientBase@451] - 
tearDown starting
[junit] 2013-01-21 09:43:18,872 [myid:] - INFO  [main:ZooKeeper@744] - 
Session: 0x13c5c7d9052 closed
[junit] 2013-01-21 09:43:18,872 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@511] - EventThread shut down
[junit] 2013-01-21 09:43:18,873 [myid:] - INFO  [main:ClientBase@421] - 
STOPPING server
[junit] 2013-01-21 09:43:18,873 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$

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

2013-01-21 Thread Apache Jenkins Server 
See https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008/677/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 182 lines...]
(zookeeper target) -> 
  cl : Command line warning D9035: option 'Wp64' has been deprecated and will 
be removed in a future release
  .\src\zookeeper.c(502): warning C4996: 'strdup': The POSIX name for this item 
is deprecated. Instead, use the ISO C++ conformant name: _strdup. See online 
help for details.
  .\src\zookeeper.c(750): warning C4996: 'strdup': The POSIX name for this item 
is deprecated. Instead, use the ISO C++ conformant name: _strdup. See online 
help for details.
  .\src\zookeeper.c(1005): warning C4996: 'strdup': The POSIX name for this 
item is deprecated. Instead, use the ISO C++ conformant name: _strdup. See 
online help for details.
  .\src\zookeeper.c(1016): warning C4996: 'strncpy': This function or variable 
may be unsafe. Consider using strncpy_s instead. To disable deprecation, use 
_CRT_SECURE_NO_WARNINGS. See online help for details.
  .\src\zookeeper.c(1022): warning C4996: 'strdup': The POSIX name for this 
item is deprecated. Instead, use the ISO C++ conformant name: _strdup. See 
online help for details.
  .\src\zookeeper.c(1083): warning C4996: 'strdup': The POSIX name for this 
item is deprecated. Instead, use the ISO C++ conformant name: _strdup. See 
online help for details.
  .\src\zookeeper.c(1212): warning C4996: 'strdup': The POSIX name for this 
item is deprecated. Instead, use the ISO C++ conformant name: _strdup. See 
online help for details.
  .\src\zookeeper.c(1215): warning C4996: 'strcpy': This function or variable 
may be unsafe. Consider using strcpy_s instead. To disable deprecation, use 
_CRT_SECURE_NO_WARNINGS. See online help for details.
  .\src\zookeeper.c(1216): warning C4996: 'strcat': This function or variable 
may be unsafe. Consider using strcat_s instead. To disable deprecation, use 
_CRT_SECURE_NO_WARNINGS. See online help for details.
  .\src\zookeeper.c(1235): warning C4996: 'strdup': The POSIX name for this 
item is deprecated. Instead, use the ISO C++ conformant name: _strdup. See 
online help for details.
  .\src\zookeeper.c(1238): warning C4996: 'strdup': The POSIX name for this 
item is deprecated. Instead, use the ISO C++ conformant name: _strdup. See 
online help for details.
  .\src\zookeeper.c(1582): warning C4996: 'vsnprintf': This function or 
variable may be unsafe. Consider using vsnprintf_s instead. To disable 
deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
  .\src\zookeeper.c(1585): warning C4996: 'strerror': This function or variable 
may be unsafe. Consider using strerror_s instead. To disable deprecation, use 
_CRT_SECURE_NO_WARNINGS. See online help for details.
  .\src\zookeeper.c(1812): warning C4996: 'strerror': This function or variable 
may be unsafe. Consider using strerror_s instead. To disable deprecation, use 
_CRT_SECURE_NO_WARNINGS. See online help for details.
  .\src\zookeeper.c(2053): warning C4133: 'function' : incompatible types - 
from 'int *__w64 ' to 'char *'
  .\src\zookeeper.c(2293): warning C4267: '=' : conversion from 'size_t' to 
'int', possible loss of data
  .\src\zookeeper.c(2311): warning C4267: '=' : conversion from 'size_t' to 
'int', possible loss of data
  .\src\zookeeper.c(2701): warning C4996: 'strdup': The POSIX name for this 
item is deprecated. Instead, use the ISO C++ conformant name: _strdup. See 
online help for details.
  .\src\zookeeper.c(2949): warning C4267: '=' : conversion from 'size_t' to 
'int', possible loss of data
  .\src\zookeeper.c(3494): warning C4267: 'initializing' : conversion from 
'size_t' to 'int', possible loss of data
  .\src\zookeeper.c(3844): warning C4996: 'strerror': This function or variable 
may be unsafe. Consider using strerror_s instead. To disable deprecation, use 
_CRT_SECURE_NO_WARNINGS. See online help for details.
  .\src\zookeeper.c(3880): warning C4996: 'strdup': The POSIX name for this 
item is deprecated. Instead, use the ISO C++ conformant name: _strdup. See 
online help for details.
  .\src\zookeeper.c(3919): warning C4996: 'sprintf': This function or variable 
may be unsafe. Consider using sprintf_s instead. To disable deprecation, use 
_CRT_SECURE_NO_WARNINGS. See online help for details.
  .\src\zk_log.c(120): warning C4996: '_snprintf': This function or variable 
may be unsafe. Consider using _snprintf_s instead. To disable deprecation, use 
_CRT_SECURE_NO_WARNINGS. See online help for details.
  .\src\zk_log.c(134): warning C4996: 'getpid': The POSIX name for this item is 
deprecated. Instead, use the ISO C++ conformant name: _getpid. See online help 
for details.
  .\src\zk_log.c(160): warning C4996: 'vsnprintf': This function or variable 
may be unsafe. Consider using vsnprintf_s instead. To disable deprecation, use 
_CRT_SECURE_NO_WARNINGS. See online