<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p>OK, feeling a bit silly about having sent this after
re-re-reading the man page for slurm.conf... and discovering the
AccountingStorageBackupHost setting.</p>
<p>Sorry for wasting the time of anyone who read that :)</p>
<p>Xand<b><br>
</b></p>
<div class="moz-cite-prefix">On 15/02/2022 15:46, Xand Meaden wrote:<br>
</div>
<blockquote type="cite" cite="mid:1d27ad43-44d7-e4d3-c218-2fdd6de7e033@kcl.ac.uk">Hello,
<br>
<br>
I'm wondering what others are doing to make their slurmdbd service
resilient? We have the following setup right now:
<br>
<br>
- two VMs running slurmctld (and also slurmdbd)
<br>
- shared storage for StateSaveLocation using CephFS
<br>
- three-way mysql cluster using Percona XtraDB
<br>
<br>
However I can see no "Slurm native" way to make slurmdbd resilient
- there is no option for a backup server in slurm.conf. I naively
tried setting the AccountingStorageHost to "localhost" but this
only worked on the primary control node.
<br>
<br>
Can we use something like Keepalived to present slurmdbd running
on both control nodes via a floating IP, or will this cause
complications with Slurm's use of it?
<br>
<br>
Thanks for any advice,
<br>
Xand
<br>
<br>
<br>
</blockquote>
<pre class="moz-signature" cols="72">--
Xand Meaden
Senior Research Infrastructure Engineer
e-Research
King's College London</pre>
</body>
</html>