Hold Off on Litestream 0.5.0

https://mtlynch.io/notes/hold-off-on-litestream-0.5.0/

70•mtlynch•4h ago

Comments

emschwartz•3h ago

Extremely helpful. I've been eagerly awaiting v0.5 but have been holding off on deploying it until I had more confidence that it would work and be stable. Reading this, I'm definitely glad that I waited.

ComputerGuru•3h ago

No need for all the “I love Litestream” disclaimers, these are serious issues that speak for themselves.

jasonthorsness•3h ago

The change log is massive, so this is not unexpected to have a few issues. Maybe the two-year backlog of features and updates should have been batched into a few releases instead of this one big one? But there was a beta, and this is ripping the bandaid.

https://github.com/benbjohnson/litestream/releases/tag/v0.5....

mtlynch•2h ago

I think the most disruptive part is the migration to the new LTX format,[0] which I'd imagine is hard to do incrementally.

[0] https://fly.io/blog/litestream-v050-is-here/#the-ltx-file-fo...

benbjohnson•2h ago

Litestream author here. Yes, that's correct. LTX was the biggest hurdle to get over and was impossible to switch over incrementally. The storage layer change brings a lot of benefits and enables a lot of future work that we're really excited about.

Thanks to mtlynch and everyone else who has submitted bug reports. We're squashing issues and working to get everything stable as quickly as possible.

liuliu•2h ago

Feels like a side-effect of forever 0.x version symptom (I am guilty of as well). Even though semi-ver says 0.x can do whatever, people don't associate enough disruptive changes to it, whereas 0.4.x if it is 1.x, then it is much clearer this is a 2.x release.

All things considered, this is probably just a tiny footnote in this software's life.

ncruces•2h ago

I've been trying to get a headstart on the lightweight read replicas for my Go SQLite driver and, yes, there are issues.

https://fly.io/blog/litestream-revamped/#lightweight-read-re...

But the concept is really cool, and it's workable. I already have a version that mostly works.

https://github.com/ncruces/go-sqlite3/tree/litestream/litest...

With Litestream v0.5.0 doing the replication, you'll get some transient read failures that really shouldn't happen.

If you build Litestream from head (or wait for v0.5.1), that'll be fixed. You'll still have similar issues around the time of a snapshot, if you keep only one snapshot.

Other than that, I'm pretty confident it just works. But the performance probably sucks. I need to add a layer of caching. But that's it.

andersmurphy•2h ago

Thanks for the heads up. I encountered similar issues so staying on 0.3.13 for now. But excited to give 0.5.x a go once the dust settles.

Livestream, sqlite and caddy are incredibly at making single box/vps ops a breeze.

placardloop•1h ago

> One of the benefits of Litestream 0.5.0 is that there’s now an official litestream Docker image. All of my previous Docker containers required a lot of boilerplate to download the correct version of Litestream and make it available in my container, but now it reduces to a single Dockerfile line

There’s been an official Litestream container image for over 3 years at this point (since version 0.3.4, it’s at the same Docker Hub as 0.5.0).

mtlynch•1h ago

Oh, thanks for the correction! I can't believe I never noticed that. I've updated the post.

After your comment, I thought, "Oh, I should contribute a PR to the repo to add the Docker badge so the Docker image is obvious to everyone," but it turns out the badge has been right there for four years.[0]

What I suspect happened is that I tried to use the Litestream Docker image once, discovered that image was amd64-only (until 0.3.9), so I didn't use it because I needed ARM, and then I just kept copy/pasting my workaround from project to project.

[0] https://github.com/benbjohnson/litestream/commit/6acfbcbc64d...

How everyday tech is training us to accept constant surveillance Seattle

'I love Hitler': Leaked messages expose Young Republicans' racist chat

What Declining Cardboard Box Sales Tell Us About the US Economy

JerryRigEverything: My Pixel 10 Pro Fold Exploded – Caught Live on Camera[video]

Signed Backdoor Hiding in Plain Sight on Framework Devices

Ask HN: How old is your data centre?

A Plan to Rebuild Gaza Lists Nearly 30 Companies. Many Say They're Not Involved

Half of America's Voting Machines Are Now Owned by a MAGA Oligarch

USA causes of death by age and gender

Virtual education company was a lifeline to a rural district. Now they're at war

Unpacking Cloudflare Workers CPU Performance Benchmarks

Reducing Pipeline Bubbles with Adaptive Parallelism on Heterogeneous Models

Crypto Became a Trump Trade – Paul Krugman

The quality of AI code is low and the AIs themselves don't understand it

AppLovin Nonconsensual Installs

Going Broke Slowly: The Investment Implications of Still-Rising Federal Debt

The DHH Problem

My New Project:)

Salesforce Says AI Customer Service Saves $100M Annually

Rest in Peace Mark Forster

Nook Browser – Browse. It's Yours. Open-Source, Private, Forever.

Say the Quiet Part Out Loud

How Can You Plan a Decade in Advance?

Reducto Raises $108M to Shape the Future of AI Document Intelligence

Surveillance Empire That Tracked World Leaders, a Vatican Enemy, and Maybe You

AI and Labor Markets: What We Know and Don't Know

The New World: Joshua Kushner, Thrive Capital, and the American Dream

Show HN: Wispbit – Keep codebase standards alive

AI bots wrote and reviewed all papers at this conference

Why the open social web matters now