My understanding is job state directory. Theoretically if you back it up, screw up and lose it, you can restore it and try again. There’s some mention of this in the upgrade docs if I’m not mistaken (as they suggest backing it up in case you mess up during).
-- #BlackLivesMatter ____ || \\UTGERS, |---------------------------*O*--------------------------- ||_// the State | Ryan Novosielski - novos...@rutgers.edu<mailto:novos...@rutgers.edu> || \\ University | Sr. Technologist - 973/972.0922 (2x0922) ~*~ RBHS Campus || \\ of NJ | Office of Advanced Research Computing - MSB C630, Newark `' On Jan 15, 2021, at 13:44, Prentice Bisbal <pbis...@pppl.gov> wrote: Slurm users, I'm planning on moving slurmctld and slurmdbd to a new host. I know how to dump the MySQL DB from the old server and import it to the new slurmdbd host, and I know how to copy the job state directories to the new host. I plan on doing this during our next maintenance window when there are no jobs running on the cluster. However, there will be plenty of jobs in the queue, so my question is this: What will happen to jobs in the queue when I do this? Is the queue information stored in the database or the job state directories, or a third location? How can I make sure I don't lose the state of the queue? -- Prentice
