We have a host dedicated to slurmdbd and mysql (Ubuntu 24.04, Slurm 24.11.4, mysql 8.0.45).  A couple days ago unattended-upgrades upgraded the MySQL package which triggered a restart of mysql.service which looks to have caused some errors in slurmdbd.  I don't think those errors were permanent, everything looks to be running as per usual currently.

Enough backstory- the question is should we configure the slurmdbd systemd unit to stop slurmdbd before mysql is stopped?  Currently there are minimal dependencies built into the unit:

After=network-online.target remote-fs.target munge.service mysql.service mysqld.service mariadb.service sssd.service
Wants=network-online.target

But nothing to tell systemd to take down slurmdbd when the mysql unit is stopped.  Is there *any* reason we'd want slurmdbd running if mysql wasn't?  Are there any problems I'd cause by creating such a dependency?

I do plan to exclude mysql from future unattended upgrading, but I'd also like to keep our systemd units sensible.

Thanks

 - Michael