Code to clean up transaction logs needs snapshots before it works?

[Koen De Groote]

Greetings all.

I was debugging something an ran into this bit of code:
https://github.com/apache/zookeeper/blob/master/zookeeper-server/src/main/java/org/apache/zookeeper/server/PurgeTxnLog.java#L81

If I understand it correctly, it seems that this means log.x files will
only get deleted if there's a snapshot.

Which is troublesome, as my dataDir is filling up with log files but not a
single snapshot in sight.

1: Is this correct behavior? Both the logic of needing a snapshot and the
fact that not snapshots are being generated?

2: While not having a fix for this, what would be useful to know is: can
these log files be freely deleted? Or does the most recent one need to be
kept, or how does it go with this files?

I thought that running "bin/zkCleanup.sh /data -n 3" would clean up both
the snapshots and the logs, but it appears that if there are not snapshots,
the logs aren't cleaned either.

What are my options here?

Kind regards,
Koen De Groote

Build failed in Jenkins: PreCommit-ZOOKEEPER-github-pr-build-maven #1121

[Apache Jenkins Server]

See 


--
[...truncated 705.20 KB...]
Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Building index for all the packages and classes...
Generating 

Generating 

Generating 

Building index for all classes...
Generating 

Generating 

Generating 

Generating 

Generating 

30 warnings
[WARNING] Javadoc Warnings
[WARNING] 
:444:
 warning - Tag @see: missing '#': "dumpConnectionInfo(PrintWriter, boolean) for 
brief stats"
[WARNING] 
:489:
 warning - @return tag has no arguments.
[WARNING] 
:312:
 warning - @return tag has no arguments.
[WARNING] 
:522:
 warning - @return tag has no arguments.
[WARNING] 

ZooKeeper_branch34_openjdk8 - Build # 420 - Failure

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch34_openjdk8/420/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 44.80 KB...]
[junit] Running org.apache.zookeeper.test.SaslAuthFailNotifyTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.576 sec
[junit] Running org.apache.zookeeper.test.SaslAuthFailTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.69 sec
[junit] Running org.apache.zookeeper.test.SaslAuthMissingClientConfigTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.584 sec
[junit] Running org.apache.zookeeper.test.SaslClientTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.082 sec
[junit] Running org.apache.zookeeper.test.SessionInvalidationTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.602 sec
[junit] Running org.apache.zookeeper.test.SessionTest
[junit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
11.48 sec
[junit] Running org.apache.zookeeper.test.SessionTimeoutTest
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.303 sec
[junit] Running org.apache.zookeeper.test.StandaloneTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.929 sec
[junit] Running org.apache.zookeeper.test.StatTest
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.794 sec
[junit] Running org.apache.zookeeper.test.StaticHostProviderTest
[junit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.866 sec
[junit] Running org.apache.zookeeper.test.SyncCallTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.563 sec
[junit] Running org.apache.zookeeper.test.TruncateTest
[junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
6.074 sec
[junit] Running org.apache.zookeeper.test.UpgradeTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.785 sec
[junit] Running org.apache.zookeeper.test.WatchedEventTest
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.082 sec
[junit] Running org.apache.zookeeper.test.WatcherFuncTest
[junit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.776 sec
[junit] Running org.apache.zookeeper.test.WatcherTest
[junit] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
28.302 sec
[junit] Running org.apache.zookeeper.test.ZkDatabaseCorruptionTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
4.809 sec
[junit] Running org.apache.zookeeper.test.ZooKeeperQuotaTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.743 sec
[junit] Running org.apache.jute.BinaryInputArchiveTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.086 sec

fail.build.on.test.failure:

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_openjdk8/build.xml:1425:
 The following error occurred while executing this line:
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_openjdk8/build.xml:1428:
 Tests failed!

Total time: 27 minutes 27 seconds
Build step 'Invoke Ant' marked build as failure
Archiving artifacts
Setting OPENJDK_8_ON_UBUNTU_ONLY__HOME=/usr/lib/jvm/java-8-openjdk-amd64/
Recording test results
Setting OPENJDK_8_ON_UBUNTU_ONLY__HOME=/usr/lib/jvm/java-8-openjdk-amd64/
Setting OPENJDK_8_ON_UBUNTU_ONLY__HOME=/usr/lib/jvm/java-8-openjdk-amd64/
Setting OPENJDK_8_ON_UBUNTU_ONLY__HOME=/usr/lib/jvm/java-8-openjdk-amd64/
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting OPENJDK_8_ON_UBUNTU_ONLY__HOME=/usr/lib/jvm/java-8-openjdk-amd64/
Setting OPENJDK_8_ON_UBUNTU_ONLY__HOME=/usr/lib/jvm/java-8-openjdk-amd64/
Setting OPENJDK_8_ON_UBUNTU_ONLY__HOME=/usr/lib/jvm/java-8-openjdk-amd64/
Setting OPENJDK_8_ON_UBUNTU_ONLY__HOME=/usr/lib/jvm/java-8-openjdk-amd64/



###
## FAILED TESTS (if any) 
##
23 tests failed.
FAILED:  org.apache.zookeeper.test.AsyncHammerTest.testObserversHammer

Error Message:
Address already in use

Stack Trace:
java.net.BindException: Address already in use
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:433)
at sun.nio.ch.Net.bind(Net.java:425)
at 
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:67)
at 

Re: Upgrade FAQ

[Norbert Kalmar]

Great, thanks Andor!

On Wed, Aug 14, 2019 at 11:52 AM Andor Molnar  wrote:

> Hi,
>
> I’ve created the following FAQ page on the wiki to collect all upgrade
> related issues and workarounds.
>
> https://cwiki.apache.org/confluence/display/ZOOKEEPER/Upgrade+FAQ
>
> Haven’t found any existing doc on the topic, hence I’ve created this one
> quickly. We might want to move it to the documentation in the long run.
>
> Please add anything that you’ve come across already.
>
> Andor
>
>

Jenkins build is still unstable: zookeeper-master-maven-jdk11 #97

[Apache Jenkins Server]

See 

Re: Code to clean up transaction logs needs snapshots before it works?

[Norbert Kalmar]

Hi,

Without a snapshot, we cannot delete the log files, as we would have no
means of recovery. txn logs applied to the snapshot gives us back the
state. Without snapshot, all txn logs needs to be "replayed" in a recovery.
And you need all the log files created since your last snapshot (in this
case, all the txn logs as there were no snapshots yet).

As for why there is no snapshot. What is your load? Per the admin guide:

"snapCount
(Java system property: zookeeper.snapCount)
ZooKeeper logs transactions to a transaction log. After snapCount
transactions are written to a log file a snapshot is started and a new
transaction log file is created. The default snapCount is 100,000."

By default there will be no auto-cleaning of the snapshot and log files.
Check the autopurge.snapRetainCount and autopurge.purgeInterval settings
for this.

Regards,
Norbert

On Wed, Aug 14, 2019 at 1:21 PM Koen De Groote 
wrote:

> Greetings all.
>
> I was debugging something an ran into this bit of code:
>
> https://github.com/apache/zookeeper/blob/master/zookeeper-server/src/main/java/org/apache/zookeeper/server/PurgeTxnLog.java#L81
>
> If I understand it correctly, it seems that this means log.x files will
> only get deleted if there's a snapshot.
>
> Which is troublesome, as my dataDir is filling up with log files but not a
> single snapshot in sight.
>
> 1: Is this correct behavior? Both the logic of needing a snapshot and the
> fact that not snapshots are being generated?
>
> 2: While not having a fix for this, what would be useful to know is: can
> these log files be freely deleted? Or does the most recent one need to be
> kept, or how does it go with this files?
>
> I thought that running "bin/zkCleanup.sh /data -n 3" would clean up both
> the snapshots and the logs, but it appears that if there are not snapshots,
> the logs aren't cleaned either.
>
> What are my options here?
>
> Kind regards,
> Koen De Groote
>

Jenkins build is back to normal : ZooKeeper-trunk-owasp #457

[Apache Jenkins Server]

See 

Re: Code to clean up transaction logs needs snapshots before it works?

[Koen De Groote]

>Without a snapshot, we cannot delete the log files, as we would have no
>means of recovery. txn logs applied to the snapshot gives us back the
>state. Without snapshot, all txn logs needs to be "replayed" in a recovery.
>And you need all the log files created since your last snapshot (in this
>case, all the txn logs as there were no snapshots yet).

Makes sense.

In the heaviest environment I'm hitting around 200 requests per second,
which all have to get data from zookeeper. Not sure what the impact is in
terms of snapCount, I didn't set up the system myself and don't fully grasp
the internals.

As for the snapCount, that hasn't been touched, so that will be the default
in my environments.
I've read that the log files are preallocated. I see them as being 65MB a
piece.

Which makes me wonder: how many of those until the process hits 10
snaps?

auto-cleaning is setup, retainCount=3, purgeInterval=1

Restarting the zookeeper process shouldn't affect this count, I think? It
doesn't happen often, though it might on test environments.



On Wed, Aug 14, 2019 at 2:06 PM Norbert Kalmar 
wrote:

> Hi,
>
> Without a snapshot, we cannot delete the log files, as we would have no
> means of recovery. txn logs applied to the snapshot gives us back the
> state. Without snapshot, all txn logs needs to be "replayed" in a recovery.
> And you need all the log files created since your last snapshot (in this
> case, all the txn logs as there were no snapshots yet).
>
> As for why there is no snapshot. What is your load? Per the admin guide:
>
> "snapCount
> (Java system property: zookeeper.snapCount)
> ZooKeeper logs transactions to a transaction log. After snapCount
> transactions are written to a log file a snapshot is started and a new
> transaction log file is created. The default snapCount is 100,000."
>
> By default there will be no auto-cleaning of the snapshot and log files.
> Check the autopurge.snapRetainCount and autopurge.purgeInterval settings
> for this.
>
> Regards,
> Norbert
>
> On Wed, Aug 14, 2019 at 1:21 PM Koen De Groote <
> koen.degro...@limecraft.com>
> wrote:
>
> > Greetings all.
> >
> > I was debugging something an ran into this bit of code:
> >
> >
> https://github.com/apache/zookeeper/blob/master/zookeeper-server/src/main/java/org/apache/zookeeper/server/PurgeTxnLog.java#L81
> >
> > If I understand it correctly, it seems that this means log.x files
> will
> > only get deleted if there's a snapshot.
> >
> > Which is troublesome, as my dataDir is filling up with log files but not
> a
> > single snapshot in sight.
> >
> > 1: Is this correct behavior? Both the logic of needing a snapshot and the
> > fact that not snapshots are being generated?
> >
> > 2: While not having a fix for this, what would be useful to know is: can
> > these log files be freely deleted? Or does the most recent one need to be
> > kept, or how does it go with this files?
> >
> > I thought that running "bin/zkCleanup.sh /data -n 3" would clean up both
> > the snapshots and the logs, but it appears that if there are not
> snapshots,
> > the logs aren't cleaned either.
> >
> > What are my options here?
> >
> > Kind regards,
> > Koen De Groote
> >
>

ZooKeeper_branch34_jdk8 - Build # 1894 - Failure

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 43.39 KB...]
[junit] Running org.apache.zookeeper.test.RestoreCommittedLogTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
21.968 sec
[junit] Running org.apache.zookeeper.test.SaslAuthDesignatedClientTest
[junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
2.948 sec
[junit] Running org.apache.zookeeper.test.SaslAuthDesignatedServerTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.539 sec
[junit] Running org.apache.zookeeper.test.SaslAuthFailDesignatedClientTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
2.774 sec
[junit] Running org.apache.zookeeper.test.SaslAuthFailNotifyTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.549 sec
[junit] Running org.apache.zookeeper.test.SaslAuthFailTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.773 sec
[junit] Running org.apache.zookeeper.test.SaslAuthMissingClientConfigTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.805 sec
[junit] Running org.apache.zookeeper.test.SaslClientTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.134 sec
[junit] Running org.apache.zookeeper.test.SessionInvalidationTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.351 sec
[junit] Running org.apache.zookeeper.test.SessionTest
[junit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
13.245 sec
[junit] Running org.apache.zookeeper.test.SessionTimeoutTest
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
2.565 sec
[junit] Running org.apache.zookeeper.test.StandaloneTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.15 sec
[junit] Running org.apache.zookeeper.test.StatTest
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
2.285 sec
[junit] Running org.apache.zookeeper.test.StaticHostProviderTest
[junit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.969 sec
[junit] Running org.apache.zookeeper.test.SyncCallTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.991 sec
[junit] Running org.apache.zookeeper.test.TruncateTest
[junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
11.149 sec
[junit] Running org.apache.zookeeper.test.UpgradeTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
2.681 sec
[junit] Running org.apache.zookeeper.test.WatchedEventTest
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.164 sec
[junit] Running org.apache.zookeeper.test.WatcherFuncTest
[junit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
4.745 sec
[junit] Running org.apache.zookeeper.test.WatcherTest
[junit] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
32.421 sec
[junit] Running org.apache.zookeeper.test.ZkDatabaseCorruptionTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
26.009 sec
[junit] Running org.apache.zookeeper.test.ZooKeeperQuotaTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
2.062 sec
[junit] Running org.apache.jute.BinaryInputArchiveTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.192 sec

fail.build.on.test.failure:

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk8/build.xml:1425: 
The following error occurred while executing this line:
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk8/build.xml:1428: 
Tests failed!

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



###
## FAILED TESTS (if any) 
##
2 tests failed.
FAILED:  org.apache.zookeeper.test.WatcherTest.testWatcherAutoResetWithLocal

Error Message:
Unable to connect to server

Stack Trace:
junit.framework.AssertionFailedError: Unable to connect to server
at 
org.apache.zookeeper.test.ClientBase.createClient(ClientBase.java:234)
at 
org.apache.zookeeper.test.WatcherTest.testWatcherAutoResetWithLocal(WatcherTest.java:254)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:55)


FAILED:  

Re: Upgrade FAQ

[Patrick Hunt]

Good idea. thx.

Patrick

On Wed, Aug 14, 2019 at 5:54 AM Enrico Olivelli  wrote:

> Awesome
>
> Enrico
>
> Il mer 14 ago 2019, 14:00 Norbert Kalmar  ha
> scritto:
>
> > Great, thanks Andor!
> >
> > On Wed, Aug 14, 2019 at 11:52 AM Andor Molnar  wrote:
> >
> > > Hi,
> > >
> > > I’ve created the following FAQ page on the wiki to collect all upgrade
> > > related issues and workarounds.
> > >
> > > https://cwiki.apache.org/confluence/display/ZOOKEEPER/Upgrade+FAQ
> > >
> > > Haven’t found any existing doc on the topic, hence I’ve created this
> one
> > > quickly. We might want to move it to the documentation in the long run.
> > >
> > > Please add anything that you’ve come across already.
> > >
> > > Andor
> > >
> > >
> >
>

Upgrade FAQ

[Andor Molnar]

Hi,

I’ve created the following FAQ page on the wiki to collect all upgrade related 
issues and workarounds.

https://cwiki.apache.org/confluence/display/ZOOKEEPER/Upgrade+FAQ

Haven’t found any existing doc on the topic, hence I’ve created this one 
quickly. We might want to move it to the documentation in the long run.

Please add anything that you’ve come across already.

Andor

Build failed in Jenkins: zookeeper-master-maven-owasp #95

[Apache Jenkins Server]

See 


--
[...truncated 263.05 KB...]
Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Building index for all the packages and classes...
Generating 

Generating 

Generating 

[jira] [Created] (ZOOKEEPER-3506) correct the SessionTrackerImpl#initializeNextSession's java doc about how to generate the sessionId

[maoling (JIRA)]

maoling created ZOOKEEPER-3506:
--

 Summary: correct the SessionTrackerImpl#initializeNextSession's 
java doc about how to generate the sessionId
 Key: ZOOKEEPER-3506
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3506
 Project: ZooKeeper
  Issue Type: Improvement
  Components: documentation, server
Reporter: maoling
 Fix For: 3.6.0


 
{code:java}
/**
 * Generates an initial sessionId. High order byte is serverId, next 5
 * 5 bytes are from timestamp, and low order 2 bytes are 0s.
 */
public static long initializeNextSession(long id) {
long nextSid;
nextSid = (Time.currentElapsedTime() << 24) >>> 8;
nextSid =  nextSid | (id <<56);
if (nextSid == EphemeralType.CONTAINER_EPHEMERAL_OWNER) {
++nextSid;  // this is an unlikely edge case, but check it just in case
}
return nextSid;
}
{code}
 

 



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Created] (ZOOKEEPER-3507) Revisit name patterns

[TisonKun (JIRA)]

TisonKun created ZOOKEEPER-3507:
---

 Summary: Revisit name patterns
 Key: ZOOKEEPER-3507
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3507
 Project: ZooKeeper
  Issue Type: Improvement
Reporter: TisonKun


While enabling checkstyle configuration on zookeeper-server, it raises the 
discussion that how we treat variable/type names out of suggested pattern. 
Backward compatibility and a consistent view should be taken into consideration.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Re: Upgrade FAQ

[Enrico Olivelli]

Awesome

Enrico

Il mer 14 ago 2019, 14:00 Norbert Kalmar  ha
scritto:

> Great, thanks Andor!
>
> On Wed, Aug 14, 2019 at 11:52 AM Andor Molnar  wrote:
>
> > Hi,
> >
> > I’ve created the following FAQ page on the wiki to collect all upgrade
> > related issues and workarounds.
> >
> > https://cwiki.apache.org/confluence/display/ZOOKEEPER/Upgrade+FAQ
> >
> > Haven’t found any existing doc on the topic, hence I’ve created this one
> > quickly. We might want to move it to the documentation in the long run.
> >
> > Please add anything that you’ve come across already.
> >
> > Andor
> >
> >
>

Re: Code to clean up transaction logs needs snapshots before it works?

[Norbert Kalmar]

Read doesn't matter, there will be no txn logs for read. Only modifications
are logged (state changes to the datatree).

As for why all txn logs are 64MB:
"preAllocSize
(Java system property: zookeeper.preAllocSize)
To avoid seeks ZooKeeper allocates space in the transaction log file in
blocks of preAllocSize kilobytes. The default block size is 64M. One reason
for changing the size of the blocks is to reduce the block size if
snapshots are taken more often. (Also, see snapCount)."

Note that all txn is written to one log file. That's why it is 64MB by
default.
I didn't check which version of admin guide I quoted, but here is the one
from 3.4.13:

snapCount
ZooKeeper records its transactions using snapshots and a transaction log
(think write-ahead log).The number of transactions recorded in the
transaction log before a snapshot can be taken (and the transaction log
rolled) is determined by snapCount. In order to prevent all of the machines
in the quorum from taking a snapshot at the same time, each ZooKeeper
server will take a snapshot when the number of transactions in the
transaction log reaches a runtime generated random value in the
[snapCount/2+1, snapCount] range.The default snapCount is 100,000.

I'm not sure without checking the code what happens if preAllocSize is
filled (new log file I think), but after a restart, there will be a new log
file created. No way to continue the last one. That's why there could be
multiple log files, and no transaction. But if you haven't reached the
100.000 transactions (writes that is, reads doesn't count), there will be
no snapshot.

Regards,
Norbert

On Wed, Aug 14, 2019 at 2:35 PM Koen De Groote 
wrote:

> >Without a snapshot, we cannot delete the log files, as we would have no
> >means of recovery. txn logs applied to the snapshot gives us back the
> >state. Without snapshot, all txn logs needs to be "replayed" in a
> recovery.
> >And you need all the log files created since your last snapshot (in this
> >case, all the txn logs as there were no snapshots yet).
>
> Makes sense.
>
> In the heaviest environment I'm hitting around 200 requests per second,
> which all have to get data from zookeeper. Not sure what the impact is in
> terms of snapCount, I didn't set up the system myself and don't fully grasp
> the internals.
>
> As for the snapCount, that hasn't been touched, so that will be the default
> in my environments.
> I've read that the log files are preallocated. I see them as being 65MB a
> piece.
>
> Which makes me wonder: how many of those until the process hits 10
> snaps?
>
> auto-cleaning is setup, retainCount=3, purgeInterval=1
>
> Restarting the zookeeper process shouldn't affect this count, I think? It
> doesn't happen often, though it might on test environments.
>
>
>
> On Wed, Aug 14, 2019 at 2:06 PM Norbert Kalmar
> 
> wrote:
>
> > Hi,
> >
> > Without a snapshot, we cannot delete the log files, as we would have no
> > means of recovery. txn logs applied to the snapshot gives us back the
> > state. Without snapshot, all txn logs needs to be "replayed" in a
> recovery.
> > And you need all the log files created since your last snapshot (in this
> > case, all the txn logs as there were no snapshots yet).
> >
> > As for why there is no snapshot. What is your load? Per the admin guide:
> >
> > "snapCount
> > (Java system property: zookeeper.snapCount)
> > ZooKeeper logs transactions to a transaction log. After snapCount
> > transactions are written to a log file a snapshot is started and a new
> > transaction log file is created. The default snapCount is 100,000."
> >
> > By default there will be no auto-cleaning of the snapshot and log files.
> > Check the autopurge.snapRetainCount and autopurge.purgeInterval settings
> > for this.
> >
> > Regards,
> > Norbert
> >
> > On Wed, Aug 14, 2019 at 1:21 PM Koen De Groote <
> > koen.degro...@limecraft.com>
> > wrote:
> >
> > > Greetings all.
> > >
> > > I was debugging something an ran into this bit of code:
> > >
> > >
> >
> https://github.com/apache/zookeeper/blob/master/zookeeper-server/src/main/java/org/apache/zookeeper/server/PurgeTxnLog.java#L81
> > >
> > > If I understand it correctly, it seems that this means log.x files
> > will
> > > only get deleted if there's a snapshot.
> > >
> > > Which is troublesome, as my dataDir is filling up with log files but
> not
> > a
> > > single snapshot in sight.
> > >
> > > 1: Is this correct behavior? Both the logic of needing a snapshot and
> the
> > > fact that not snapshots are being generated?
> > >
> > > 2: While not having a fix for this, what would be useful to know is:
> can
> > > these log files be freely deleted? Or does the most recent one need to
> be
> > > kept, or how does it go with this files?
> > >
> > > I thought that running "bin/zkCleanup.sh /data -n 3" would clean up
> both
> > > the snapshots and the logs, but it appears that if there are not
> > snapshots,
> > > the logs aren't cleaned either.
> > >
> > > What are my options here?
> 

Jenkins build is back to normal : PreCommit-ZOOKEEPER-github-pr-build-maven #1122

[Apache Jenkins Server]

See 

Jenkins build became unstable: PreCommit-ZOOKEEPER-github-pr-build-maven #1123

[Apache Jenkins Server]

See 

ZooKeeper_branch35_jdk8 - Build # 1505 - Still Failing

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 71.04 KB...]
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.213 sec, Thread: 2, Class: org.apache.zookeeper.test.SaslSuperUserTest
[junit] Running org.apache.zookeeper.test.ServerCnxnTest in thread 2
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
3.416 sec, Thread: 2, Class: org.apache.zookeeper.test.ServerCnxnTest
[junit] Running org.apache.zookeeper.test.SessionInvalidationTest in thread 
2
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
2.478 sec, Thread: 2, Class: org.apache.zookeeper.test.SessionInvalidationTest
[junit] Running org.apache.zookeeper.test.SessionTest in thread 2
[junit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
14.067 sec, Thread: 2, Class: org.apache.zookeeper.test.SessionTest
[junit] Running org.apache.zookeeper.test.SessionTimeoutTest in thread 2
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
2.467 sec, Thread: 2, Class: org.apache.zookeeper.test.SessionTimeoutTest
[junit] Running org.apache.zookeeper.test.SessionTrackerCheckTest in thread 
2
[junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.13 sec, Thread: 2, Class: org.apache.zookeeper.test.SessionTrackerCheckTest
[junit] Running org.apache.zookeeper.test.SessionUpgradeTest in thread 2
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
24.25 sec, Thread: 2, Class: org.apache.zookeeper.test.SessionUpgradeTest
[junit] Running org.apache.zookeeper.test.StandaloneTest in thread 2
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
2.84 sec, Thread: 2, Class: org.apache.zookeeper.test.StandaloneTest
[junit] Running org.apache.zookeeper.test.StatTest in thread 2
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
2.61 sec, Thread: 2, Class: org.apache.zookeeper.test.StatTest
[junit] Running org.apache.zookeeper.test.StaticHostProviderTest in thread 2
[junit] Tests run: 26, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
2.623 sec, Thread: 2, Class: org.apache.zookeeper.test.StaticHostProviderTest
[junit] Running org.apache.zookeeper.test.StringUtilTest in thread 2
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.075 sec, Thread: 2, Class: org.apache.zookeeper.test.StringUtilTest
[junit] Running org.apache.zookeeper.test.SyncCallTest in thread 2
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.923 sec, Thread: 2, Class: org.apache.zookeeper.test.SyncCallTest
[junit] Running org.apache.zookeeper.test.TruncateTest in thread 2
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
115.127 sec, Thread: 3, Class: org.apache.zookeeper.test.RecoveryTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
108.376 sec, Thread: 4, Class: org.apache.zookeeper.test.RestoreCommittedLogTest
[junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
20.279 sec, Thread: 2, Class: org.apache.zookeeper.test.TruncateTest
[junit] Running org.apache.zookeeper.test.WatchEventWhenAutoResetTest in 
thread 3
[junit] Running org.apache.zookeeper.test.WatchedEventTest in thread 4
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.133 sec, Thread: 4, Class: org.apache.zookeeper.test.WatchedEventTest
[junit] Running org.apache.zookeeper.test.WatcherFuncTest in thread 2
[junit] Running org.apache.zookeeper.test.WatcherTest in thread 4
[junit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
5.722 sec, Thread: 2, Class: org.apache.zookeeper.test.WatcherFuncTest
[junit] Running org.apache.zookeeper.test.X509AuthTest in thread 2
[junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.104 sec, Thread: 2, Class: org.apache.zookeeper.test.X509AuthTest
[junit] Running org.apache.zookeeper.test.ZkDatabaseCorruptionTest in 
thread 2
[junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
14.43 sec, Thread: 2, Class: org.apache.zookeeper.test.ZkDatabaseCorruptionTest
[junit] Running org.apache.zookeeper.test.ZooKeeperQuotaTest in thread 2
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
23.464 sec, Thread: 3, Class: 
org.apache.zookeeper.test.WatchEventWhenAutoResetTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.222 sec, Thread: 2, Class: org.apache.zookeeper.test.ZooKeeperQuotaTest
[junit] Running org.apache.zookeeper.util.PemReaderTest in thread 3
[junit] Running org.apache.jute.BinaryInputArchiveTest in thread 2

[jira] [Created] (ZOOKEEPER-3509) Revisit log format

[TisonKun (JIRA)]

TisonKun created ZOOKEEPER-3509:
---

 Summary: Revisit log format
 Key: ZOOKEEPER-3509
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3509
 Project: ZooKeeper
  Issue Type: Improvement
  Components: server
Reporter: TisonKun


Currently ZooKeeper mixes up different log format and even a number of log 
statements are buggy. It is an opportunity that we revisit log format in 
ZooKeeper and do a pass to fix all log format related issues.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Build failed in Jenkins: PreCommit-ZOOKEEPER-github-pr-build-maven #1125

[Apache Jenkins Server]

See 


--
[...truncated 436.25 KB...]
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/asm/asm/3.3.1/asm-3.3.1.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/asm/asm/3.3.1/asm-3.3.1.pom (266 B at 27 
kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/asm/asm-parent/3.3.1/asm-parent-3.3.1.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/asm/asm-parent/3.3.1/asm-parent-3.3.1.pom 
(4.3 kB at 361 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/net/minidev/json-smart/2.0-RC2/json-smart-2.0-RC2.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/net/minidev/json-smart/2.0-RC2/json-smart-2.0-RC2.pom
 (1.4 kB at 142 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/net/minidev/parent/2.0-RC2/parent-2.0-RC2.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/net/minidev/parent/2.0-RC2/parent-2.0-RC2.pom
 (11 kB at 1.0 MB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/net/minidev/json-smart/2.0-RC3/json-smart-2.0-RC3.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/net/minidev/json-smart/2.0-RC3/json-smart-2.0-RC3.pom
 (1.4 kB at 142 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/net/minidev/parent/2.0-RC3/parent-2.0-RC3.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/net/minidev/parent/2.0-RC3/parent-2.0-RC3.pom
 (8.4 kB at 840 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/net/minidev/asm/1.0-RC3/asm-1.0-RC3.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/net/minidev/asm/1.0-RC3/asm-1.0-RC3.pom 
(1.6 kB at 142 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/net/minidev/json-smart/2.0/json-smart-2.0.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/net/minidev/json-smart/2.0/json-smart-2.0.pom
 (1.4 kB at 142 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/net/minidev/parent/2.0/parent-2.0.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/net/minidev/parent/2.0/parent-2.0.pom (8.6 
kB at 660 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/net/minidev/asm/1.0/asm-1.0.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/net/minidev/asm/1.0/asm-1.0.pom (1.6 kB at 
145 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/net/minidev/json-smart/2.1.0/json-smart-2.1.0.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/net/minidev/json-smart/2.1.0/json-smart-2.1.0.pom
 (2.2 kB at 197 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/net/minidev/parent/2.1.0/parent-2.1.0.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/net/minidev/parent/2.1.0/parent-2.1.0.pom 
(8.6 kB at 785 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/net/minidev/asm/1.0.2/asm-1.0.2.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/net/minidev/asm/1.0.2/asm-1.0.2.pom (1.8 
kB at 163 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/net/minidev/json-smart/2.1.1/json-smart-2.1.1.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/net/minidev/json-smart/2.1.1/json-smart-2.1.1.pom
 (2.2 kB at 201 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/net/minidev/json-smart/2.2/json-smart-2.2.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/net/minidev/json-smart/2.2/json-smart-2.2.pom
 (2.3 kB at 210 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/net/minidev/minidev-parent/2.2/minidev-parent-2.2.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/net/minidev/minidev-parent/2.2/minidev-parent-2.2.pom
 (9.1 kB at 828 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/net/minidev/accessors-smart/1.1/accessors-smart-1.1.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/net/minidev/accessors-smart/1.1/accessors-smart-1.1.pom
 (2.1 kB at 190 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/org/ow2/asm/asm/5.0.3/asm-5.0.3.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/org/ow2/asm/asm/5.0.3/asm-5.0.3.pom (1.9 
kB at 176 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/org/ow2/asm/asm-parent/5.0.3/asm-parent-5.0.3.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/org/ow2/asm/asm-parent/5.0.3/asm-parent-5.0.3.pom
 (5.5 kB at 500 kB/s)
[INFO] Downloading from central: 

Re: Code to clean up transaction logs needs snapshots before it works?

[Koen De Groote]

Al right, I'll try and go forward with that info. Thanks.

On Wed, Aug 14, 2019 at 2:55 PM Norbert Kalmar 
wrote:

> Read doesn't matter, there will be no txn logs for read. Only modifications
> are logged (state changes to the datatree).
>
> As for why all txn logs are 64MB:
> "preAllocSize
> (Java system property: zookeeper.preAllocSize)
> To avoid seeks ZooKeeper allocates space in the transaction log file in
> blocks of preAllocSize kilobytes. The default block size is 64M. One reason
> for changing the size of the blocks is to reduce the block size if
> snapshots are taken more often. (Also, see snapCount)."
>
> Note that all txn is written to one log file. That's why it is 64MB by
> default.
> I didn't check which version of admin guide I quoted, but here is the one
> from 3.4.13:
>
> snapCount
> ZooKeeper records its transactions using snapshots and a transaction log
> (think write-ahead log).The number of transactions recorded in the
> transaction log before a snapshot can be taken (and the transaction log
> rolled) is determined by snapCount. In order to prevent all of the machines
> in the quorum from taking a snapshot at the same time, each ZooKeeper
> server will take a snapshot when the number of transactions in the
> transaction log reaches a runtime generated random value in the
> [snapCount/2+1, snapCount] range.The default snapCount is 100,000.
>
> I'm not sure without checking the code what happens if preAllocSize is
> filled (new log file I think), but after a restart, there will be a new log
> file created. No way to continue the last one. That's why there could be
> multiple log files, and no transaction. But if you haven't reached the
> 100.000 transactions (writes that is, reads doesn't count), there will be
> no snapshot.
>
> Regards,
> Norbert
>
> On Wed, Aug 14, 2019 at 2:35 PM Koen De Groote <
> koen.degro...@limecraft.com>
> wrote:
>
> > >Without a snapshot, we cannot delete the log files, as we would have no
> > >means of recovery. txn logs applied to the snapshot gives us back the
> > >state. Without snapshot, all txn logs needs to be "replayed" in a
> > recovery.
> > >And you need all the log files created since your last snapshot (in this
> > >case, all the txn logs as there were no snapshots yet).
> >
> > Makes sense.
> >
> > In the heaviest environment I'm hitting around 200 requests per second,
> > which all have to get data from zookeeper. Not sure what the impact is in
> > terms of snapCount, I didn't set up the system myself and don't fully
> grasp
> > the internals.
> >
> > As for the snapCount, that hasn't been touched, so that will be the
> default
> > in my environments.
> > I've read that the log files are preallocated. I see them as being 65MB a
> > piece.
> >
> > Which makes me wonder: how many of those until the process hits 10
> > snaps?
> >
> > auto-cleaning is setup, retainCount=3, purgeInterval=1
> >
> > Restarting the zookeeper process shouldn't affect this count, I think? It
> > doesn't happen often, though it might on test environments.
> >
> >
> >
> > On Wed, Aug 14, 2019 at 2:06 PM Norbert Kalmar
> > 
> > wrote:
> >
> > > Hi,
> > >
> > > Without a snapshot, we cannot delete the log files, as we would have no
> > > means of recovery. txn logs applied to the snapshot gives us back the
> > > state. Without snapshot, all txn logs needs to be "replayed" in a
> > recovery.
> > > And you need all the log files created since your last snapshot (in
> this
> > > case, all the txn logs as there were no snapshots yet).
> > >
> > > As for why there is no snapshot. What is your load? Per the admin
> guide:
> > >
> > > "snapCount
> > > (Java system property: zookeeper.snapCount)
> > > ZooKeeper logs transactions to a transaction log. After snapCount
> > > transactions are written to a log file a snapshot is started and a new
> > > transaction log file is created. The default snapCount is 100,000."
> > >
> > > By default there will be no auto-cleaning of the snapshot and log
> files.
> > > Check the autopurge.snapRetainCount and autopurge.purgeInterval
> settings
> > > for this.
> > >
> > > Regards,
> > > Norbert
> > >
> > > On Wed, Aug 14, 2019 at 1:21 PM Koen De Groote <
> > > koen.degro...@limecraft.com>
> > > wrote:
> > >
> > > > Greetings all.
> > > >
> > > > I was debugging something an ran into this bit of code:
> > > >
> > > >
> > >
> >
> https://github.com/apache/zookeeper/blob/master/zookeeper-server/src/main/java/org/apache/zookeeper/server/PurgeTxnLog.java#L81
> > > >
> > > > If I understand it correctly, it seems that this means log.x
> files
> > > will
> > > > only get deleted if there's a snapshot.
> > > >
> > > > Which is troublesome, as my dataDir is filling up with log files but
> > not
> > > a
> > > > single snapshot in sight.
> > > >
> > > > 1: Is this correct behavior? Both the logic of needing a snapshot and
> > the
> > > > fact that not snapshots are being generated?
> > > >
> > > > 2: While not having a fix for this, what would be 

Jenkins build is back to normal : PreCommit-ZOOKEEPER-github-pr-build-maven #1126

[Apache Jenkins Server]

See 

Re: Code to clean up transaction logs needs snapshots before it works?

[Ted Dunning]

On Wed, Aug 14, 2019 at 5:35 AM Koen De Groote 
wrote:

> ...
> I've read that the log files are preallocated. I see them as being 65MB a
> piece.
>

Yes. Preallocation of logs is an important performance trick.

The point is that if a file doesn't change length when you write to it,
then the file attributes don't have to change. Writing file attributes can
be as expensive as writing the data and, in any case, isn't free and it has
forced ordering.

[jira] [Created] (ZOOKEEPER-3508) Strategy on line break

[TisonKun (JIRA)]

TisonKun created ZOOKEEPER-3508:
---

 Summary: Strategy on line break
 Key: ZOOKEEPER-3508
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3508
 Project: ZooKeeper
  Issue Type: Improvement
Reporter: TisonKun


While enabling checkstyle configuration on zookeeper-server module, it raises 
the discussion that how we generally break/wrap long lines. Whether or not we 
introduce a standard and if so, how we ensure it is obeyed.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Build failed in Jenkins: PreCommit-ZOOKEEPER-github-pr-build-maven #1124

[Apache Jenkins Server]

See 


--
[...truncated 436.30 KB...]
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/asm/asm/3.3.1/asm-3.3.1.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/asm/asm/3.3.1/asm-3.3.1.pom (266 B at 19 
kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/asm/asm-parent/3.3.1/asm-parent-3.3.1.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/asm/asm-parent/3.3.1/asm-parent-3.3.1.pom 
(4.3 kB at 361 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/net/minidev/json-smart/2.0-RC2/json-smart-2.0-RC2.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/net/minidev/json-smart/2.0-RC2/json-smart-2.0-RC2.pom
 (1.4 kB at 129 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/net/minidev/parent/2.0-RC2/parent-2.0-RC2.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/net/minidev/parent/2.0-RC2/parent-2.0-RC2.pom
 (11 kB at 738 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/net/minidev/json-smart/2.0-RC3/json-smart-2.0-RC3.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/net/minidev/json-smart/2.0-RC3/json-smart-2.0-RC3.pom
 (1.4 kB at 102 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/net/minidev/parent/2.0-RC3/parent-2.0-RC3.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/net/minidev/parent/2.0-RC3/parent-2.0-RC3.pom
 (8.4 kB at 646 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/net/minidev/asm/1.0-RC3/asm-1.0-RC3.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/net/minidev/asm/1.0-RC3/asm-1.0-RC3.pom 
(1.6 kB at 142 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/net/minidev/json-smart/2.0/json-smart-2.0.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/net/minidev/json-smart/2.0/json-smart-2.0.pom
 (1.4 kB at 129 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/net/minidev/parent/2.0/parent-2.0.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/net/minidev/parent/2.0/parent-2.0.pom (8.6 
kB at 780 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/net/minidev/asm/1.0/asm-1.0.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/net/minidev/asm/1.0/asm-1.0.pom (1.6 kB at 
145 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/net/minidev/json-smart/2.1.0/json-smart-2.1.0.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/net/minidev/json-smart/2.1.0/json-smart-2.1.0.pom
 (2.2 kB at 197 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/net/minidev/parent/2.1.0/parent-2.1.0.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/net/minidev/parent/2.1.0/parent-2.1.0.pom 
(8.6 kB at 508 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/net/minidev/asm/1.0.2/asm-1.0.2.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/net/minidev/asm/1.0.2/asm-1.0.2.pom (1.8 
kB at 48 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/net/minidev/json-smart/2.1.1/json-smart-2.1.1.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/net/minidev/json-smart/2.1.1/json-smart-2.1.1.pom
 (2.2 kB at 170 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/net/minidev/json-smart/2.2/json-smart-2.2.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/net/minidev/json-smart/2.2/json-smart-2.2.pom
 (2.3 kB at 193 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/net/minidev/minidev-parent/2.2/minidev-parent-2.2.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/net/minidev/minidev-parent/2.2/minidev-parent-2.2.pom
 (9.1 kB at 828 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/net/minidev/accessors-smart/1.1/accessors-smart-1.1.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/net/minidev/accessors-smart/1.1/accessors-smart-1.1.pom
 (2.1 kB at 190 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/org/ow2/asm/asm/5.0.3/asm-5.0.3.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/org/ow2/asm/asm/5.0.3/asm-5.0.3.pom (1.9 
kB at 161 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/org/ow2/asm/asm-parent/5.0.3/asm-parent-5.0.3.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/org/ow2/asm/asm-parent/5.0.3/asm-parent-5.0.3.pom
 (5.5 kB at 423 kB/s)
[INFO] Downloading from central: 

Re: [jira] [Updated] (ZOOKEEPER-1112) Add support for C client for SASL authentication

[Damien Diederen]

Greetings, all,

Note sure how notifications work on this project, but in case it did not
pop up on your radar: I have picked up ZOOKEEPER-1112, which was dormant
since 2011, and pushed a first set of patches:

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

Reviews and/or comments would be very welcome!

Thanks,
Damien Diederen

Re: [jira] [Updated] (ZOOKEEPER-1112) Add support for C client for SASL authentication

[Ted Dunning]

Kudos to you for this!



On Wed, Aug 14, 2019 at 10:55 AM Damien Diederen 
wrote:

>
> Greetings, all,
>
> Note sure how notifications work on this project, but in case it did not
> pop up on your radar: I have picked up ZOOKEEPER-1112, which was dormant
> since 2011, and pushed a first set of patches:
>
> https://github.com/apache/zookeeper/pull/1054
>
> Reviews and/or comments would be very welcome!
>
> Thanks,
> Damien Diederen
>

Jenkins build is unstable: zookeeper-master-maven-jdk12 #93

[Apache Jenkins Server]

See