NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
NuGet
The TigerBeetle client for C# and .NET
Latest stable
0.17.9
Last release 4 months ago
06 Jul 2026
Ships on a steady schedule
a new release about every 2 weeks
Nearly every release is documented
notes for 60 of the last 60 stable releases
1 version withdrawn
withdrawn after publishing
127 years old
300 releases · first in 1900
Drag across the ruler to compare, or tap a release to open it.
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.23
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.23
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.28docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.28-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
You cannot run a newer client against an older cluster: clients are only compatible
with replicas from their own release or newer, subject to the newer release's
Oldest supported client version.
dotnet add package tigerbeetle --version 0.16.28go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.16.28com.tigerbeetle.tigerbeetle-java in pom.xml
to 0.16.28.npm install --save-exact tigerbeetle-node@0.16.28pip install tigerbeetle==0.16.28Note: Before performing this upgrade, please make sure to check that no replicas are lagging and state syncing.
You can ensure this by temporarily pausing load to the TigerBeetle cluster and waiting for all
replicas to catch up. If some replicas in your cluster were indeed lagging, you should see
on_repair_sync_timeout: request sync; lagging behind cluster in the logs, followed by
sync: ops=, which indicates the end of state sync. If you don't see the former in the logs, then
you are already safe to upgrade!
This is to work around an issue in the upgrade between 0.16.25 → 0.16.26, wherein a state syncing replica goes into a crash loop when it upgrades to 0.16.26. If one of your replicas has already hit this crash loop, please reach out to us on the Community Slack so we can help you safely revive it.
Test misdirected writes in the VOPR.
Fix a recovery correctness bug caused by a misdirected write in the WAL (discovered by the VOPR in #2677).
Refactor the tb_client packet interface, hiding private members in an opaque field. Add assertions to enforce expectations for each packet field.
Fix a Node client crash when it was closed with outstanding requests.
Flush loopback queue before queueing another prepare_ok.
Fuzzer weights are now configurable.
The REPL now uses StaticAllocator on init and deinit.
tigerbeetle inspect constants now prints a napkin math estimate for the memory usage.
Update docs with new talks, an updated illustration, and a new Slack invite link.
Don't expose VSR module to dependents in build.zig.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Remove the deprecated version of the start_view message.
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.21
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.27docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.27-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
You cannot run a newer client against an older cluster: clients are only compatible
with replicas from their own release or newer, subject to the newer release's
Oldest supported client version.
dotnet add package tigerbeetle --version 0.16.27go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.16.27com.tigerbeetle.tigerbeetle-java in pom.xml
to 0.16.27.npm install --save-exact tigerbeetle-node@0.16.27pip install tigerbeetle==0.16.27Note: Before performing this upgrade, please make sure to check that no replicas are lagging and state syncing.
You can ensure this by temporarily pausing load to the TigerBeetle cluster and waiting for all
replicas to catch up. If some replicas in your cluster were indeed lagging, you should see
on_repair_sync_timeout: request sync; lagging behind cluster in the logs, followed by
sync: ops=, which indicates the end of state sync. If you don't see the former in the logs, then
you are already safe to upgrade!
This is to work around an issue in the upgrade between 0.16.25 → 0.16.26, wherein a state syncing replica goes into a crash loop when it upgrades to 0.16.26. If one of your replicas has already hit this crash loop, please reach out to us on the Community Slack so we can help you safely revive it.
Remove redundant calls to IO.init() and IO.deinit() during the format and start commands.
These redundant calls could lead to an assertion error in the Zig standard library when a failure
occurs after the second IO.init().
Enhance the docs search bar with arrow-key navigation over search results, and folder collapse using the enter key.
Add talks from SystemsDistributed '23, P99 CONF '23, Money2020 '24, and SYCL '24.
Improve CPU utilization of the CFO by spawning fuzzers more frequently.
Motivated by the measurement that the cumulative CPU was (on average) 40-45% idle.
Assert zeroed padding for WAL prepares in the VOPR.
Remove the deprecated version of the start_view message.
As part of #2600, we rolled out a new on-disk format for the CheckpointState. To avoid bumping the VSR version, we made it so that replicas temporarily send two versions of the start_view message, with both the old and new CheckpointState formats.
Add fair scheduler to the CFO to avoid starvation of short running fuzzers.
Earlier, long running LSM fuzzers ended up spending more than their fair share of time on the CPU, with only 1-10% of CFO time being spent on short running VOPR fuzzers.
<img width="3508" height="1973" alt="ReleaseNotes_0 16 27" src="https://github.com/user-attachments/assets/9e532331-8e19-482d-a609-60b186296201" />
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.20
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.20
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.26docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.26-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
You cannot run a newer client against an older cluster: clients are only compatible
with replicas from their own release or newer, subject to the newer release's
Oldest supported client version.
dotnet add package tigerbeetle --version 0.16.26go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.16.26com.tigerbeetle.tigerbeetle-java in pom.xml
to 0.16.26.npm install --save-exact tigerbeetle-node@0.16.26pip install tigerbeetle==0.16.26Note: Before performing this upgrade, please make sure to check that no replicas are lagging and state syncing.
You can ensure this by temporarily pausing load to the TigerBeetle cluster and waiting for all
replicas to catch up. If some replicas in your cluster were indeed lagging, you should see
on_repair_sync_timeout: request sync; lagging behind cluster in the logs, followed by
sync: ops=, which indicates the end of state sync. If you don't see the former in the logs, then
you are already safe to upgrade!
This is to work around an issue in the upgrade between 0.16.25 → 0.16.26, wherein a state syncing replica goes into a crash loop when it upgrades to 0.16.26. If one of your replicas has already hit this crash loop, please reach out to us on the Community Slack so we can help you safely revive it.
Consider blocks and prepares with nonzero padding to be corrupt. Previously blocks asserted zero padding, which can fail due to bitrot.
Also fix a similar bug in the superblock copy index handling. The copy index is not covered by a checksum, so we must treat it carefully to avoid propagating bad data if it is corrupt.
VOPR now injects single-bit errors into storage rather than whole-sector errors.
The current checkpoint process immediately frees all blocks released in the previous checkpoint. This can lead to cluster unavailability by prematurely freeing and overwriting released blocks.
To fix this, delay freeing blocks until the checkpoint is durable on a commit-quorum, ensuring data integrity and preventing single-replica failures (in a 3 node cluster) from impacting availability.
When state syncing, replicas would send prepare_oks only up to a point, to ensure they don't falsely contribute to the durability of a non-durable checkpoint they've synced to.
However, the logic to send these prepare_oks after state sync has finished was missing, which could lead to a situation where a primary was unavailable to advance. Add in the ability to send these prepare_oks after syncing.
Recently, tb_client was reworked to use OS native signals instead of a socket for delivering cross thread events.
Fix some incorrect asserts, and add a fuzz test.
#2694, #2695, #2686, #2688, #2685, #2676, #2684
A few fixes and an "Edit this page" button for our new docs!
Allocate the reply buffer in the Go client once the reply has been received. This can save up to 1MB of memory.
Refactor parts of our CFO, the process responsible for running fuzzers and the VOPR and sending the results to devhub, to better handle OOM in subprocesses and reduce false fuzz failures.
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.19
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.19
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.25docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.25-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
You cannot run a newer client against an older cluster: clients are only compatible
with replicas from their own release or newer, subject to the newer release's
Oldest supported client version.
dotnet add package tigerbeetle --version 0.16.25go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.16.25com.tigerbeetle.tigerbeetle-java in pom.xml
to 0.16.25.npm install --save-exact tigerbeetle-node@0.16.25pip install tigerbeetle==0.16.25Avoid considering just-repaired journal headers as faulty during WAL recovery.
Reduce the minimum exponential backoff delay from 100ms (which is too pessimistic) to 10ms, a value more appropriate for fast networks.
Introduce a new CheckpointState format on disk, which ensures that blocks released during
a checkpoint are freed only when the next checkpoint is durable, solving a known
liveness issue.
The previous format is still supported and will be removed in a future release to ensure the
proper upgrade path.
Demote a clock skew warning to a debug message when the ping time is legitimately behind the window. On the other hand, assert that the monotonic clock is within the window.
Workaround to prevent the initialization value for the AOF message from being embedded as a
binary resource, saving constants.message_size_max bytes in the executable size!
Fix a VOPR false positive where it erroneously infers that a replica has lost a prepare that it has acknowledged.
New statically generated docs website, featuring many UX improvements while removing tons of dependencies! Check it out at https://docs.tigerbeetle.com/
Make the CFO utilize all cores all the time for running tests, pushing updates every 5 minutes.
Nothing published for this version
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.18
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.18
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.23docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.23-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
You cannot run a newer client against an older cluster: clients are only compatible
with replicas from their own release or newer, subject to the newer release's
Oldest supported client version.
dotnet add package tigerbeetle --version 0.16.23go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.16.23com.tigerbeetle.tigerbeetle-java in pom.xml
to 0.16.23.npm install --save-exact tigerbeetle-node@0.16.23pip install tigerbeetle==0.16.23Fix Python client initialization with long address strings.
Prevent Client IO thread starvation.
Set prepare/request timeout RTTs dynamically. Previously our backoff was almost always much too high, leading to much lower throughput when ring replication failed.
Add --clients flag to tigerbeetle benchmark for generating load from multiple concurrent
clients.
For test/verify only functions, assert constants.verify at compile-time, not runtime.
Fix flaky Java client test testConcurrentInterruptedTasks.
Fix VOPR false positive due to smallest_missing_prepare_between bug.
In clients, add Events for efficient cross-thread notification.
Devhub fixes due to Ubuntu/kcov.
Nothing published for this version
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.17
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.17
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.21docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.21-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
You cannot run a newer client against an older cluster: clients are only compatible
with replicas from their own release or newer, subject to the newer release's
Oldest supported client version.
dotnet add package tigerbeetle --version 0.16.21go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.16.21com.tigerbeetle.tigerbeetle-java in pom.xml
to 0.16.21.npm install --save-exact tigerbeetle-node@0.16.21pip install tigerbeetle==0.16.21Happy 2025!
Fix multiple VOPR false positives
Disable costly cache map verification: trust, verify, but mind big-O!
Improve state sync performance by getting rid of awaiting_checkpoint state.
Improve VOPR coverage when running out of IOPs.
#2593, #2623, #2625, #2626, #2627, #2628
Improve WAL repair performance.
Improve replication performance.
Add simple metrics to the state machine.
Greatly improve performance of append-only file (AOF). Note that this changes format of AOF on disk.
Add tigerbeetle inspect constants command to visualize important compile-time parameters.
Use asynchronous disk IO on Windows (as a reminder, at the moment TigerBeetle server is considered to production-ready only on Linux).
Add experimental alternative replication topologies (star and closed loop).
Move RingBufferType into stdx, TigerBeetle's extended standard library.
Run go vet on CI.
Fix tracing compatibility with perfetto.
Make it easier to investigate Vortex runs.
Correctly calculate the number of results in the Go client. Previously, the answer was correct despite the logic being wrong!
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.16
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.16
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.20docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.20-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
You cannot run a newer client against an older cluster: clients are only compatible
with replicas from their own release or newer, subject to the newer release's
Oldest supported client version.
dotnet add package tigerbeetle --version 0.16.20go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.16.20com.tigerbeetle.tigerbeetle-java in pom.xml
to 0.16.20.npm install --save-exact tigerbeetle-node@0.16.20pip install tigerbeetle==0.16.20Improve replication reliability for tiny messages.
Add info-level logging for basic progress events.
Add logging and runtime configuration parameters for state sync.
Fix fuzz_lsm_scan checkpoint schedule.
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.14
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.14
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.19docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.19-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
You cannot run a newer client against an older cluster: clients are only compatible
with replicas from their own release or newer, subject to the newer release's
Oldest supported client version.
dotnet add package tigerbeetle --version 0.16.19go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.16.19com.tigerbeetle.tigerbeetle-java in pom.xml
to 0.16.19.npm install --save-exact tigerbeetle-node@0.16.19pip install tigerbeetle==0.16.19Coalesce LSM tables in memory before writing them to disk. This significantly improves workloads with small batch sizes, that would otherwise churn in the top level of the LSM while incurring heavy write amplification.
TigerBeetle recently gained the ability to do runtime debug logging with --log-debug. Extend
that to other subcommands - not just start.
Additionally, the Python client now has logs integrated with Python's native logging module,
which means no more printing to stderr!
Fix broken links to TigerBeetle blog posts, thanks @PThorpe92!
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.13
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.13
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.18docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.18-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
You cannot run a newer client against an older cluster: clients are only compatible
with replicas from their own release or newer, subject to the newer release's
Oldest supported client version.
dotnet add package tigerbeetle --version 0.16.18go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.16.18com.tigerbeetle.tigerbeetle-java in pom.xml
to 0.16.18.npm install --save-exact tigerbeetle-node@0.16.18pip install tigerbeetle==0.16.18Our repair can create a feedback loop. Repair requests prepares and headers, but, upon receiving back, we re-trigger repair, which could lead to duplicate repair work.
To avoid that, make sure that we are not sending more than two repair messages per replica per our repair timeout.
Trace AOF write duration
Timeouts with exponential backoff should reset to their original delay when the timeout is stopped.
Assert against ABA problem during commit.
Add retry for flock. flocks are cleaned up by the kernel when the file descriptor is closed,
but since that file descriptor is used by io_uring, it actually outlives the process itself.
Fix mlock flag value.
Don't crash if a round of view changes happened while repairing the pipeline.
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.12
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.12
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.17docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.17-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.16.17go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.16.17com.tigerbeetle.tigerbeetle-java in pom.xml
to 0.16.17.npm install tigerbeetle-node@0.16.17This release includes a correctness fix for the preview API get_account_balances,
get_account_transfers, query_accounts, and query_transfers. If your application uses these
features it might be affected.
Fix correctness bug which affected the preview get_account_balances, get_account_transfers,
query_accounts, and query_transfers queries. Specifically, if several filters are used (that
is, several fields in QueryFilter or AccountFilter are set), then some objects might be
missing from the result set.
The underlying data is safely stored in the database, so re-running these queries using the new version of TigerBeetle will give correct results.
Fix panic in the node client which occurred on eviction.
Fix incorrect ABI used on aarch64 for the client library. To prevent such issues from cropping up in the future, add aarch64 testing to CI.
Add extra assertions to verify object cache consistency.
Implement network fault injection in Vörtex, our non-deterministic whole system simulator.
Log level can now be specified at runtime.
Log messages now include UTC timestamp (formatted as per RFC 3339).
Relax compiler requirements for building TigerBeetle. While we only support building using one
specific version of Zig, the one downloaded via ./zig/download.sh, you can try using other
versions.
Document how to handle errors during release. TigerBeetle's release process is complicated, as we
need to release, in lockstep, both the tigerbeetle binary and all the related client libraries.
The release process is intentionally designed to be "highly-available", such that a failure of any
aspect of a release can be safely detected, isolated, and repaired. But, so far, this wasn't
clearly spelled out in the documentation!
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.11
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.11
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.16docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.16-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.16.16go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.16.16com.tigerbeetle.tigerbeetle-java in pom.xml
to 0.16.16.npm install tigerbeetle-node@0.16.16The highlight of today's release is the new official Python client, implemented in #2527, and #2487. Please kick the tires!
Require that all replicas in a cluster have the latest TigerBeetle binary as a precondition for an upgrade.
Fix several bugs when handling misdirected writes. That is, situations when the disk reports a write as successful, despite the write ending up in the wrong place on the disk!
Make sure that TigerBeetle memory is not swappable, otherwise a storage fault can occur in a currently swapped-out page, circumventing TigerBeetle guarantees.
REPL correctly emits errors when several objects are used as an argument of an operation that
only works for a single object, like get_account_transfers.
Add randomized integration tests for the Java client.
Ignore OOM failures during fuzzing. Fuzzers normally don't use that much memory, but, depending on random parameters selected by swarm testing, there are big outliers. If all concurrent fuzzers hit a seed that requires a lot of memory, a fuzzing machine runs out of physical RAM. Handle such errors and don't treat them as fuzzing failures.
Track the number of untriaged issues on DevHub.
Nothing published for this version
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.10
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.10
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.14docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.14-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.16.14go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.16.14com.tigerbeetle.tigerbeetle-java in pom.xml
to 0.16.14.npm install tigerbeetle-node@0.16.14Call DetachCurrentThread when the Java client is closed. The underlying Zig TigerBeetle client
runs in a separate thread internally, and a handler to this thread was being leaked.
This is not noticeable in normal operation, but could impact long running processes that create and close clients frequently.
Document that it's not possible to currently look up or query more than a full batch of accounts atomically without using the history flag and querying balances.
Add the ability to check timestamp order - and verify they are monotonically increasing - for accounts and transfers inside Vortex.
Recently the VOPR has gotten too good, and it's very tempting to switch to an empirical mode of coding: write some code and let the VOPR figure out whether it is correct or not.
This is suboptimal - silence of the VOPR doesn't guarantee total absence of bugs and safety comes in layers and cross checks. Just formal or informal reasoning is not enough, we need both.
Document this in TigerStyle.
Previously, the Zig part of languages clients logged directly to stderr using Zig's std.log, but
since directly outputting to stderr is considered rude for a library, logging was disabled.
This PR adds in scaffolding for sending these logs to the client language to be handled there, tying in with native log libraries (eg, Log4j). No languages use it yet, however.
Additionally, log warn and err directly to stderr, if there's no handler.
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.9
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.9
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.13docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.13-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.16.13go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.16.13com.tigerbeetle.tigerbeetle-java in pom.xml
to 0.16.13.npm install tigerbeetle-node@0.16.13Fix a broken assert when a recently-state-synced replica that has not completed journal repair
receives an old commit message.
Retry EAGAIN on (disk) reads. This is essential for running TigerBeetle on XFS, since XFS
returns EAGAIN unexpectedly.
Fix a message bus crash when a client reconnects to a replica without the replica receiving a disconnect for the first connection.
Save 256KiB of RAM by not having a prefetch cache for historical balances. (Historical balances are never prefetched, so this cache was unused.)
Update hardware requirements in the documentation to include the recommended network bandwidth, advice for very large data files, and farther emphasis on the importance of ECC RAM.
Don't panic the client when the client's session is
evicted.
Instead, report an error any time a new batch is submitted to the evicted client.
(How the error is reported depends on the client language – e.g. Java throws an exception, whereas
Node.js rejects the Promise).
Note that if running clients are evicted, that typically indicates that there are too many clients running – check out the suggested system architecture.
Add REPL interactivity. Also change the REPL from dynamic to static allocation. Thanks @wpaulino!
Expose the VSR timestamp to the client. (This is an experimental feature which will be removed soon – don't use this!)
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.8
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.8
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.12docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.12-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.16.12go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.16.12com.tigerbeetle.tigerbeetle-java in pom.xml
to 0.16.12.npm install tigerbeetle-node@0.16.12Fix an attempt to access uninitialized fields of tb_packet_t when tb_client_deinit aborts
pending requests. Also add Java unit tests to reproduce the problem and validate the fix.
Fix a liveness issue where the cluster gets stuck despite sufficient durability, caused by buggy
logic for cycling through faulty blocks during repair. Now, we divide the request buffer between
the read_global_queue and faulty_blocks, ensuring that we always request blocks from both.
Update DevHub styling.
Vortex can now not only crash replicas (by killing and restarting the process) but also stop and resume them.
Fix the Dotnet walkthrough example that misused length instead of the final index when slicing
an array. Thanks @tenatus for reporting it!
Fix a CI failure caused by concurrent processes trying to create the fs_supports_direct_io
probe file in the same path.
Replace curl shell invocation with Zig's http client. 😎
Properly handle "host unreachable" (EHOSTUNREACH) on Linux, instead of returning unexpected
error.
#2443, #2451, #2459, #2460, #2465
Various code refactorings to improve naming conventions, readability, and organization.
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.4
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.4
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.11docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.11-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.16.11go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.16.11com.tigerbeetle.tigerbeetle-java in pom.xml
to 0.16.11.npm install tigerbeetle-node@0.16.11Make Grid.reserve() abort rather than returning null.
When Grid.reserve() aborts, that indicates that the data file size limit would be exceeded by
the reservation. We were already panicking in this case by unwrapping the result, but now it has
a useful error message.
Improve availability and performance by sending start_view message earlier in the new-primary
recovery – as soon as the journal headers are repaired.
Refactor compaction to clarify the scheduling logic, schedule more aggressively, and make it easier to run multiple compactions concurrently. This also improved the benchmark performance.
Support multiversion (non-automatic) upgrades when the replica is started with --development
or --experimental.
Allow a release's Git tag and config.process.release to differ. This simplifies the release
process for hotfixes, when the Git tag is bumped but the config.process.release is unchanged.
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.3
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.3
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.10docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.10-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.16.10go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.16.10com.tigerbeetle.tigerbeetle-java in pom.xml
to 0.16.10.npm install tigerbeetle-node@0.16.10Improve performance & availability during view change by ensuring a replica only repairs the portion of the WAL that is required to become primary, instead of repairing it in its entirety.
Add a unit test for Zig's stdlib sort.
Stable sort is critical for compaction correctness. Zig stdlib does have a sort fuzz test, but it doesn't cover the presorted subarray case, and doesn't check arrays much larger than the sort algorithm's on-stack cache.
Fix a bug in the MessageBus wherein connections weren't being terminated during client teardown.
Fix a bug in the benchmark wherein the usage of --account-count-hot was broken when used in
conjunction with the uniform distribution.
Revamp the core_missing_prepares liveness-mode check to correctly check for the prepares that a
replica should repair (after #2414).
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.2
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.2
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.9docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.9-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.16.9go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.16.9com.tigerbeetle.tigerbeetle-java in pom.xml
to 0.16.9.npm install tigerbeetle-node@0.16.9TigerBeetle clients internally batch operations for improved performance. Fix a bug where an unclosed link chain could be batched before another linked chain, causing them to be treated as one long linked chain. Additionally, prevent non-batchable requests from sharing packets entirely.
AMOUNT_MAX is used as a sentinel value for things like balancing transfers to specify moving
as much as possible. Correct and fix its value in the Java client. Thanks @tKe!
Improve the benchmark by adding Zipfian distributed random numbers, to better simulate realistic conditions and as a precursor to approximating YCSB.
Previously, TigerBeetle's clients disallowed empty batches locally, before the request was even sent to the cluster. However, this is actually a valid protocol message - even if it's not used by the current state machine - so allow empty batches to be sent from clients.
Revamp client documentation so that each snippet is self-contained, and standardize it across all languages.
Give the DevHub a fresh coat of paint, and fix passing seeds being blue in dark mode.
#2408, #2400, #2391, #2399, #2402, #2385
Improve VOPR logging and fix a few failing seeds.
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.1
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.16.1
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.8docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.8-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.16.8go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.16.8com.tigerbeetle.tigerbeetle-java in pom.xml
to 0.16.8.npm install tigerbeetle-node@0.16.8Significantly reduced P100 latency by incrementally spreading the mutable table's sort during compaction. This leverages the optimization of sort algorithms for processing sequences of already sorted sub-arrays.
Improve the workload generator to support concurrent tests with different ledgers.
Fix VOPR seeds. For more awesome details about the backstory and solutions to these issues, please refer to the PR.
Update the REPL to support representing the maximum integer value as -0,
serving as the AMOUNT_MAX sentinel.
Additionally, other negative values such as -1 can be used to represent maxInt - 1.
Also, include support for hexadecimal numbers for more convenient inputting of GUID/UUID
literals (e.g. 0xa1a2a3a4_b1b2_c1c2_d1d2_e1e2e3e4e5e6).
Allow the timestamp field to be set, enabling the REPL to be used for imported events.
Use zig fetch as a replacement for downloading files, removing dependence on external tools.
Port of Rust's dbg! macro to Zig,
and the corresponding CI validation to prevent code using it from being merged into main! 😎
Verify the release versions included in the multiversion binary pack at build time (not only
during runtime) and improve the tigerbeetle version --verbose command's multiversion output.
Fix a multiversioning issue where the binary size exceeded the read buffer, failing to parse the executable header.
Consistently use transient_error instead of transient_failure and cleanup the StateMachine
code.
Add missing links to the operations query_accounts and query_transfers in the documentation
and include the declaration for QueryFilter and QueryFilterFlags in the tb_client.h header.
Clearer error message when the replica crashes due to a data file being too large, instructing the operator to increase the memory allocated for the manifest log.
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.15.6
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.15.6
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.4docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.4-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.16.4go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.16.4com.tigerbeetle.tigerbeetle-java in pom.xml
to 0.16.4.npm install tigerbeetle-node@0.16.4This release introduces "transient errors": error codes for create_transfers which depend on the
state of the database (e.g. exceeds_credits). Going forward, a transfer that fails with a
transient error will not succeed if retried.
See the API tracking issue and the documentation for more details.
Reduce chance of recovering_head status by recovering from torn writes in the WAL.
This improves the availability of the cluster, as recovering_head replicas cannot participate in
consensus until after they repair.
Ensure idempotence for create_transfers' "transient errors" with new result code
id_already_failed. In particular, this guards against surprising behavior when the client is
running in a stateless API service.
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.15.5
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.15.5
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.3docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.3-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.16.3go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.16.3com.tigerbeetle.tigerbeetle-java in pom.xml
to 0.16.3.npm install tigerbeetle-node@0.16.3Improve cluster availability by more aggressive recovery for crashes that happen while a replica is checkpointing.
Add a more efficient recipe for balance-conditional transfers. A balance-conditional transfer is a transfer that succeeds only if the source account has more than a threshold amount of funds in it.
Add a new recipe for enforcing debits_must_not_exceed_credits on some subset of transfers (this
is a special case of a balance-conditional transfer, with the threshold value being equal to
transferred amount).
Add triaged issue label to prevent newly opened issues from slipping through the cracks.
Add CI check for dead code.
Cleanup the source tree by removing top-level tools directory.
Make sure that process-spawning API used for build-time "scripting" consistently reports errors when the subprocess fails or hangs.
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.15.4
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.15.4
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.2docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.2-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.16.2go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.16.2com.tigerbeetle.tigerbeetle-java in pom.xml
to 0.16.2.npm install tigerbeetle-node@0.16.2Tighten up the VSR assertions so the transition to .recovering_head can only be called from the
.recovering status.
Make the primary abdicate if it is unable to process requests due to a broken clock.
Smoke integration test using the real multiversion binary.
Workload generator based on the Java client to be used in integration tests (i.e. Antithesis).
#2298, #2307, #2304, #2309, #2321
Remove Tracy integration and dependencies.
Add JSON traces for events with multiple running instances, such as IO, lookups, and scans.
Add the ability to filter by user_data_{128,64,32} and code in get_account_transfers
and get_account_balances.
Mute the log on stderr when building client libraries.
Reduce the log's severity of some entries logged as .err to .warn for less noise when
running with log_level = .err.
Document and explain how time works in TigerBeetle ⏱️.
Refactor Forest.compact and remove some dead code.
Rewrite commit_dispatch, a chain of asynchronous stages calling each other, as a state machine
implementation that resembles linear control flow that is much easier to read.
Fix the Node.js example that was using an incorrect enum flag. Thanks for the heads up @jorispz!
Update outdated scripts in HACKING.md.
Use git timestamps to build Docker images. This is a requirement for being deterministic in CI.
Devhub link to pending code reviews.
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.15.3
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.15.3
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.1docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.1-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.16.1go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.16.1com.tigerbeetle.tigerbeetle-java in pom.xml
to 0.16.1.npm install tigerbeetle-node@0.16.1Improve view change efficiency; new heuristic for lagging replicas to forfeit view change.
A lagging replicas first gives a more up-to-date replica a chance to become primary by forfeiting view change. If the more up-to-date replica cannot step up as primary, the lagging replica attempts to step up as primary.
Complete rollout of the new state sync protocol.
Remove in-code remnants of the old state sync protocol. Replicas now panic if they receive messages belonging to the old protocol.
Improve log warnings for client eviction due to its version being too low/high.
Fix VOPR false positive wherein checkpoint was being updated twice in the upgrade path.
Fix typos found using codespell.
Document example for debiting multiple accounts and crediting a single account wherein the total amount to transfer to the credit account is known, but the balances of the individual debit accounts are not known.
Document the behavior of user_data_128/user_data_64/user_data_32 in the presence of pending
transfers.
Inline Dockerfile in the release code, removing tools/docker/Dockerfile.
Add support for tracing IO & CPU events. This allows for coarse-grained performance analysis, for example collectively profiling IO and CPU performance (as opposed to IO or CPU in isolation).
Remove explicit header sector locks, using a common locking path for prepare and header sectors.
Change CliArgs -> CLIArgs in accordance with TigerStyle.
Vendor llvm-objcopy in the dependencies
repository in accordance with our "no dependencies" policy. This ensures users don't have to
manually install LLVM.
Assign correct date to the release binary date; it was earlier set to the epoch ("Jan 1 1970").
Introduce fatal errors for crashing the replica process in the face of uncorrectable errors (for example, insufficient memory/storage).
Add formatting check in the CI for the Go client.
Reduce dimensionality of configuration modes.
Removes the development configuration which was used to run the replica with asserts enabled, enabling asserts for the production configuration instead. Additionally, removes the -Dconfig CLI option, making production configuration the default.
…value in such cases. Note that this is a breaking change.
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.15.3
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.0docker pull ghcr.io/tigerbeetle/tigerbeetle:0.16.0-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.16.0go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.16.0com.tigerbeetle.tigerbeetle-java in pom.xml
to 0.16.0.npm install tigerbeetle-node@0.16.0This release is 0.16.0 as it includes a new breaking API change around zero amount transfers, as well as the behavior around posting a full pending transfer amount or balancing as much as possible. These are all gated by the client's release version.
If you're running a client older than 0.16.0, you'll see the old behavior where zero amount transfers are disallowed, but on newer clients these are supported and will create a transfer with an amount of 0.
Additionally, the sentinel value to representing posting the full amount of a pending transfer, or
doing a balancing transfer for as much as possible has changed. It's no longer 0, but instead
AMOUNT_MAX.
See the tracking issue for more details.
Change how replicas that haven't finished syncing send a prepare_ok message,
preventing them from falsely contributing to the durability of a checkpoint, which could
potentially cause liveness issues in the event of storage faults.
The new state sync protocol regressed the behavior where the replica would try to repair the WAL before switching to state sync, and this puts the old behavior back in.
WAL repair is used when the lagging replica's log still intersects with the cluster's current log, while state sync is used when when the logs no longer intersect.
Try to repair (but not commit) prepares, even if we don't have all the headers between checkpoint and head.
This makes things consistent between the normal and repair paths, and improves concurrency while repairing.
Reject prepares on the primary if its view isn't durable, much like solo clusters.
This solves a failing VOPR seed wherein a primary accepting prepares before making its log_view durable exposes a break in its hash chain.
A few sysctls and security frameworks (eg, seccomp) might block io_uring. Print out a more
helpful error message, rather than a generic "permission denied" or "system outdated".
Add the new imported flag to allow user-defined timestamps when creating
Accounts and Transfers from historical events.
Allow Transfers with amount=0 and change behavior for balancing and post-pending
transfers, introducing the constant AMOUNT_MAX to replace the use of the zero sentinel when
representing the maximum/original value in such cases. Note that this is a
breaking change.
Also, explicitly define optional indexes, which previously were determined simply by not indexing zeroed values.
Introduce a new flag, Account.flags.closed, which causes an account to reject any further
transfers, except for voiding two-phase transfers that are still pending.
The account flag can be set during creation or through a closing transfer. In the latter case, closed account can be re-opened by voiding or expiring the closing transfer.
Deprecates the old state sync protocol, no longer supporting both protocols simultaneously. As planned for this release, it only ignores old messages, allowing replicas to upgrade normally. In the next release, replicas would panic if they receive an old message.
Move multiversion build logic into build.zig from release.zig. This makes it much easier to
build multiversion binaries as part of a regular zig build, without having to invoke CI or
release process specific code that's normally part of release.zig.
It also makes it possible to build multiversion binaries on platforms that aren't x86_64 Linux.
Refactor the Multiversion API, bringing it in line with pre-existing code patterns.
Previously, TigerBeetle release numbers were based on a finicky conversion of GitHub's internal action run number to a version number.
This was error prone, and difficult to reason about before hand (what would the given version number for a release be?). Instead, make it so this very changelog is the source of truth for the version number which is explicitly set.
Change init function signatures to allow for in-place initialization. This addresses the silent
stack growth caused by intermediate copy/move allocations during the initialization of large
objects.
Specifically, the Forest struct can grow indefinitely depending on the number of
Grooves/IndexTrees needed to support the StateMachine's custom logic, causing TigerBeetle to
crash during startup due to stack-overflow.
Don't cancel in-progress GitHub actions on the main branch. In particular, this ensures that the devhub records the benchmark measurements for every merge to main, even if those merges occur in quick succession.
Make the experimental feature aof (append-only file) a runtime flag instead of a build-time
setting. This simplifies operations, allowing the use of the same standard release binary in
environments that require aof.
Renames the LSM constant lsm_batch_multiple to lsm_compaction_ops, providing clearer meaning
on how it relates to the pace at which LSM tree compaction is triggered.
Add support for indexing flags, namely the new imported flag.
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.15.3
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.15.3
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.15.6docker pull ghcr.io/tigerbeetle/tigerbeetle:0.15.6-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.15.6go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.15.6com.tigerbeetle.tigerbeetle-java in pom.xml
to 0.15.6.npm install tigerbeetle-node@0.15.6Add new state sync protocol, fixing a couple of liveness issues. State sync is now performed as part of the view change.
Major state sync performance improvements.
Ensure u128 (and related type) consistency across client implementations.
Fix multiversioning builds for aarch64 macOS.
Automatically include oldest supported releases in release notes.
Refactor build.zig to break up the biggest function in the codebase.
Minor improvements to zig install scripts.
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.15.3
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.15.3
When upgrading from 0.15.4, the binary will stop automatically by hitting an assert. You should restart it after that.
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.15.5docker pull ghcr.io/tigerbeetle/tigerbeetle:0.15.5-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.15.5go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.15.5com.tigerbeetle.tigerbeetle-java in pom.xml
to 0.15.5.npm install tigerbeetle-node@0.15.5Highlight of this release is fully rolled-out support for multiversion binaries. This means that,
from now on, the upgrade procedure is going to be as simple as dropping the new version of
tigerbeetle binary onto the servers. TigerBeetle will take care of restarting the cluster at the
new version when it is appropriate. See https://docs.tigerbeetle.com/operating/upgrading for
reference documentation.
Note that the upgrade procedure from 0.15.3 and 0.15.4 is a bit more involved.
0.15.3, you'll need to stop and restart tigerbeetle binary manually.0.15.4, the binary will stop automatically by hitting an assert. You
should restart it after that.Test client eviction in the VOPR.
Add integration tests for upgrades.
Add more hardening parameters to the suggested systemd unit definition.
Make the root directory smaller by getting rid of scripts and .gitattributes entries.
Root directory is the first thing you see when opening the repository, this space shouldn't be
wasted!
Complete the integration of multiversion binaries with the release infrastructure. From now on, the upgrade procedure is as simple as replacing the binary on disk with a new version. TigerBeetle will take care of safely and seamlessly restarting the cluster when appropriate itself.
Prepare to rollout the new state sync protocol. Stay tuned for the next release!
Simplify iteration over an LSM tree during scans.
Fix addresses logging in the client regressed by #2164.
Modernize scripts to generate client bindings to follow modern idioms for build.zig.
Fix typo in the currency exchange example.
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.15.3
Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.15.3
This is the first release of TigerBeetle which supports upgrading from a past version! The only special consideration is that if you're running a 0.15.3 cluster, you have to manually restart each replica after installing the new 0.15.4 binary.
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.15.4docker pull ghcr.io/tigerbeetle/tigerbeetle:0.15.4-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.15.4go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.15.4com.tigerbeetle.tigerbeetle-java in pom.xml
to 0.15.4.npm install tigerbeetle-node@0.15.4This release incorporates over 4 months of changes since the last published release, 0.15.3! You can see all the changes here starting from 2024-04-01 to 2024-07-29.
NOTE: You must run the same version of server and client. We do not yet follow semantic versioning where all patch releases are interchangeable.
0.15.3
NOTE: You must run the same version of server and client. We do not yet follow semantic versioning where all patch releases are interchangeable.
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.15.3docker pull ghcr.io/tigerbeetle/tigerbeetle:0.15.3-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.15.3go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.15.3com.tigerbeetle.tigerbeetle-java in pom.xml to 0.15.3.npm install tigerbeetle-node@0.15.3Set TigerBeetle's block size to 512KB.
Previously, we used to have a block size of 1MB to help with approximate pacing. Now that pacing can be tuned independently of block size, reduce this value (but not too much - make the roads wider than you think) to help with read amplification on queries.
Automated build. Do not use in production.
0.15.2
Automated build. Do not use in production.
NOTE: You must run the same version of server and client. We do not yet follow semantic versioning where all patch releases are interchangeable.
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.15.2docker pull ghcr.io/tigerbeetle/tigerbeetle:0.15.2-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.15.2go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.15.2com.tigerbeetle.tigerbeetle-java in pom.xml to 0.15.2.npm install tigerbeetle-node@0.15.2Implement compaction pacing: traditionally LSM databases run compaction on a background thread. In contrast compaction in tigerbeetle is deterministically interleaved with normal execution process, to get predictable latencies and to guarantee that ingress can never outrun compaction.
In this PR, this "deterministic scheduling" is greatly improved, slicing compaction work into smaller bites which are more evenly distributed across a bar of batched requests.
Include information about tigerbeetle version into the VSR protocol and the data file.
#1732, #1743, #1742, #1720, #1719, #1705, #1708, #1707, #1723, #1706, #1700, #1696, #1686.
Many availability issues found by the simulator fixed!
Fix a buffer leak when get_account_balances is called on an invalid account.
#1671, #1713, #1709, #1688, #1691, #1690.
Many improvements to the documentation!
Rename get_account_history to get_account_balances.
Automatically expire pending transfers.
Implement in-place upgrades, so that the version of tigerbeetle binary can be updated without recreating the data file from scratch.
Consistently use MiB rather than MB in the CLI interface.
Mark --standby and benchmark CLI arguments as experimental.
Unify PostedGroove and the index pending_status.
Include an entire header into checkpoint state to ease recovery after state sync.
Automated build. Do not use in production.
0.15.0
Automated build. Do not use in production.
NOTE: You must run the same version of server and client. We do not yet follow semantic versioning where all patch releases are interchangeable.
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.15.0docker pull ghcr.io/tigerbeetle/tigerbeetle:0.15.0-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.15.0go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.15.0com.tigerbeetle.tigerbeetle-java in pom.xml to 0.15.0.npm install tigerbeetle-node@0.15.0Implement compaction pacing: traditionally LSM databases run compaction on a background thread. In contrast compaction in tigerbeetle is deterministically interleaved with normal execution process, to get predictable latencies and to guarantee that ingress can never outrun compaction.
In this PR, this "deterministic scheduling" is greatly improved, slicing compaction work into smaller bites which are more evenly distributed across a bar of batched requests.
Include information about tigerbeetle version into the VSR protocol and the data file.
#1732, #1743, #1742, #1720, #1719, #1705, #1708, #1707, #1723, #1706, #1700, #1696, #1686.
Many availability issues found by the simulator fixed!
Fix a buffer leak when get_account_balances is called on an invalid account.
#1671, #1713, #1709, #1688, #1691, #1690.
Many improvements to the documentation!
Rename get_account_history to get_account_balances.
Automatically expire pending transfers.
Implement in-place upgrades, so that the version of tigerbeetle binary can be updated without recreating the data file from scratch.
Consistently use MiB rather than MB in the CLI interface.
Mark --standby and benchmark CLI arguments as experimental.
Unify PostedGroove and the index pending_status.
Include an entire header into checkpoint state to ease recovery after state sync.
Automated build. Do not use in production.
0.14.184
Automated build. Do not use in production.
NOTE: You must run the same version of server and client. We do not yet follow semantic versioning where all patch releases are interchangeable.
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.184docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.184-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.14.184go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.14.184com.tigerbeetle.tigerbeetle-java in pom.xml to 0.14.184.npm install tigerbeetle-node@0.14.184Fetching account history and transfers now has unit tests, helping detect and fix a reported bug with posting and voiding transfers.
#1656, #1659, #1666, #1667, #1667
Preparation for in-place upgrade support.
#1633, #1661, #1652, #1647, #1637, #1638, #1655
Documentation has received some very welcome organizational and clarity changes. Go check them out!
Automated build. Do not use in production.
0.14.183
Automated build. Do not use in production.
NOTE: You must run the same version of server and client. We do not yet follow semantic versioning where all patch releases are interchangeable.
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.183docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.183-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.14.183go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.14.183com.tigerbeetle.tigerbeetle-java in pom.xml to 0.14.183.npm install tigerbeetle-node@0.14.183#1584 Lower our memory usage by removing a redundant stash and not requiring a non-zero object cache size for Grooves.
The object cache is designed to help things like Account lookups, where the positive case can skip all the prefetch machinery, but it doesn't make as much sense for other Grooves.
Hook nyrkiö up to our CI! You can find our dashboard here in addition to our devhub.
#1635 #1634 #1623 #1619 #1609 #1608 #1595
Lots of small VSR changes, including a VOPR crash fix.
Fix a VOPR failure where state sync would cause a break in the hash chain.
Use Expand-Archive over unzip in PowerShell - thanks @felipevalerio for reporting!
Implement explicit coverage marks.
#1621 #1625 #1622 #1600 #1605 #1618 #1606
Minor doc fixups.
Default the VOPR to short log, and fix a false assertion in the liveness checker.
Fix a memory leak in our Java tests.
Automated build. Do not use in production.
0.14.181
Automated build. Do not use in production.
NOTE: You must run the same version of server and client. We do not yet follow semantic versioning where all patch releases are interchangeable.
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.181docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.181-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.14.181go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.14.181com.tigerbeetle.tigerbeetle-java in pom.xml to 0.14.181.npm install tigerbeetle-node@0.14.181Rework the log repair logic to never repair beyond a "confirmed" checkpoint, fixing a liveness issue where it was impossible for the primary to repair its entire log, even with a quorum of replicas at a recent checkpoint.
Some Java unit tests created native client instances without the proper deinitialization,
causing an OutOfMemoryError during CI.
Fix Vopr's false alarms.
Document how assertions should be used, especially those with complexity O(n) under
the constants.verify conditional.
Harmonize and automate the logging pattern by using the @src built-in to retrieve the
function name.
Include the benchmark smoke as part of the zig build test command rather than a special case
during CI.
Remove unused code coverage metrics from the CI.
Re-enable Windows CI 🎉.
Automated build. Do not use in production.
0.14.180
Automated build. Do not use in production.
NOTE: You must run the same version of server and client. We do not yet follow semantic versioning where all patch releases are interchangeable.
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.180docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.180-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.14.180go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.14.180com.tigerbeetle.tigerbeetle-java in pom.xml to 0.14.180.npm install tigerbeetle-node@0.14.180DVCs implicitly nack missing prepares from old log-views.
(This partially addresses a liveness issue in the view change.)
When a replica joins a view by receiving an SV message, some of the SV's headers may be too far ahead to insert into the journal. (That is, they are beyond the replica's checkpoint trigger.)
During a view change, those headers are now eligible to be DVC headers.
(This partially addresses a liveness issue in the view change.)
Fixes a bug in the C client that wasn't handling error.TooManyOutstanding correctly.
Bring back Windows tests for .Net client in CI.
Add script to scaffold changelog updates.
Improve CI/test error reporting.
Draw devhub graph as line graph.
Simplify command to run a single test.
Add client batching integration tests.
Format default values into the CLI help message.
Track commit timestamp to enable retrospective benchmarking in the devhub.
Improve CI/test performance.
Guarantee that the test runner correctly reports "zero tests run" when run with a filter that matches no tests.
(Hat tip to iofthetiger!)
Automated build. Do not use in production.
0.14.179
Automated build. Do not use in production.
NOTE: You must run the same version of server and client. We do not yet follow semantic versioning where all patch releases are interchangeable.
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.179docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.179-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.14.179go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.14.179com.tigerbeetle.tigerbeetle-java in pom.xml to 0.14.179.npm install tigerbeetle-node@0.14.179Reduce checkpoint latency by checkpointing the grid concurrently with other trailers.
Fix a logical race condition (which was caught by an assert) when reading and writing client replies concurrently.
Double check that both checksum and request number match between a request and the corresponding reply.
Optimize fields with zero value by not adding them to an index.
Introduce get_account_history operation for querying the historical balances of a given account.
Add helper function for generating approximately monotonic IDs to various language clients.
Automated build. Do not use in production.
0.14.178
Automated build. Do not use in production.
NOTE: You must run the same version of server and client. We do not yet follow semantic versioning where all patch releases are interchangeable.
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.178docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.178-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.14.178go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.14.178com.tigerbeetle.tigerbeetle-java in pom.xml to 0.14.178.npm install tigerbeetle-node@0.14.178Harden VSR against edge cases.
Allows VSR to perform checkpoint steps concurrently to reduce latency spikes.
Removed unused indexes on account balances for a nice bump in throughput and lower memory usage.
Only zero-out the parts necessary for correctness of fresh storage buffers. "Defense in Depth" without sacrificing performance!
TigerBeetle's dev workbench now also tracks memory usage (RSS), throughput, and latency benchmarks over time!
Simplify assertions and tests for VSR and Replica.
.NET CI fixups
Spring Cleaning
Deprecate support and testing for Node 16, which is EOL.
0.14.177
Automated build. Do not use in production.
NOTE: You must run the same version of server and client. We do not yet follow semantic versioning where all patch releases are interchangeable.
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.177docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.177-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.14.177go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.14.177com.tigerbeetle.tigerbeetle-java in pom.xml to 0.14.177.npm install tigerbeetle-node@0.14.177Panic on checkpoint divergence. Previously, if a replica's state on disk diverged, we'd use state sync to bring it in line. Now, we don't allow any storage engine nondeterminism (mixed version clusters are forbidden) and panic if we encounter any.
Fix a liveness issues when starting a view across checkpoints in an idle cluster.
Stop an isolated replica from locking a standby out of a cluster.
Change get_account_transfers to use timestamp_min and timestamp_max to allow filtering by
timestamp ranges.
Allow setting --addresses=0 when starting TigerBeetle to enable a mode helpful for integration
tests:
TigerBeetle now has a dev workbench! Currently we track our build times and executable size over time.
tigerbeetle client ... is now tigerbeetle repl ....
Deprecate support and testing for Node 16, which is EOL.
#1477, #1469, #1475, #1457, #1452.
Improve VOPR & VSR logging, docs, assertions and tests.
Improve integration tests around Node and pending_transfer_expired - thanks to our friends at
Rafiki for reporting!
Automated build. Do not use in production.
0.14.176
Automated build. Do not use in production.
NOTE: You must run the same version of server and client. We do not yet follow semantic versioning where all patch releases are interchangeable.
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.176docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.176-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.14.176go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.14.176com.tigerbeetle.tigerbeetle-java in pom.xml to 0.14.176.npm install tigerbeetle-node@0.14.176Welcome to 2024!
#1425, #1412, #1410, #1408, #1395.
Run more fuzzers directly in CI as a part of not rocket science package.
Formalize some ad-hoc testing practices as proper integration tests (that is, tests that interact
with a tigerbeetle binary through IPC).
Add a lint check for unused Zig files.
Improve cluster availability by including conservative information about the current view into ping-pong messages. In particular, prevent the cluster from getting stuck when all replicas become primaries for different views.
Test both the latest and the oldest supported Java version on CI.
Fix a data race on close in the Java client.
Make binaries on Linux about six times smaller (12MiB -> 2MiB). Turns tigerbeetle was
accidentally including 10 megabytes worth of debug info! Note that unfortunately stripping all
debug info also prevents getting a nice stack trace in case of a crash. We are working on finding
the minimum amount of debug information required to get just the stack traces.
Cleanup error handling API for Java client to never surface internal errors as checked exceptions.
Add example for setting up TigerBeetle as a systemd service.
Drop support for .Net Standard 2.1.
Don't exit repl on help command.
Overhaul documentation-testing infrastructure to reduce code duplication.
Don't test NodeJS client on platforms for which there are no simple upstream installation scripts.
Use histogram in the benchmark script to reduce memory usage.
Automated build. Do not use in production.
0.14.175
Automated build. Do not use in production.
NOTE: You must run the same version of server and client. We do not yet follow semantic versioning where all patch releases are interchangeable.
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.175docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.175-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.14.175go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.14.175com.tigerbeetle.tigerbeetle-java in pom.xml to 0.14.175.npm install tigerbeetle-node@0.14.175Welcome to 2024!
#1425, #1412, #1410, #1408, #1395.
Run more fuzzers directly in CI as a part of not rocket science package.
Formalize some ad-hoc testing practices as proper integration tests (that is, tests that interact
with a tigerbeetle binary through IPC).
Add a lint check for unused Zig files.
Improve cluster availability by including conservative information about the current view into ping-pong messages. In particular, prevent the cluster from getting stuck when all replicas become primaries for different views.
Test both the latest and the oldest supported Java version on CI.
Fix a data race on close in the Java client.
Make binaries on Linux about six times smaller (12MiB -> 2MiB). Turns tigerbeetle was
accidentally including 10 megabytes worth of debug info! Note that unfortunately stripping all
debug info also prevents getting a nice stack trace in case of a crash. We are working on finding
the minimum amount of debug information required to get just the stack traces.
Cleanup error handling API for Java client to never surface internal errors as checked exceptions.
Add example for setting up TigerBeetle as a systemd service.
Drop support for .Net Standard 2.1.
Don't exit repl on help command.
Overhaul documentation-testing infrastructure to reduce code duplication.
Don't test NodeJS client on platforms for which there are no simple upstream installation scripts.
Use histogram in the benchmark script to reduce memory usage.
Automated build. Do not use in production.
0.14.174
Automated build. Do not use in production.
NOTE: You must run the same version of server and client. We do not yet follow semantic versioning where all patch releases are interchangeable.
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.174docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.174-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.14.174go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.14.174com.tigerbeetle.tigerbeetle-java in pom.xml to 0.14.174.npm install tigerbeetle-node@0.14.174“The exception confirms the rule in cases not excepted." ― Cicero.
Due to significant commits we had this last week, we decided to make an exception in our release schedule and cut one more release in 2023!
Still, the TigerBeetle team wishes everyone happy holidays! 🎁
Some CI-related stuff plus the -Drelease flag, which will bring back the joy of
using the compiler from the command line 🤓.
Added value count to TableInfo, allowing future optimizations for paced compaction.
The simulator found a failure when the WAL gets corrupted near a checkpoint boundary, leading us to also consider scenarios where corrupted blocks in the grid end up "intersecting" with corruption in the WAL, making the state unrecoverable where it should be. We fixed it by extending the durability of "prepares", evicting them from the WAL only when there's a quorum of checkpoints covering this "prepare".
Fix a unit test that regressed after we changed an undesirable behavior that allowed prefetch
to invoke its callback synchronously.
Relaxed a simulator's verification, allowing replicas of the core cluster to be missing some prepares, as long as they are from a past checkpoint.
A highly anticipated feature lands on TigerBeetle: it's now possible to retrieve the transfers
involved with a given account by using the new operation get_account_transfers.
Note that this feature itself is an ad-hoc API intended to be replaced once we have a proper Querying API. The real improvement of this PR is the implementation of range queries, enabling us to land exciting new features on the next releases.
Bump the client's maximum limit and the default value of concurrency_max to fully take
advantage of the batching logic.
Automated build. Do not use in production.
0.14.171
Automated build. Do not use in production.
NOTE: You must run the same version of server and client. We do not yet follow semantic versioning where all patch releases are interchangeable.
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.171docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.171-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.14.171go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.14.171com.tigerbeetle.tigerbeetle-java in pom.xml to 0.14.171.npm install tigerbeetle-node@0.14.171As the last release of the year 2023, the TigerBeetle team wishes everyone happy holidays! 🎁
We've established a rotation between the team for handling releases. As the one writing these release notes, I am now quite aware.
Fix panic in JVM unit test on Java 21. We test JNI functions even if they're not used by the Java client and the semantics have changed a bit since Java 11.
Move client sessions from the Superblock (database metadata) into the Grid (general storage). This simplifies control flow for various sub-components like Superblock checkpointing and Replica state sync.
An optimization for removes on secondary indexes makes a return. Now tombstone values in the LSM can avoid being compacted all the way down to the lowest level if they can be cancelled out by inserts.
Clients automatically batch pending similar requests 🎉! If a tigerbeetle client submits a
request, and one with the same operation is currently in-flight, they will be grouped and
processed together where possible (currently, only for CreateAccount and CreateTransfers).
This should greatly improve the performance
of workloads which submit a single operation at a time.
Nothing published for this version
Automated build. Do not use in production.
0.14.169
Automated build. Do not use in production.
NOTE: You must run the same version of server and client. We do not yet follow semantic versioning where all patch releases are interchangeable.
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.169docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.169-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.14.169go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.14.169com.tigerbeetle.tigerbeetle-java in pom.xml to 0.14.169.npm install tigerbeetle-node@0.14.169Defense in depth: add checkpoint ID to prepare messages. Checkpoint ID is a hash that covers, via hash chaining, the entire state stored in the data file. Verifying that checkpoint IDs match provides a direct strong cryptographic guarantee that the state is the same across replicas, on top of existing guarantee that the sequence of events leading to the state is identical.
Gate the main branch on more checks: unit-tests for NodeJS and even more fuzzers.
Code cleanups after removal of storage size limit.
Automated build. Do not use in production.
0.14.168
Automated build. Do not use in production.
NOTE: You must run the same version of server and client. We do not yet follow semantic versioning where all patch releases are interchangeable.
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.168docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.168-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.14.168go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.14.168com.tigerbeetle.tigerbeetle-java in pom.xml to 0.14.168.npm install tigerbeetle-node@0.14.168Fix free set index. The free set is a bitset of free blocks in the grid. To speed up block allocation, the free set also maintains an index --- a coarser-grained bitset where a single bit corresponds to 1024 blocks. Maintaining consistency between a data structure and its index is hard, and thorough assertions are crucial. When moving free set to the grid, we discovered that, in fact, we don't have enough assertions in this area and, as a result, even have a bug! Assertions added, bug removed!
LSM tree fuzzer found a couple of bugs in its own code.
Remove format-time limit on the size of the data file. Before, the maximum size of the data file affected the layout of the superblock, and there wasn't any good way to increase this limit, short of recreating the cluster from scratch. Now, this limit only applies to the in-memory data structures: when a data files grows large, it is sufficient to just restart its replica with a larger amount of RAM.
We finally have the "installation" page in our docs!
Use Zig's new if (@inComptime()) builtin to compute checksum of an empty byte slice at compile
time.
Fix unit tests for the Go client and add them to not rocket science set of checks.
Automated build. Do not use in production.
0.14.167
Automated build. Do not use in production.
NOTE: You must run the same version of server and client. We do not yet follow semantic versioning where all patch releases are interchangeable.
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.167docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.167-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.14.167go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.14.167com.tigerbeetle.tigerbeetle-java in pom.xml to 0.14.167.npm install tigerbeetle-node@0.14.167When validating our releases, use the release branch instead of main to ensure everything is
in sync, and give the Java validation some retry logic to allow for delays in publishing to
Central.
Pad storage checksums from 128-bit to 256-bit. These are currently unused, but we're reserving the space for AEAD tags in future.
Remove a trailing comma in our Java client sample code.
Switch bootstrap.sh to use spaces only for indentation and ensure it's checked by our
shellcheck lint.
Update our DESIGN.md to better reflect storage fault probabilities and add in a reference.
Add CHANGELOG.md validation to our tidy lint script. We now check line length limits and
trailing whitespace.
In keeping with
TigerStyle,
rename reserved_nonce to nonce_reserved.
Note in TigerStyle that callbacks go last in the list of parameters.
Add an exception for line length limits if there's a link in said line.
Automated build. Do not use in production.
0.14.166
Automated build. Do not use in production.
NOTE: You must run the same version of server and client. We do not yet follow semantic versioning where all patch releases are interchangeable.
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.166docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.166-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.14.166go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.14.166com.tigerbeetle.tigerbeetle-java in pom.xml to 0.14.166.npm install tigerbeetle-node@0.14.166Recursively check for padding in structs used for data serialization, ensuring that no uninitialized bytes can be stored or transmitted over the network. Previously, we checked only if the struct had no padding, but not its fields.
Minor adjustments in the release process, making it easier to track updates in the documentation website when a new version is released, even if there are no changes in the documentation itself.
Fix outdated documentation regarding 128-bit balances.
Fix a bug discovered and reported
during the Hackathon 2023, where the Node.js
client's error messages were truncated due to an incorrect string concatenation adding a null
byte 0x00 in the middle of the string.
Update the Node.js samples instructions, guiding the user to install all dependencies before the sample project.
We've doubled the Headers size to 256 bytes, paving the way for future improvements that will
require extra space. Concurrently, this change also refactors a great deal of code.
Some of the Header's fields are shared by all messages, however, each Command also requires
specific pieces of information that are only used by its kind of message, and it was necessary to
repurpose and reinterpret fields so that the same header could hold different data depending on
the context. Now, commands have their own specialized data type containing the fields that are
only pertinent to the context, making the API much safer and intent-clear.
With larger headers (see #1295) we have enough room to make the cluster ID a 128-bit integer, allowing operators to generate random cluster IDs without the cost of having a centralized ID coordinator. Also updates the documentation and sample programs to reflect the new maximum batch size, which was reduced from 8191 to 8190 items after we doubled the header.
Automated build. Do not use in production.
0.14.165
Automated build. Do not use in production.
NOTE: You must run the same version of server and client. We do not yet follow semantic versioning where all patch releases are interchangeable.
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.165docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.165-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.14.165go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.14.165com.tigerbeetle.tigerbeetle-java in pom.xml to 0.14.165.npm install tigerbeetle-node@0.14.165Implement last-mile release artifact verification in CI.
Bump the simulator's safety phase max-ticks to avoid false positives from the liveness check.
Fix a crash caused by a race between a commit and a repair acquiring a client-reply Write.
Fix a crash caused by a race between state (table) sync and a move-table compaction.
Both bugs didn't stand a chance in the Line of Fire of our deterministic simulator!
Specify which CPU features are supported in builds.
Improve shell.zig's directory handling, to guard against mistakes with respect to the current
working directory.
Interpret a git hash as a VOPR seed, to enable reproducible simulator smoke tests in CI.
Explicitly target glibc 2.7 when building client libraries, to make sure TigerBeetle clients are compatible with older distributions.
Automated build. Do not use in production.
0.14.164
Automated build. Do not use in production.
NOTE: You must run the same version of server and client. We do not yet follow semantic versioning where all patch releases are interchangeable.
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.164docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.164-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.14.164go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.14.164com.tigerbeetle.tigerbeetle-java in pom.xml to 0.14.164.npm install tigerbeetle-node@0.14.164Implement last-mile release artifact verification in CI.
Bump the simulator's safety phase max-ticks to avoid false positives from the liveness check.
Fix a crash caused by a race between a commit and a repair acquiring a client-reply Write.
Fix a crash caused by a race between state (table) sync and a move-table compaction.
Both bugs didn't stand a chance in the Line of Fire of our deterministic simulator!
Specify which CPU features are supported in builds.
Improve shell.zig's directory handling, to guard against mistakes with respect to the current
working directory.
Interpret a git hash as a VOPR seed, to enable reproducible simulator smoke tests in CI.
Explicitly target glibc 2.7 when building client libraries, to make sure TigerBeetle clients are compatible with older distributions.
Nothing published for this version
Nothing published for this version
Automated build. Do not use in production.
0.14.160
Automated build. Do not use in production.
NOTE: You must run the same version of server and client. We do not yet follow semantic versioning where all patch releases are interchangeable.
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.160docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.160-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.14.160go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.14.160com.tigerbeetle.tigerbeetle-java in pom.xml to 0.14.160.npm install tigerbeetle-node@0.14.160Revive the TigerBeetle VOPRHub! Some previous changes left it on it's Last Stand, but the bot is back in business finding liveness bugs: #1266
Set the latest Docker image to track the latest release. Avoids language clients going out of sync with your default docker replica installations.
Nothing published for this version
Automated build. Do not use in production.
0.14.158
Automated build. Do not use in production.
NOTE: You must run the same version of server and client. We do not yet follow semantic versioning where all patch releases are interchangeable.
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.158docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.158-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.14.158go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.14.158com.tigerbeetle.tigerbeetle-java in pom.xml to 0.14.158.npm install tigerbeetle-node@0.14.158Prove a tighter upper bound for the size of manifest log. With this new bound, manifest log is guaranteed to fit in allocated memory and is smaller. Additionally, manifest log compaction is paced depending on the current length of the log, balancing throughput and time-to-recovery.
Recommend using ULID for event IDs. ULIDs are approximately sorted, which significantly improves common-case performance.
Rewrite Node.js client implementation to use the common C client underneath. While clients for other languages already use the underlying C library, the Node.js client duplicated some code for historical reasons, but now we can leave that duplication in the past. This Is A Photograph.
Automated build. Do not use in production.
0.14.157
Automated build. Do not use in production.
NOTE: You must run the same version of server and client. We do not yet follow semantic versioning where all patch releases are interchangeable.
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.157docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.157-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.14.157go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.14.157com.tigerbeetle.tigerbeetle-java in pom.xml to 0.14.157.npm install tigerbeetle-node@0.14.157Include Docker images in the release.
Increase block size to reduce latencies due to compaction work. Today, we use a simplistic schedule for compaction, which causes latency spikes at the end of the bar. While the future solution will implement a smarter compaction pacing to distribute the work more evenly, we can get a quick win by tweaking the block and the bar size, which naturally evens out latency spikes.
The new release process changed the names of the published artifacts (the version is no longer included in the name). This broke our quick start scripts, which we have fixed. Note that we are in the process of rolling out the new release process, so some unexpected breakage is expected.
Speed up secondary index maintenance by statically distinguishing between insertions and updates. Faster than the speed of night!
Simplify superblock layout by using a linked list of blocks for manifest log, so that the superblock needs to store only two block references.
P.S. Note the PR number!
Nothing published for this version
Automated build. Do not use in production.
0.14.152
Automated build. Do not use in production.
NOTE: You must run the same version of server and client. We do not yet follow semantic versioning where all patch releases are interchangeable.
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.14.152NOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.14.152go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.14.152com.tigerbeetle.tigerbeetle-java in pom.xml to 0.14.152.npm install tigerbeetle-node@0.14.152Automated build. Do not use in production.
Automated build. Do not use in production.
NOTE: You must run the same version of server and client. We do not yet follow semantic versioning where all patch releases are interchangeable.
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.13.138docker pull ghcr.io/tigerbeetle/tigerbeetle:0.13.138-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.13.138go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.13.138com.tigerbeetle.tigerbeetle-java in pom.xml to 0.13.138.npm install tigerbeetle-node@0.13.138Automated build. Do not use in production.
Automated build. Do not use in production.
NOTE: You must run the same version of server and client. We do not yet follow semantic versioning where all patch releases are interchangeable.
docker pull ghcr.io/tigerbeetle/tigerbeetle:0.13.137docker pull ghcr.io/tigerbeetle/tigerbeetle:0.13.137-debugNOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.
dotnet add package tigerbeetle --version 0.13.137go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.13.137com.tigerbeetle.tigerbeetle-java in pom.xml to 0.13.137.npm install tigerbeetle-node@0.13.137One column per quarter.