High cpu/disk usage after upgrading MariaDB to plugin version 2.5.2

[Jelmerl101]

Describe the issue you are experiencing

HomeAssistant used to idle with 1-2% cpu usage and after upgrading the MariaDB plugin from 2.5.0 to 2.5.2 this has increased to almost 50% (full load on one core). I used glances to trace it to MariaDB, this has been going on for ~18 hours now.

Monitoring the processes on the database doesn't reveal anyhing out of the ordinary, just generic updates on states/events.

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Which add-on are you reporting an issue with?

Almond

What is the version of the add-on?

2.5.2

Steps to reproduce the issue

1. Updating to MariaDB 2.5.2 is the only step that started causing this.

System Health information

System Information

version	core-2023.4.5
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.10.10
os_name	Linux
os_version	6.1.24
arch	x86_64
timezone	Europe/Amsterdam
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
GitHub API Calls Remaining	4905
Installed Version	1.32.1
Stage	running
Available Repositories	1267
Downloaded Repositories	14

Home Assistant Cloud

logged_in	true
subscription_expiration	December 21, 2023 at 1:00 AM
relayer_connected	true
relayer_region	eu-central-1
remote_enabled	true
remote_connected	true
alexa_enabled	false
google_enabled	true
remote_server	eu-central-1-0.ui.nabu.casa
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 10.0
update_channel	stable
supervisor_version	supervisor-2023.04.0
agent_version	1.5.1
docker_version	23.0.3
disk_total	196.2 GB
disk_used	103.3 GB
healthy	true
supported	true
board	ova
supervisor_api	ok
version_api	ok
installed_addons	Home Assistant Google Drive Backup (0.110.3), File editor (5.5.0), Samba share (10.0.0), Home Panel (2.6.0), Duck DNS (1.15.0), FTP (4.6.3), SSH & Web Terminal (13.1.0), Grafana (8.2.2), phpMyAdmin (0.8.5), Mosquitto broker (6.2.0), TileBoard (1.3.7), MariaDB (2.5.2), Zigbee2MQTT (1.30.3-1), Glances (0.18.1)

Dashboards

dashboards	1
resources	5
views	8
mode	storage

Recorder

oldest_recorder_run	August 6, 2021 at 10:59 AM
current_recorder_run	April 21, 2023 at 9:06 AM
estimated_db_size	71924.52 MiB
database_engine	mysql
database_version	10.6.10

Anything in the Supervisor logs that might be useful for us?

No response

Anything in the add-on logs that might be useful for us?

Nothing out of the ordinary.

Additional information

No response

[Jelmerl101]

The CPU/Disk usage goes to normal if I restart MariaDB manually in the Add-on. However after restarting Home Assistant it returns and I will have to restart it trough the Add-on again to stop it.

Disabling Add-ons and integrations did not change this behavior.

Updated to HomeAssitant core 2023.4.6 today.

I have tried logging al queries being executed on the database but this revealed nothing out of the ordinary.

This is what I used for logging queries:

SET global general_log = 1;
SET global log_output = 'table'
select * from mysql.general_log

I will update if I find anything else. For now I will have to restart MariaDB after every HA restart to resolve this.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[dhzl84]

@Jelmerl101 DId you find a solution? I'm facing a similar issue right now. High CPU load spikes combines with huge disk reads. Restarting the MAriaDB Add-on does not fx it for me.

[Jelmerl101]

@dhzl84 No I didn't but it resolved itself after a few updates and never returned. I'm not sure exactly which version fixed it.