Recorder queue reached the maximum size of

[el97 (Erik)]

This error just occurred for me after a scheduled backup.

[cybernard (Jonathan)]

How big is your DB and scheduled backup?
Mine grew to 25gb and the backup was about 6gb

[el97 (Erik)]

I’m sorry for the late response! My DB is around 15 GB and the backup file is 3 GB.

[TommySharpNZ (Tommy)]

I’m having this same issue with a database of 6GB and 20 million rows…

[catalinbordan]

Same here! And I don’t know how to solve it…

[el97 (Erik)]

Here is a follow-up from another thread regarding the backup.

Error: The recorder queue reached the maximum size of 30000; Events are no longer being recorded

I’m not sure if it’s related but this happens every time I do a scheduled backup. I looked at the logs for MariaDB and saw that the table locks, unlocks then locks again. This happens in the same moment when the backup triggers. Another strange thing is that the time is un-syncronized in the first unlock. Yet again this might be unrelated but I want to point it out I did a scheduled backup with this add-on hassio-addons/samba-backup at master · thomasmauerer/hassio-addons · GitHub [15:00:15] …

I also posted some information on a open issue for the add-on I’m using to preform scheduled backups. Feel free to comment if anyone experiencing the same issues with this. Corrupt Archive / Backup stopping logger · Issue #122 · thomasmauerer/hassio-addons · GitHub

[rico365 (rico)]

@el97

ree to co

ugh, I moved to Maria after my SQLlite DB was corrupt and lost around 12 months of energy data… not i’m hitting this also using this tool for backups and noticed it failed after the backup last night.

[cybernard (Jonathan)]

I moved my maria DB to another PI and set the following to 2gb each

innodb_buffer_pool_size
innodb_log_file_size

Performance is good now