Hi Carlos,

that's it.

So regarding a) the html documentation is wrong and regarding b) there
was a typo on my side.


Thanks a lot,

        Uwe

Am 20.10.2014 um 14:33 schrieb Carlos Fenoy:
> Hi Uwe,
> 
> Looks like you are missing an "s" at the end of the name. We have:
> 
> SchedulerParameters=max_switch_wait=864000,...
> 
> Regards,
> Carles Fenoy
> Barcelona Supercomputing Center
> 
> On Mon, Oct 20, 2014 at 10:27 AM, Uwe Sauter <uwe.sauter...@gmail.com
> <mailto:uwe.sauter...@gmail.com>> wrote:
> 
> 
>     Hi all,
> 
>     I'm trying to configure the scheduling parameter "max_switch_wait" on
>     14.03.8 but
> 
>     a) there seems to be a mismatch between the html documentation and the
>     salloc/sbatch/srun man pages.
> 
>     b) Slurm doesn't seem to know the parameters referenced in the
>     documentation.
> 
> 
>     Regarding a)
> 
>     Manpages salloc/sbatch/srun reference a parameter called
>     "SchedulerParameters":
> 
>     --switches=<count>[@<max-time>]
>       When a tree topology is used, this defines the maximum count of
>       switches desired for the job allocation and optionally the maximum
>       time to wait for that number of switches. If SLURM finds an
>       allocation containing more switches than the count specified, the job
>       remains  pending  until it either finds an allocation with desired
>       switch count or the time limit expires. It there is no switch count
>       limit, there is no delay in starting the job. Acceptable time formats
>       include "minutes", "minutes:seconds", "hours:minutes:seconds", "days-
>       hours", "days-hours:minutes" and "days-hours:minutes:seconds". The
>       job’s maximum time delay may be limited by the system administrator
>       using the SchedulerParameters configuration parameter with the
>       max_switch_wait  parameter option. The default max-time is the
>       max_switch_wait SchedulerParameter.
> 
>     while http://slurm.schedmd.com/sched_config.html calls this parameter
>     "SchedulingParameters"
> 
>     Regarding b)
> 
>     Trying both variants I cannot get Slurm started:
> 
>     ##### with SchedulerParameter ####
>     [root@controller etc]# service slurm restart
>     scontrol: error: Parsing error at unrecognized key: SchedulerParameter
>     scontrol: error: Parse error in file
>     /opt/system/slurm/14.03.8/etc/slurm.conf line 103:
>     "SchedulerParameter=max_switch_wait=86400"
>     scontrol: fatal: Unable to process configuration file
>     scontrol: error: Parsing error at unrecognized key: SchedulerParameter
>     scontrol: error: Parse error in file
>     /opt/system/slurm/14.03.8/etc/slurm.conf line 103:
>     "SchedulerParameter=max_switch_wait=86400"
>     scontrol: fatal: Unable to process configuration file
> 
>     ##### with SchedulingParameter ####
>     [root@controller etc]# service slurm restart
>     scontrol: error: Parsing error at unrecognized key: SchedulingParameter
>     scontrol: error: Parse error in file
>     /opt/system/slurm/14.03.8/etc/slurm.conf line 103:
>     "SchedulingParameter=max_switch_wait=86400"
>     scontrol: fatal: Unable to process configuration file
>     scontrol: error: Parsing error at unrecognized key: SchedulingParameter
>     scontrol: error: Parse error in file
>     /opt/system/slurm/14.03.8/etc/slurm.conf line 103:
>     "SchedulingParameter=max_switch_wait=86400"
>     scontrol: fatal: Unable to process configuration file
>     ###################################
> 
>     Does anyone know the correct name and usage of this parameter?
> 
>     Thank you.
> 
>     Regards,
> 
>             Uwe
> 
> 
> 
> 
> -- 
> --
> Carles Fenoy

Reply via email to