RollupDB 0.5 Counts Retried Batches Once and Takes Prometheus Remote Write

Mon, 02 Nov 2026 00:00:00 +0000

RollupDB 0.5.0 is out, and most of it is about one awkward moment. A batch goes in, the connection drops, and you don’t know if it committed. Until now the docs said: don’t retry blindly, you might count everything twice. That’s honest, but it isn’t much help at three in the morning.

So a batch can now carry an ID. RollupDB stores the ID, a hash of the readings and the result in the same transaction as the data. Send the same batch again and you get the first answer back, marked "replayed": true, and nothing changes. Send different readings under the same ID and it’s refused with batch_conflict, which is what you want if two jobs ever end up sharing a name.

Prometheus on RollupDB.com

RollupDB 0.5 Counts Retried Batches Once and Takes Prometheus Remote Write