First release of 2019

This is a bugfix release

Better support for Rook

This version adds first-class support for Rook. You can now uncomment just two lines in the site config to get Rook to work with BTrDB.

Fixes to historic queries

We introduced a regression in caching logic a few versions back that affects queries done at old versions (like done by DISTIL). This fixes it and improves the admin API a bit

Journal pool

This release moves the BTrDB journal to its own pool (rather than a namespace in the hot pool). This improves startup performance for clusters where the hot pool is several tens of terabytes big. To upgrade, simply scale down the BTrDB statefulset, apply the new manifest file and scale back up. You need to manually create the new journal pool.

Add API keys

This release now supports using API keys for authentication via the API frontend. Both the go bindings and python bindings support this as well.

Tweaks

Incorporates a bugfix for mr-plotter's tree and a fix for the maximum size of the etcd database. Also adds a new query for building CSV files.

TLS rework

Fix the Lets Encrypt mechanisms for mrplotter and add TLS to the API frontend. The API is now available on port 4411 (secure GRPC) and 9001 (HTTPS) in addition to the legacy 4410 and 9000.

Persistent etcd

This release features a new mechanism for etcd in BTrDB. In prior releases we used etcd-operator but they don't really handle persistence well (servers restarting) and no longer offer a good backup solution. This release runs etcd as daemonsets on nodes that are configured in the siteconfig.yaml. This will make the cluster tolerant to restarts and power cycling.

If upgrading from a previous version of BTrDB, you will need to backup your etcd data and restore it. Please take a look at the backuptool for a guide on how this is done.

The PQM lands!

This is the first release candidate to bring the persistent queryable mux, which drastically improves the performance of BTrDB for non-high-density or non-batched insertion workloads.

Note this is still an odd-numbered release (4.9.x) so is not quite ready for production, but ready for testing!

So bleeding edge you'll wish you never tried it

This is not fit for public consumption. This release contains the new performance enhancements, persistent queryable mux and more. But only half the features work as advertised.