Anyone using #litestream for an #sqlite DB
-
Anyone using #litestream for an #sqlite DB
I have a 3GB database, and Litestream is replicating it to another server. However, it seems to be running out of control with disk space. On the original server (where the live DB is) is agenerationsfolder under the hidden litestream folder. It is full of WAL files. Currently over 37,000 files consuming 118GB of disk space.
My config includesretention: 24handretention-check-interval: 1hwith asnapshot-interval: 4h. I understood it would delete anything older than 24 hours. Am I doing something wrong? These wal files go back to the day I started using litestream
#GoToSocial #gts @gotosocial@thefedi.forum -
replied to Bumble last edited by
@bumble @gotosocial hmm. AFAIK, there should’t be any extra files at the live db, since litestream stores its metadata in tables in the db itself. I can’t check right now, so could be wrong, but sounds like a configuration issue.
-
replied to Markus 🤓✨ last edited by
@bumble @gotosocial I was wrong! I have the dir too, but it doesn’t take up a lot of space.
-
replied to Markus 🤓✨ last edited by
@markus@hachyderm.io @gotosocial@thefedi.forum I've had to turn it off for now. It's continuing to eat disk space. I didn't know if I could just delete all those files or it would comprise the integrity of the mirror process. Very odd.
I did try their support channel but no response in a week. I'm at a loss. Need to try and find a new solution.
#litestream -
replied to Bumble last edited by
@bumble @gotosocial hmm. Odd. I've had this configuration for a year or so, it’s working quite well: https://gist.github.com/markuswustenberg/3914cd2fea9aa9e3313863de501b67a5 . Maybe you can stop litestream, delete the metadata files and tables ("_litestream_lock" and “_litestream_seq”), change to this config, and try again?
