Updates.db Steadily Growing about mercure HOT 8 CLOSED

Currently this file is never dropped/cleaned up (it stores the list of updates to allow retrieving old ones).
But indeed we could provide an expiration mechanism for stored events to prevent this file to grow.

from mercure.

Hey @dunglas, is this expiration mechanism implemented in some way now? We are facing the same issue, when the file is constantly growing and have to manually empty it.

from mercure.

100 events.

from mercure.

I have some problem now - Mercure runs on small droplet - 25Gb and for a week it eat all disk space and broke.
How I can trunk DB? Or (best solution) clear old messages, for example - clear all, witch older 3 days?

from mercure.

@balabis I found solution - https://mercure.rocks/docs/hub/config - Bolt Adapter section

from mercure.

Sorry the documentation of Mercure is once again not clear enough. What is the unit of size? bolt:///var/run/mercure.db?size=100

Eg. What does 100 means? 100 bytes? 100 kB? 100MB? 100GB? Looking at Go code in the repo, the size might be a size of database records? Not sure.

from mercure.

100 events.

Thanks! Maybe document this :)

from mercure.

Ps. so now the mercure.db I got has a size of 3.8GB. So let's say I set a limit of a thousand (1000) events in my case, what size would this result into? Like 10MB? or .. It's a bit of a gut feeling you know what I mean, what I do know is that server owners don't want 5, 10, or 15GB mercure database files :).

from mercure.