Skip to content

20.3.0: Make lock-timeout for event submission configurable

Choose a tag to compare

View all tags
@ePaul ePaul released this 06 May 16:27
· 109 commits to master since this release
20.3.0
c08646f
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

This version is for Spring-Boot 2.

Feature (#120): Configurable lock timeout

When sending events out, we are first locking them for some time so no other process running the same library is trying to send out the same events. With this change, the time for which those events are locked is configurable, which is helpful for applications with low latency and high volume requirements.
Look for lock-duration and lock-duration-buffer in the README if you want to use this feature.

No migration is needed, the default settings behave as before (but might change in the future).

Benchmark (#83): We also got a nakadi-producer-load-test subproject, which allows to measure how fast large quantities of events can be submitted (using a locally running Nakadi instance).
See the README in that sub-project folder for how to use it.

Assets 2
Loading