ironic/releasenotes/notes/not-heartbeat-the-conductor-with-sqlite-7cfc71e717d69bc5.yaml
Julia Kreger 0099d1812d Don't actually heartbeat with sqlite
Disables internal heartbeat mechanism when ironic has been
configured to utilize a SQLite database backend.

This is done to lessen the possibility of a
"database is locked" error, which can occur when two
distinct threads attempt to write to the database
at the same time with open writers.

The process keepalive heartbeat process was identified as
a major source of these write operations as it was writing
every ten seconds by default, which would also collide with
periodic tasks.

Change-Id: I7b6d7a78ba2910f22673ad8e72e255f321d3fdff
2023-07-14 09:22:01 -07:00

14 lines
590 B
YAML

---
deprecations:
- |
The use of a SQLite database with mutli-process (i.e. ``ironic-api`` and
``ironic-conductor`` services) is not supported, and the ability to launch
a dedicated ``ironic-api`` process with a SQLite database backend will
be an error in the future. In this case, the single process combined
API and Conductor service should be utilized.
fixes:
- |
Database locks with a ``sqlite`` database backend should now be lessened
as the conductor will no longer perform a keepalive heartbeat operation
when the use of SQLite has been detected.