[slurm-users] Slurm 20.02 Dry-Run DB upgrade - Question on the cloned DB

Moshe Mergy moshe.mergy at weizmann.ac.il
Mon Feb 7 08:42:11 UTC 2022

Hi all

I cloned the Slurm DB into a separated node, in order to test and run a Dry-Run DB upgrade.

Slurm 20.02.4 --> 21.08.5 on CentOS 7.6 / MariaDB 5.5.64-1.

according to guide https://wiki.fysik.dtu.dk/niflheim/Slurm_installation#make-a-dry-run-database-upgrade

DB cloning: OK - mysql shows 2 differents DB with same data:

the original DB on Head machine + the cloned DB on the Node.

MY FEAR: destroying the original DB

MY TEST: creating a dummy user on cloned DB and check that it is not present in original DB

Node: slurmdbd is running only (NO slurmd)

Head: slurmdbd, slurmctld are running

1/ On Node "sacctmgr create user dummy" into cloned DB

2/ On Node "sacctmgr show user -s": user dummy is present in cloned DB --> OK

3/ On Head "sacctmgr show user -s": user dummy is NOT present in original DB --> OK


But if I use command "sshare -al" to list the users, the user dummy appears to be present in cloned DB... AND in original DB too...!!


It seems (from manual) that sshare uses slurmctld, which is related to the original DB on Head machine.

So user dummy should NOT be listed with "sshare" command from Head machine. Neither from Node...?!

(And on the other hand, in case sshare does not use slurmctld, but send direct requests to the DB, then the dummy user should be listed (with sshare) only on Node, but NOT on Head machine...)

Are the 2 DBs really separated ?

So I can run the DB upgrade test on this cloned DB without destroying the original DB ?

Thanks a lot for your help!



(Slurm & Mysql novice)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.schedmd.com/pipermail/slurm-users/attachments/20220207/52a54fc0/attachment.htm>

More information about the slurm-users mailing list