On 20/12/22 6:01 pm, Brian Andrus wrote:
You may want to dump the database, find what table/records need updated and try updating them. If anything went south, you could restore from the dump.
+lots to making sure you've got good backups first, and stop slurmdbd before you start on the backups and don't restart it until you've made the changes, including setting the rollup times to be before the jobs started to make sure that the rollups include these changes!
When you start slurmdbd after making the changes it should see that it needs to do rollups and kick those off.
All the best, Chris -- Chris Samuel : http://www.csamuel.org/ : Berkeley, CA, USA
