You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to some issues with processing jinja templates in a custom card I observed this chain reaction:
huge CPU load -> rapidly increasing DB
The DB size jumped from ~1GB to ~8GB within a few hours.
Why these templates & card caused this huge CPU load - is another issue.
Why this huge CPU load caused a rapid constant flooding the DB - is also another issue (have no idea, may be some integration, stock or custom, reacted this abnormal way).
After HA reboot I called a "purge + repack" service:
and after some time it gave me ~7GB file:
w/o any errors & messages in a Log (default logger settings).
I expected the DB file to be fixed and reduced in a size.
WTH this has not happened?
What version of Home Assistant Core has the issue?
2024.2.1
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
ildar170975
changed the title
Recoreder: after "purge+repack" the DB is still abnormally huge
Recorder: after "purge+repack" the DB is still abnormally huge
Feb 13, 2024
Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (recorder) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of recorder can trigger bot actions by commenting:
@home-assistant close Closes the issue.
@home-assistant rename Awesome new title Renames the issue.
@home-assistant reopen Reopen the issue.
@home-assistant unassign recorder Removes the current integration label and assignees on the issue, add the integration domain after the command.
@home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
@home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
The problem
Due to some issues with processing jinja templates in a custom card I observed this chain reaction:
huge CPU load -> rapidly increasing DB
The DB size jumped from ~1GB to ~8GB within a few hours.
Why these templates & card caused this huge CPU load - is another issue.
Why this huge CPU load caused a rapid constant flooding the DB - is also another issue (have no idea, may be some integration, stock or custom, reacted this abnormal way).
After HA reboot I called a "purge + repack" service:
and after some time it gave me ~7GB file:
w/o any errors & messages in a Log (default logger settings).
I expected the DB file to be fixed and reduced in a size.
WTH this has not happened?
What version of Home Assistant Core has the issue?
2024.2.1
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: