[jira] [Updated] (ZOOKEEPER-1557) jenkins jdk7 test failure in testBadSaslAuthNotifiesWatch
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Junqueira updated ZOOKEEPER-1557: Fix Version/s: (was: 3.4.6) > jenkins jdk7 test failure in testBadSaslAuthNotifiesWatch > - > > Key: ZOOKEEPER-1557 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1557 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.0, 3.4.5 >Reporter: Patrick Hunt >Assignee: Eugene Koontz > Fix For: 3.5.0 > > Attachments: jstack.out, SaslAuthFailTest.log, ZOOKEEPER-1557.patch > > > Failure of testBadSaslAuthNotifiesWatch on the jenkins jdk7 job: > https://builds.apache.org/job/ZooKeeper-trunk-jdk7/407/ > haven't seen this before. -- 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-1557) jenkins jdk7 test failure in testBadSaslAuthNotifiesWatch
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13759580#comment-13759580 ] Flavio Junqueira commented on ZOOKEEPER-1557: - Moving it to 3.5.0. > jenkins jdk7 test failure in testBadSaslAuthNotifiesWatch > - > > Key: ZOOKEEPER-1557 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1557 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.0, 3.4.5 >Reporter: Patrick Hunt >Assignee: Eugene Koontz > Fix For: 3.5.0 > > Attachments: jstack.out, SaslAuthFailTest.log, ZOOKEEPER-1557.patch > > > Failure of testBadSaslAuthNotifiesWatch on the jenkins jdk7 job: > https://builds.apache.org/job/ZooKeeper-trunk-jdk7/407/ > haven't seen this before. -- 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-1448 PreCommit Build #1556
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1448 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1556/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 276929 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/12601682/ZOOKEEPER-1448-trunk.patch [exec] against trunk revision 1519655. [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/1556//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1556//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1556//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] 66d9d93ce0bc8ab93582d2e02d0b8fe1e9c39004 logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD SUCCESSFUL Total time: 31 minutes 14 seconds Archiving artifacts Recording test results Description set: ZOOKEEPER-1448 Email was triggered for: Success Sending email for trigger: Success ### ## FAILED TESTS (if any) ## All tests passed
[jira] [Commented] (ZOOKEEPER-1448) Node+Quota creation in transaction log can crash leader startup
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13759501#comment-13759501
]
Hadoop QA commented on ZOOKEEPER-1448:
--
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12601682/ZOOKEEPER-1448-trunk.patch
against trunk revision 1519655.
+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/1556//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1556//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1556//console
This message is automatically generated.
> Node+Quota creation in transaction log can crash leader startup
> ---
>
> Key: ZOOKEEPER-1448
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1448
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
>Affects Versions: 3.3.5
>Reporter: Botond Hejj
>Assignee: Flavio Junqueira
>Priority: Critical
> Fix For: 3.5.0, 3.4.6
>
> Attachments: ZOOKEEPER-1448_branch3.3.patch, ZOOKEEPER-1448.patch,
> ZOOKEEPER-1448.patch, ZOOKEEPER-1448.patch, ZOOKEEPER-1448.patch,
> ZOOKEEPER-1448.patch, ZOOKEEPER-1448-trunk.patch
>
>
> Hi,
> I've found a bug in zookeeper related to quota creation which can shutdown
> zookeeper leader on startup.
> Steps to reproduce:
> 1. create /quota_bug
> 2. setquota -n 1 /quota_bug
> 3. stop the whole ensemble (the previous operations should be in the
> transaction log)
> 4. start all the servers
> 5. the elected leader will shutdown with an exception (Missing stat node for
> count /zookeeper/quota/quota_bug/zookeeper_
> stats)
> I've debugged a bit what happening and I found the following problem:
> On startup each server loads the last snapshot and replays the last
> transaction log. While doing this it fills up the pTrie variable of the
> DataTree with the path of the nodes which have quota.
> After the leader is elected the leader servers loads the snapshot and last
> transaction log but it doesn't clean up the pTrie variable. This means it
> still contains the "/quota_bug" path. Now when the "create /quota_bug" is
> processed from the transaction log the DataTree already thinks that the quota
> nodes ("/zookeeper/quota/quota_bug/zookeeper_limits" and
> "/zookeeper/quota/quota_bug/zookeeper_stats") are created but those node
> creation actually comes later in the transaction log. This leads to the
> missing stat node exception.
> I think clearing the pTrie should solve this problem.
--
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-442) need a way to remove watches that are no longer of interest
[ https://issues.apache.org/jira/browse/ZOOKEEPER-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13759179#comment-13759179 ] Flavio Junqueira commented on ZOOKEEPER-442: Sounds like an interesting feature if anyone is looking for a low-hanging fruit to contribute. Shall we revisit this? > need a way to remove watches that are no longer of interest > --- > > Key: ZOOKEEPER-442 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-442 > Project: ZooKeeper > Issue Type: New Feature >Reporter: Benjamin Reed >Assignee: Daniel Gómez Ferro >Priority: Critical > Fix For: 3.5.0 > > Attachments: ZOOKEEPER-442.patch, ZOOKEEPER-442.patch, > ZOOKEEPER-442.patch, ZOOKEEPER-442.patch, ZOOKEEPER-442.patch, > ZOOKEEPER-442.patch, ZOOKEEPER-442.patch > > > currently the only way a watch cleared is to trigger it. we need a way to > enumerate the outstanding watch objects, find watch events the objects are > watching for, and remove interests in an event. -- 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-1448) Node+Quota creation in transaction log can crash leader startup
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13759461#comment-13759461
]
Flavio Junqueira commented on ZOOKEEPER-1448:
-
b3.4: Committed revision 1520418.
> Node+Quota creation in transaction log can crash leader startup
> ---
>
> Key: ZOOKEEPER-1448
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1448
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
>Affects Versions: 3.3.5
>Reporter: Botond Hejj
>Assignee: Flavio Junqueira
>Priority: Critical
> Fix For: 3.5.0, 3.4.6
>
> Attachments: ZOOKEEPER-1448_branch3.3.patch, ZOOKEEPER-1448.patch,
> ZOOKEEPER-1448.patch, ZOOKEEPER-1448.patch, ZOOKEEPER-1448.patch,
> ZOOKEEPER-1448.patch, ZOOKEEPER-1448-trunk.patch
>
>
> Hi,
> I've found a bug in zookeeper related to quota creation which can shutdown
> zookeeper leader on startup.
> Steps to reproduce:
> 1. create /quota_bug
> 2. setquota -n 1 /quota_bug
> 3. stop the whole ensemble (the previous operations should be in the
> transaction log)
> 4. start all the servers
> 5. the elected leader will shutdown with an exception (Missing stat node for
> count /zookeeper/quota/quota_bug/zookeeper_
> stats)
> I've debugged a bit what happening and I found the following problem:
> On startup each server loads the last snapshot and replays the last
> transaction log. While doing this it fills up the pTrie variable of the
> DataTree with the path of the nodes which have quota.
> After the leader is elected the leader servers loads the snapshot and last
> transaction log but it doesn't clean up the pTrie variable. This means it
> still contains the "/quota_bug" path. Now when the "create /quota_bug" is
> processed from the transaction log the DataTree already thinks that the quota
> nodes ("/zookeeper/quota/quota_bug/zookeeper_limits" and
> "/zookeeper/quota/quota_bug/zookeeper_stats") are created but those node
> creation actually comes later in the transaction log. This leads to the
> missing stat node exception.
> I think clearing the pTrie should solve this problem.
--
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] [Comment Edited] (ZOOKEEPER-1448) Node+Quota creation in transaction log can crash leader startup
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13759458#comment-13759458
]
Flavio Junqueira edited comment on ZOOKEEPER-1448 at 9/5/13 9:03 PM:
-
The latest patch didn't apply cleanly, so I generated a new one.
was (Author: fpj):
The latest patch didn't apply cleanly, so I generate a new one.
> Node+Quota creation in transaction log can crash leader startup
> ---
>
> Key: ZOOKEEPER-1448
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1448
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
>Affects Versions: 3.3.5
>Reporter: Botond Hejj
>Assignee: Flavio Junqueira
>Priority: Critical
> Fix For: 3.5.0, 3.4.6
>
> Attachments: ZOOKEEPER-1448_branch3.3.patch, ZOOKEEPER-1448.patch,
> ZOOKEEPER-1448.patch, ZOOKEEPER-1448.patch, ZOOKEEPER-1448.patch,
> ZOOKEEPER-1448.patch, ZOOKEEPER-1448-trunk.patch
>
>
> Hi,
> I've found a bug in zookeeper related to quota creation which can shutdown
> zookeeper leader on startup.
> Steps to reproduce:
> 1. create /quota_bug
> 2. setquota -n 1 /quota_bug
> 3. stop the whole ensemble (the previous operations should be in the
> transaction log)
> 4. start all the servers
> 5. the elected leader will shutdown with an exception (Missing stat node for
> count /zookeeper/quota/quota_bug/zookeeper_
> stats)
> I've debugged a bit what happening and I found the following problem:
> On startup each server loads the last snapshot and replays the last
> transaction log. While doing this it fills up the pTrie variable of the
> DataTree with the path of the nodes which have quota.
> After the leader is elected the leader servers loads the snapshot and last
> transaction log but it doesn't clean up the pTrie variable. This means it
> still contains the "/quota_bug" path. Now when the "create /quota_bug" is
> processed from the transaction log the DataTree already thinks that the quota
> nodes ("/zookeeper/quota/quota_bug/zookeeper_limits" and
> "/zookeeper/quota/quota_bug/zookeeper_stats") are created but those node
> creation actually comes later in the transaction log. This leads to the
> missing stat node exception.
> I think clearing the pTrie should solve this problem.
--
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-1448) Node+Quota creation in transaction log can crash leader startup
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flavio Junqueira updated ZOOKEEPER-1448:
Attachment: ZOOKEEPER-1448-trunk.patch
The latest patch didn't apply cleanly, so I generate a new one.
> Node+Quota creation in transaction log can crash leader startup
> ---
>
> Key: ZOOKEEPER-1448
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1448
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
>Affects Versions: 3.3.5
>Reporter: Botond Hejj
>Assignee: Flavio Junqueira
>Priority: Critical
> Fix For: 3.5.0, 3.4.6
>
> Attachments: ZOOKEEPER-1448_branch3.3.patch, ZOOKEEPER-1448.patch,
> ZOOKEEPER-1448.patch, ZOOKEEPER-1448.patch, ZOOKEEPER-1448.patch,
> ZOOKEEPER-1448.patch, ZOOKEEPER-1448-trunk.patch
>
>
> Hi,
> I've found a bug in zookeeper related to quota creation which can shutdown
> zookeeper leader on startup.
> Steps to reproduce:
> 1. create /quota_bug
> 2. setquota -n 1 /quota_bug
> 3. stop the whole ensemble (the previous operations should be in the
> transaction log)
> 4. start all the servers
> 5. the elected leader will shutdown with an exception (Missing stat node for
> count /zookeeper/quota/quota_bug/zookeeper_
> stats)
> I've debugged a bit what happening and I found the following problem:
> On startup each server loads the last snapshot and replays the last
> transaction log. While doing this it fills up the pTrie variable of the
> DataTree with the path of the nodes which have quota.
> After the leader is elected the leader servers loads the snapshot and last
> transaction log but it doesn't clean up the pTrie variable. This means it
> still contains the "/quota_bug" path. Now when the "create /quota_bug" is
> processed from the transaction log the DataTree already thinks that the quota
> nodes ("/zookeeper/quota/quota_bug/zookeeper_limits" and
> "/zookeeper/quota/quota_bug/zookeeper_stats") are created but those node
> creation actually comes later in the transaction log. This leads to the
> missing stat node exception.
> I think clearing the pTrie should solve this problem.
--
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-1753) ClientCnxn is not properly releasing the resources, which are used to ping RwServer
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh R updated ZOOKEEPER-1753:
Attachment: 0001-ZOOKEEPER-1753-fix-branch-3_4.patch
> ClientCnxn is not properly releasing the resources, which are used to ping
> RwServer
> ---
>
> Key: ZOOKEEPER-1753
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1753
> Project: ZooKeeper
> Issue Type: Bug
> Components: java client
>Reporter: Rakesh R
>Assignee: Rakesh R
> Fix For: 4.0.0, 3.4.6
>
> Attachments: 0001-ZOOKEEPER-1753-fix-branch-3_4.patch,
> 0001-ZOOKEEPER-1753.patch
>
>
> While pinging to the RwServer, ClientCnxn is opening a socket and using
> BufferedReader. These are not properly closed in finally block and could
> cause leaks on exceptional cases.
> ClientCnxn#pingRwServer()
> {code}
> try {
> Socket sock = new Socket(addr.getHostName(), addr.getPort());
> BufferedReader br = new BufferedReader(
> new InputStreamReader(sock.getInputStream()));
> ..
> sock.close();
> br.close();
> } catch (ConnectException e) {
> // ignore, this just means server is not up
> } catch (IOException e) {
> // some unexpected error, warn about it
> LOG.warn("Exception while seeking for r/w server " +
> e.getMessage(), e);
> }
> {code}
--
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
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13759315#comment-13759315
]
Asad Saeed commented on ZOOKEEPER-1366:
---
A few issues with this patch. It is much broader than it should be.
In Login.java: 2 timesources are being utilized and incorrectly compared:
Time.currentElapsedTime is not compatible with the (KerberosTicket).getEndTime
which will return the expiry based on the system time. The 2 time values are
compared in the following block
--
if (nextRefresh > expiry) {
LOG.error("next refresh: " + nextRefreshDate + " is
later than expiry " + expiryDate
+ ". This may indicate a clock skew
problem. Check that this host and the KDC's "
+ "hosts' clocks are in sync. Exiting
refresh thread.");
return;
--
ZookeeperServer::getTime: Utilization of Time.currentElapsedTime here will lead
to unusable timestamps for the mtime and ctime for nodes. DataTree::processTxn
uses the TxnHeader.time to populate the Stat structure. TxnHeader.time is
assigned by PrepRequestProcessor::pRequest2Txn using ZookeeperServer.getTime.
> 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,
> ZOOKEEPER-1366.patch, ZOOKEEPER-1366.patch, ZOOKEEPER-1366.patch,
> zookeeper-3.4.5-ZK1366-SC01.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] (BOOKKEEPER-664) Compaction increases latency on journal writes
[
https://issues.apache.org/jira/browse/BOOKKEEPER-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13759145#comment-13759145
]
Hadoop QA commented on BOOKKEEPER-664:
--
Testing JIRA BOOKKEEPER-664
Patch
[0001-BOOKKEEPER-664-branch-4.2-Compaction-increases-laten.patch|https://issues.apache.org/jira/secure/attachment/12601613/0001-BOOKKEEPER-664-branch-4.2-Compaction-increases-laten.patch]
downloaded at Thu Sep 5 15:06:20 UTC 2013
{color:red}-1{color} Patch failed to apply to head of branch
> Compaction increases latency on journal writes
> --
>
> Key: BOOKKEEPER-664
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-664
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-server
>Affects Versions: 4.2.1
>Reporter: Ivan Kelly
>Assignee: Ivan Kelly
> Fix For: 4.2.2, 4.3.0
>
> Attachments:
> 0001-BOOKKEEPER-664-branch-4.2-Compaction-increases-laten.patch,
> 0001-BOOKKEEPER-664-branch-4.2-Compaction-increases-laten.patch,
> 0001-BOOKKEEPER-664-Compaction-increases-latency-on-journ_branch4.2.patch,
> 0001-BOOKKEEPER-664-Compaction-increases-latency-on-journ-branch-4.2.patch,
> 0001-BOOKKEEPER-664-Compaction-increases-latency-on-journ.patch,
> 0001-BOOKKEEPER-664-Compaction-increases-latency-on-journ_trunk.patch,
> 0002-BOOKKEEPER-664-trunk-Compaction-increases-latency-on.patch, bench.png,
> BOOKKEEPER-664.patch
>
>
> Compaction writes to the journal to avoid data loss (see BOOKKEEPER-530).
> BOOKKEEPER-530 correctly identified that this may affect latency on the
> journal but we have observed this since in production. It is possible to
> avoid the journal completely, as twitter do in their github branch.
> Basically, we need to write to the entrylogger first, flush the entry log and
> then add to the index.
--
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-1753) ClientCnxn is not properly releasing the resources, which are used to ping RwServer
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13759161#comment-13759161
]
Hadoop QA commented on ZOOKEEPER-1753:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12601618/0001-ZOOKEEPER-1753-fix-branch-3_4.patch
against trunk revision 1519655.
+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/1555//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1555//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1555//console
This message is automatically generated.
> ClientCnxn is not properly releasing the resources, which are used to ping
> RwServer
> ---
>
> Key: ZOOKEEPER-1753
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1753
> Project: ZooKeeper
> Issue Type: Bug
> Components: java client
>Reporter: Rakesh R
>Assignee: Rakesh R
> Fix For: 4.0.0, 3.4.6
>
> Attachments: 0001-ZOOKEEPER-1753-fix-branch-3_4.patch,
> 0001-ZOOKEEPER-1753.patch
>
>
> While pinging to the RwServer, ClientCnxn is opening a socket and using
> BufferedReader. These are not properly closed in finally block and could
> cause leaks on exceptional cases.
> ClientCnxn#pingRwServer()
> {code}
> try {
> Socket sock = new Socket(addr.getHostName(), addr.getPort());
> BufferedReader br = new BufferedReader(
> new InputStreamReader(sock.getInputStream()));
> ..
> sock.close();
> br.close();
> } catch (ConnectException e) {
> // ignore, this just means server is not up
> } catch (IOException e) {
> // some unexpected error, warn about it
> LOG.warn("Exception while seeking for r/w server " +
> e.getMessage(), e);
> }
> {code}
--
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-1753 PreCommit Build #1555
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1753 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1555/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 279649 lines...] [exec] [exec] -1 overall. Here are the results of testing the latest attachment [exec] http://issues.apache.org/jira/secure/attachment/12601618/0001-ZOOKEEPER-1753-fix-branch-3_4.patch [exec] against trunk revision 1519655. [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/1555//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1555//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1555//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] 3d55ba67c287ff273d53e5179ebb5d36a80ed406 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: 31 minutes 11 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Recording test results Description set: ZOOKEEPER-1753 Email was triggered for: Failure Sending email for trigger: Failure ### ## FAILED TESTS (if any) ## All tests passed
[jira] [Updated] (ZOOKEEPER-1753) ClientCnxn is not properly releasing the resources, which are used to ping RwServer
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh R updated ZOOKEEPER-1753:
Fix Version/s: 3.4.6
> ClientCnxn is not properly releasing the resources, which are used to ping
> RwServer
> ---
>
> Key: ZOOKEEPER-1753
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1753
> Project: ZooKeeper
> Issue Type: Bug
> Components: java client
>Reporter: Rakesh R
>Assignee: Rakesh R
> Fix For: 4.0.0, 3.4.6
>
> Attachments: 0001-ZOOKEEPER-1753-fix-branch-3_4.patch,
> 0001-ZOOKEEPER-1753.patch
>
>
> While pinging to the RwServer, ClientCnxn is opening a socket and using
> BufferedReader. These are not properly closed in finally block and could
> cause leaks on exceptional cases.
> ClientCnxn#pingRwServer()
> {code}
> try {
> Socket sock = new Socket(addr.getHostName(), addr.getPort());
> BufferedReader br = new BufferedReader(
> new InputStreamReader(sock.getInputStream()));
> ..
> sock.close();
> br.close();
> } catch (ConnectException e) {
> // ignore, this just means server is not up
> } catch (IOException e) {
> // some unexpected error, warn about it
> LOG.warn("Exception while seeking for r/w server " +
> e.getMessage(), e);
> }
> {code}
--
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-1753) ClientCnxn is not properly releasing the resources, which are used to ping RwServer
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh R updated ZOOKEEPER-1753:
Attachment: 0001-ZOOKEEPER-1753.patch
> ClientCnxn is not properly releasing the resources, which are used to ping
> RwServer
> ---
>
> Key: ZOOKEEPER-1753
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1753
> Project: ZooKeeper
> Issue Type: Bug
> Components: java client
>Reporter: Rakesh R
>Assignee: Rakesh R
> Attachments: 0001-ZOOKEEPER-1753.patch
>
>
> While pinging to the RwServer, ClientCnxn is opening a socket and using
> BufferedReader. These are not properly closed in finally block and could
> cause leaks on exceptional cases.
> ClientCnxn#pingRwServer()
> {code}
> try {
> Socket sock = new Socket(addr.getHostName(), addr.getPort());
> BufferedReader br = new BufferedReader(
> new InputStreamReader(sock.getInputStream()));
> ..
> sock.close();
> br.close();
> } catch (ConnectException e) {
> // ignore, this just means server is not up
> } catch (IOException e) {
> // some unexpected error, warn about it
> LOG.warn("Exception while seeking for r/w server " +
> e.getMessage(), e);
> }
> {code}
--
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-1753) ClientCnxn is not properly releasing the resources, which are used to ping RwServer
Rakesh R created ZOOKEEPER-1753:
---
Summary: ClientCnxn is not properly releasing the resources, which
are used to ping RwServer
Key: ZOOKEEPER-1753
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1753
Project: ZooKeeper
Issue Type: Bug
Components: java client
Reporter: Rakesh R
Assignee: Rakesh R
While pinging to the RwServer, ClientCnxn is opening a socket and using
BufferedReader. These are not properly closed in finally block and could cause
leaks on exceptional cases.
ClientCnxn#pingRwServer()
{code}
try {
Socket sock = new Socket(addr.getHostName(), addr.getPort());
BufferedReader br = new BufferedReader(
new InputStreamReader(sock.getInputStream()));
..
sock.close();
br.close();
} catch (ConnectException e) {
// ignore, this just means server is not up
} catch (IOException e) {
// some unexpected error, warn about it
LOG.warn("Exception while seeking for r/w server " +
e.getMessage(), e);
}
{code}
--
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
ZooKeeper-trunk-solaris - Build # 661 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-solaris/661/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 198189 lines...] [junit] 2013-09-05 09:11:47,240 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2013-09-05 09:11:47,241 [myid:] - INFO [main:ZooKeeperServer@422] - shutting down [junit] 2013-09-05 09:11:47,241 [myid:] - INFO [main:SessionTrackerImpl@180] - Shutting down [junit] 2013-09-05 09:11:47,241 [myid:] - INFO [main:PrepRequestProcessor@929] - Shutting down [junit] 2013-09-05 09:11:47,242 [myid:] - INFO [main:SyncRequestProcessor@175] - Shutting down [junit] 2013-09-05 09:11:47,242 [myid:] - INFO [ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@156] - PrepRequestProcessor exited loop! [junit] 2013-09-05 09:11:47,242 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@155] - SyncRequestProcessor exited! [junit] 2013-09-05 09:11:47,242 [myid:] - INFO [main:FinalRequestProcessor@427] - shutdown of request processor complete [junit] 2013-09-05 09:11:47,243 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-09-05 09:11:47,243 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[] [junit] 2013-09-05 09:11:47,245 [myid:] - INFO [main:ClientBase@414] - STARTING server [junit] 2013-09-05 09:11:47,245 [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/test8789806051345349794.junit.dir/version-2 snapdir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test8789806051345349794.junit.dir/version-2 [junit] 2013-09-05 09:11:47,246 [myid:] - INFO [main:NIOServerCnxnFactory@670] - Configuring NIO connection handler with 10s sessionless connection timeout, 2 selector thread(s), 16 worker threads, and 64 kB direct buffers. [junit] 2013-09-05 09:11:47,246 [myid:] - INFO [main:NIOServerCnxnFactory@683] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2013-09-05 09:11:47,247 [myid:] - INFO [main:FileSnap@83] - Reading snapshot /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test8789806051345349794.junit.dir/version-2/snapshot.b [junit] 2013-09-05 09:11:47,250 [myid:] - INFO [main:FileTxnSnapLog@297] - Snapshotting: 0xb to /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test8789806051345349794.junit.dir/version-2/snapshot.b [junit] 2013-09-05 09:11:47,251 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-09-05 09:11:47,252 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:57136 [junit] 2013-09-05 09:11:47,253 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@829] - Processing stat command from /127.0.0.1:57136 [junit] 2013-09-05 09:11:47,253 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn$StatCommand@678] - Stat command output [junit] 2013-09-05 09:11:47,253 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@1000] - Closed socket connection for client /127.0.0.1:57136 (no session established for client) [junit] 2013-09-05 09:11:47,253 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[InMemoryDataTree, StandaloneServer_port] [junit] 2013-09-05 09:11:47,255 [myid:] - INFO [main:JMXEnv@105] - expect:InMemoryDataTree [junit] 2013-09-05 09:11:47,255 [myid:] - INFO [main:JMXEnv@108] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] 2013-09-05 09:11:47,255 [myid:] - INFO [main:JMXEnv@105] - expect:StandaloneServer_port [junit] 2013-09-05 09:11:47,255 [myid:] - INFO [main:JMXEnv@108] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2013-09-05 09:11:47,256 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@57] - FINISHED TEST METHOD testQuota [junit] 2013-09-05 09:11:47,256 [myid:] - INFO [main:ClientBase@451] - tearDown starting [junit] 2013-09-05 09:11:47,326 [myid:] - INFO [main:ZooKeeper@777] - Session: 0x140ed6443ce closed [junit] 2013-09-05 09:11:47,326 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down [junit] 2013-09-05 09:11:47,326 [myid:] - INFO [main:ClientBase@421] - STOPPING server [junit] 2013-09-05 09:11:47,327 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$
[jira] [Updated] (ZOOKEEPER-1552) Enable sync request processor in Observer
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Germán Blanco updated ZOOKEEPER-1552: - Attachment: ZOOKEEPER-1552.patch I have dared to do a bit of cleanup on the patch so that it runs against current 3.4 branch. I believe I have modified only spaces and blank lines. > Enable sync request processor in Observer > - > > Key: ZOOKEEPER-1552 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1552 > Project: ZooKeeper > Issue Type: Improvement > Components: quorum, server >Affects Versions: 3.4.3 >Reporter: Thawan Kooburat >Assignee: Thawan Kooburat > Fix For: 3.5.0, 3.4.6 > > Attachments: ZOOKEEPER-1552.patch, ZOOKEEPER-1552.patch, > ZOOKEEPER-1552.patch, ZOOKEEPER-1552.patch > > > Observer doesn't forward its txns to SyncRequestProcessor. So it never > persists the txns onto disk or periodically creates snapshots. This increases > the start-up time since it will get the entire snapshot if the observer has > be running for a long time. -- 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-1657) Increased CPU usage by unnecessary SASL checks
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758852#comment-13758852
]
Flavio Junqueira commented on ZOOKEEPER-1657:
-
Can I get a +1 here please?
> Increased CPU usage by unnecessary SASL checks
> --
>
> Key: ZOOKEEPER-1657
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1657
> Project: ZooKeeper
> Issue Type: Bug
> Components: java client
>Affects Versions: 3.4.5
>Reporter: Gunnar Wagenknecht
>Assignee: Philip K. Warren
> Labels: performance
> Fix For: 3.5.0, 3.4.6
>
> Attachments: ZOOKEEPER-1657.patch, ZOOKEEPER-1657.patch,
> ZOOKEEPER-1657.patch, ZOOKEEPER-1657.patch, ZOOKEEPER-1657.patch,
> zookeeper-hotspot-gone.png, zookeeper-hotspot.png
>
>
> I did some profiling in one of our Java environments and found an interesting
> footprint in ZooKeeper. The SASL support seems to trigger a lot times on the
> client although it's not even in use.
> Is there a switch to disable SASL completely?
> The attached screenshot shows a 10-minute profiling session on one of our
> production Jetty servers. The Jetty server handles ~1k web requests per
> minute. The average response time per web request is a few milli seconds. The
> profiling was performed on a machine running for >24h.
> We noticed a significant CPU increase on our servers when deploying an update
> from ZooKeeper 3.3.2 to ZooKeeper 3.4.5. Thus, we started investigating. The
> screenshot shows that only 32% CPU time are spent in Jetty. In contrast, 65%
> are spend in ZooKeeper.
> A few notes/thoughts:
> * {{ClientCnxn$SendThread.clientTunneledAuthenticationInProgress}} seems to
> be the culprit
> * {{javax.security.auth.login.Configuration.getConfiguration}} seems to be
> called very often?
> * There is quite a bit reflection involved in
> {{java.security.AccessController.doPrivileged}}
> * No security manager is active in the JVM: I tend to place an if-check in
> the code before calling {{AccessController.doPrivileged}}. When no SM is
> installed, the runnable can be called directly which safes cycles.
--
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
ZooKeeper_branch33_solaris - Build # 637 - Failure
See https://builds.apache.org/job/ZooKeeper_branch33_solaris/637/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 105794 lines...] [junit] 2013-09-05 07:11:03,771 - INFO [main:ZooKeeperServer@154] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch33_solaris/trunk/build/test/tmp/test6611897664099915525.junit.dir/version-2 snapdir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch33_solaris/trunk/build/test/tmp/test6611897664099915525.junit.dir/version-2 [junit] 2013-09-05 07:11:03,772 - INFO [main:NIOServerCnxn$Factory@143] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2013-09-05 07:11:03,774 - INFO [main:FileSnap@82] - Reading snapshot /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch33_solaris/trunk/build/test/tmp/test6611897664099915525.junit.dir/version-2/snapshot.0 [junit] 2013-09-05 07:11:03,777 - INFO [main:FileTxnSnapLog@256] - Snapshotting: b [junit] 2013-09-05 07:11:03,779 - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-09-05 07:11:03,780 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn$Factory@251] - Accepted socket connection from /127.0.0.1:39225 [junit] 2013-09-05 07:11:03,781 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@1237] - Processing stat command from /127.0.0.1:39225 [junit] 2013-09-05 07:11:03,782 - INFO [Thread-4:NIOServerCnxn$StatCommand@1153] - Stat command output [junit] 2013-09-05 07:11:03,783 - INFO [Thread-4:NIOServerCnxn@1435] - Closed socket connection for client /127.0.0.1:39225 (no session established for client) [junit] ensureOnly:[InMemoryDataTree, StandaloneServer_port] [junit] expect:InMemoryDataTree [junit] found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] expect:StandaloneServer_port [junit] found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2013-09-05 07:11:03,786 - INFO [main:ClientBase@408] - STOPPING server [junit] 2013-09-05 07:11:03,788 - INFO [ProcessThread:-1:PrepRequestProcessor@128] - PrepRequestProcessor exited loop! [junit] 2013-09-05 07:11:03,788 - INFO [SyncThread:0:SyncRequestProcessor@151] - SyncRequestProcessor exited! [junit] 2013-09-05 07:11:03,789 - INFO [main:FinalRequestProcessor@370] - shutdown of request processor complete [junit] 2013-09-05 07:11:03,790 - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] ensureOnly:[] [junit] 2013-09-05 07:11:03,792 - INFO [main:ClientBase@401] - STARTING server [junit] 2013-09-05 07:11:03,793 - INFO [main:ZooKeeperServer@154] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch33_solaris/trunk/build/test/tmp/test6611897664099915525.junit.dir/version-2 snapdir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch33_solaris/trunk/build/test/tmp/test6611897664099915525.junit.dir/version-2 [junit] 2013-09-05 07:11:03,794 - INFO [main:NIOServerCnxn$Factory@143] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2013-09-05 07:11:03,795 - INFO [main:FileSnap@82] - Reading snapshot /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch33_solaris/trunk/build/test/tmp/test6611897664099915525.junit.dir/version-2/snapshot.b [junit] 2013-09-05 07:11:03,798 - INFO [main:FileTxnSnapLog@256] - Snapshotting: b [junit] 2013-09-05 07:11:03,800 - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-09-05 07:11:03,801 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn$Factory@251] - Accepted socket connection from /127.0.0.1:39227 [junit] 2013-09-05 07:11:03,802 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@1237] - Processing stat command from /127.0.0.1:39227 [junit] 2013-09-05 07:11:03,802 - INFO [Thread-5:NIOServerCnxn$StatCommand@1153] - Stat command output [junit] 2013-09-05 07:11:03,804 - INFO [Thread-5:NIOServerCnxn@1435] - Closed socket connection for client /127.0.0.1:39227 (no session established for client) [junit] ensureOnly:[InMemoryDataTree, StandaloneServer_port] [junit] expect:InMemoryDataTree [junit] found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] expect:StandaloneServer_port [junit] found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2013-09-05 07:11:03,806 - INFO [main:Clie
