ohhh… the same here, but every few hours, my system became crazy… (im spanish and i dont speak really good english) Sorry about it.
I tried stop the recorder system, but is not sttoped, continue with the same… every few hours, everything at home is not working…
Any solution? For me, my smart home is very important, and im soooo tired about the situation, the CPU is working a lot, the RAM memory is using a lot, the BD file is growing up a lot in a few minutes…
if you see, in a few minutes the file is growing up a lot. Making all the system dont repond to anything, no light going on, or off… is so depresing situation
is not possible block the recorder???
I dont think is seriously… whole the home block for this recorder??? Come on… my house is not a game, i have so many “systems” blocked by the recorder… we need a solution please!
hi
I have the same problem recently and i have to reboot everyday. Is there a actual solution tion for this? Thanks
I had the same problem recently. Eventually traced my issue to a problem with the Synology NAS that is remotely hosting the MariaDB for my recorder. I had a RAID disk failure and when I replaced it the RAID rebuild/verification process took a few days (apparently not uncommon). During this rebuild time my recorder would stop working after a few hours with the limit reached message.
After completing the rebuild/verification the recorder problem stopped.
Not sure if this helps anyone else.
This has just started becoming an issue for me also 
This issue has been more than 9 month already. Can’t believe there is still no fix to it. Hopefully it can be fixed soon.
same here…
https://www.reddit.com/r/homeassistant/comments/pg2ies/how_do_i_reset_the_recorder_queue
You can check your db and determine which causes excessive logs:
hi all,
I was able to overcome this issue by replacing the external server with PostgreSQL. I did a fresh install for the base OS then installed PostgreSQL12. It seems to be ok now after a week. I tried to drop the database in the old MariaDB server but it did not solve the issue. Hope this will help.
I was receiving following log every day
2022-08-08 03:52:46.878 ERROR (MainThread) [homeassistant.components.recorder.core] The recorder backlog queue reached the maximum size of 40000 events; usually, the system is CPU bound, I/O bound, or the database is corrupt due to a disk problem; The recorder will stop recording events to avoid running out of memory
In my case it was due to conflict (partial overlap) of automated backup and database purge - backup was not completely finished when database purge started. Since I shifted backup’s start it seems to be sorted out 
I am also having this error, and there seems to be no actual fix in sight.
I keep rebooting everyday.
I upgraded my storage, but to still happens.
This error just occurred for me after a scheduled backup.
How big is your DB and scheduled backup?
Mine grew to 25gb and the backup was about 6gb
I’m sorry for the late response! My DB is around 15 GB and the backup file is 3 GB.
I’m having this same issue with a database of 6GB and 20 million rows…
Same here! And I don’t know how to solve it… 
Here is a follow-up from another thread regarding the backup.
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
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.
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