Hi Loris,
as far as i can read the man page, it indicates that the BatchHost (the
node, where the batchscript gets executed) will be one of the types
asked for by --batch.
Moreover, if the allocation does not have any of the requested
--batch-features, the job will start as usually on the firs
Hi Tomo,
"Uemoto, Tomoki" writes:
> Hi,all
> I'm working with slurm 18.08.6 on RHEL7.6
> manager : 1node
> computes: 2nodes (c001:haswell,c002:broadwell)
>
> I am checking the --batch option of the sbatch command.
> The following Features were set for testing.
>
> # scontrol update nodenam
Hi,all
I'm working with slurm 18.08.6 on RHEL7.6
manager : 1node
computes: 2nodes (c001:haswell,c002:broadwell)
I am checking the --batch option of the sbatch command.
The following Features were set for testing.
# scontrol update nodename=c001 Features=haswell
# scontrol update nodename=
Et, Use the job_submit plugin https://slurm.schedmd.com/job_submit_plugins.html
and check the value of job_desc.shared.
-b
On 10/1/19 5:30 AM, Espen Tangen wrote:
Hi all, I need a bullet proof way of checking the setting of the OverSubscribe
parameter from within a runscript.
Where do I find
Hi all, I need a bullet proof way of checking the setting of the OverSubscribe
parameter from within a runscript.
Where do I find this parameter, and/or what would the variable be called.
Regards
Et.
Hi all, I need a bullet proof way of checking the setting of the OverSubscribe
parameter from within a runscript.
Where do I find this parameter, and/or what would the variable be called.
Regards
Et.
