Releases: PowerDNS/lightningstream
Release list
v1.0.0
The highlight of this release is the Azure Blob support that was added to Simpleblob by @ptasker . In addition to that, we've decided it's time to give Lightning Stream its version 1 tag!
What's Changed
- add a check for update-docs.sh by @Luit in #126
- Documentation improvements regarding pdns auth integration by @hlindqvist in #124
- Pre 1.0 upgrades by @Luit in #127
- receive mode: do not force snapshots by @wojas in #94
- build(deps): bump the all-actions group across 1 directory with 6 updates by @dependabot[bot] in #128
- Add Azure Blob Storage backend by @ptasker in #121
New Contributors
- @hlindqvist made their first contribution in #124
- @ptasker made their first contribution in #121
Full Changelog: v0.6.0...v1.0.0
v0.6.0
v0.5.3
v0.5.2
v0.5.1
What's Changed
- name info: fix empty base name by @wojas in #93
- Upgrade module dependencies and move to standard slices package by @neilcook in #97
- GitHub Actions workflow for building and pushing documentation to docs.powerdns.com by @neilcook in #105
- Change documentation theme and logos to PowerDNS branding by @neilcook in #107
New Contributors
Full Changelog: v0.5.0...v0.5.1
v0.5.0
New feature: tombsweeper
The main new feature in the release is the 'tombsweeper'. When a record is deleted in a Lightning Stream installation, we do not actually remove the record, but instead write a deletion marker. Up until now these deletion markers were never deleted, leading to unbounded database growth in installations that see delete-heavy workloads. The new tombsweeper can clean these deletion markers after a configured interval.
WARNING: This is DISABLED by default, because enabling this functionality requires careful consideration. When enabled, you MUST make sure that no instance that has been offline for longer than the sweeper retention_days will ever reconnect. If this does happen, old entries that have been deleted may be resurrected causing anything from undesired results to database state corruption. Be especially careful about development or testing systems that only come online occasionally.
For small personal installations with infrequent changes, it is probably better NOT to enable this functionality, and accept that deleted entries accumulate over time. Only consider this you have frequent updates and deletion markers would actually become a problem over time. And in that case, be very conservative with the retention_days setting, the longer the better.
What's Changed
- Tombsweeper: clean stale delete markers by @wojas in #89
- Rename module to github.com/PowerDNS/lightningstream/lmdbenv by @wojas in #76
- GitHub Actions workflow for building and pushing multi-platform Docker images to Docker Hub by @joel-ling in #78
- Upgrade to Go 1.24 & CI fixes by @wojas in #87
- Add hooks by @wojas in #88
- Module upgrades, including lmdb-go to 1.9.3 by @wojas in #91
- Add Minio to github actions to use in test suite by @verscheures in #77
New Contributors
- @joel-ling made their first contribution in #78
- @verscheures made their first contribution in #77
Full Changelog: v0.4.3...v0.5.0
v0.4.4
v0.4.3
What's Changed
- Downloader: call
Closeon updates that are overwritten in(*Downlader).LoadOnceby @ahouene in #70 - S3 snapshot metrics by @nvaatstra in #74
New Contributors
- @nvaatstra made their first contribution in #74
Full Changelog: v0.4.2...v0.4.3
v0.4.2
v0.4.1
This fixes a resource leak that can cause growing memory and CPU usage over time (#57) for all S3 backend users.
It also fixes the update marker not working when a global S3 prefix is used, which causes the backend to use more expensive LIST API calls, leading to increased S3 usage costs. (#55)
This only affects you if you are using the opt-in upgrade marker.
What's Changed
- Upgrade Simpleblob to v0.2.4 by @franklouwers in #58
New Contributors
- @franklouwers made their first contribution in #58, thank you!
Full Changelog: v0.4.0...v0.4.1