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
Looking at the database process list, a parallel DELETE statement is executed for this table, looking like one generated by Icinga DB's retention part.
MariaDB [icingadb]> show processlist;
+-----+----------+-----------------+----------+---------+------+----------+---------------------------------------------------------------------------------------
---------------+----------+
| Id | User | Host | db | Command | Time | State | Info
| Progress |
+-----+----------+-----------------+----------+---------+------+----------+---------------------------------------------------------------------------------------
---------------+----------+
| 55 | icingadb | localhost:54518 | icingadb | Execute | 3341 | Updating | DELETE FROM state_history WHERE environment_id = ? AND event_time < ?
ORDER BY event_time LIMIT 5000 | 0.000 |
| 144 | icingadb | localhost | icingadb | Query | 0 | starting | show processlist
| 0.000 |
+-----+----------+-----------------+----------+---------+------+----------+---------------------------------------------------------------------------------------
---------------+----------+
2 rows in set (0.000 sec)
Such a crash happened reproducibly; sometimes after five minutes, sometimes after an hour, but eventually it crashed. After disabling the retention part, it worked again.
The text was updated successfully, but these errors were encountered:
While working on another issue with a larger test instance, I ran into a database locking issue after enabling the Icinga DB retention.
After adding the following
retention
block to my config, the problems started.Shortly after restarting Icinga DB, the following error appeared, always for the
state_history
table.Looking at the database process list, a parallel
DELETE
statement is executed for this table, looking like one generated by Icinga DB's retention part.Such a crash happened reproducibly; sometimes after five minutes, sometimes after an hour, but eventually it crashed. After disabling the retention part, it worked again.
The text was updated successfully, but these errors were encountered: