Hi!

In our site we store the logs and the pid files of slurmctld and slurmdbbd 
daemons on local disk, it is better so to distinguish who is doing what and 
since if a node is down the daemons are not running then there is no need to 
put them on a shared filesystem. For slurmctld we have the state dir and 
jobcomp on a shared active/active filesystem. For slurmdbd we have an 
active/passive filesystem between the master nodes where we store the 
mysql/mariadb database.

I understand that it is your policy to use shared filesystems for those files 
(and in general is not a bad idea) but in this case for slurm control daemons 
you should use local disks (personal opinion).

Anyway, if you insist to use shared fs then I can only think of one solution: 
use symbolic links. E.g.:
@master1: path-of-pidfile-in-slurm.conf -> /sharedfs/slurm/run/master1.pid
@master2: path-of-pidfile-in-slurm.conf -> /sharedfs/slurm/run/master2.pid

Cheers,
Chrysovalantis Paschoulas


On 06/10/2015 04:47 AM, Qianqian Sha wrote:
Hi,

    We store all slurm logs/pids/tmpfiles on a shared disk. logs/pids/tmpfiles 
of different slurmds can be distinguished by nodename(%n) or hostname(%h). But 
it seems that logs/pids path of slurmctld or backup-slurmctld does not support 
%n or %h.

   Any assistance or advice is appreciated.

Thanks.



------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------

Reply via email to