0.15.5

Supported upgrade versions

Oldest supported client version: 0.15.3 Oldest upgradable replica version: 0.15.3

Upgrading from 0.15.4

When upgrading from 0.15.4, the binary will stop automatically by hitting an assert. You should restart it after that.

Server

• Binary: Download the zip for your OS and architecture from this page and unzip.
• Docker: docker pull ghcr.io/tigerbeetle/tigerbeetle:0.15.5
• Docker (debug image): docker pull ghcr.io/tigerbeetle/tigerbeetle:0.15.5-debug

Clients

NOTE: Because of package manager caching, it may take a few minutes after the release for this version to appear in the package manager.

• .NET: dotnet add package tigerbeetle --version 0.15.5
• Go: go mod edit -require github.com/tigerbeetle/tigerbeetle-go@v0.15.5
• Java: Update the version of com.tigerbeetle.tigerbeetle-java in pom.xml to 0.15.5.
• Node.js: npm install tigerbeetle-node@0.15.5

Changelog

Highlight 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.

• When upgrading from 0.15.3, you'll need to stop and restart tigerbeetle binary manually.
• When upgrading from 0.15.4, the binary will stop automatically by hitting an assert. You should restart it after that.

Safety And Performance

• #2174 #2190,

  Test client eviction in the VOPR.

• #2187

  Add integration tests for upgrades.

• #2188

  Add more hardening parameters to the suggested systemd unit definition.

Features

• #2180, #2185, #2189, #2196

  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!

• #2199, #2165, #2198, #2184.

  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.

• #2181

  Prepare to rollout the new state sync protocol. Stay tuned for the next release!

Internals

• #2179, #2200

  Simplify iteration over an LSM tree during scans.

• #2182

  Fix addresses logging in the client regressed by #2164.

• #2193

  Modernize scripts to generate client bindings to follow modern idioms for build.zig.

• #2195

  Fix typo in the currency exchange example.

TigerTracks 🎧

• High Hopes