[slurm-users] About seff command

Hi guys, I would like to calculate the CPU efficiency and Memory efficiency of slurm jobs. I know that the “seff” command is for this. I’d like to do the same job on my own. When I was studying the source code of the seff command, I saw the code below: my $ncpus = 1; if (exists $job->{'alloc_cp

Re: [slurm-users] How can I get complete field values with without specify the length

Hello, Mevik, I tried the -p option and it worked. Thank you for your reply! Regards, Xiaojing > On Mar 9, 2021, at 3:19 PM, Bjørn-Helge Mevik wrote: > > "xiaojingh...@163.com" writes: > >> I am doing a parsing job on slurm fields. Sometimes when one field is >> too long, slum will limit the

Re: [slurm-users] How can I get complete field values with without specify the length

"xiaojingh...@163.com" writes: > I am doing a parsing job on slurm fields. Sometimes when one field is > too long, slum will limit the length with a “+”. You don't say which slurm command you are trying to parse the output from, but if it is sacctmgr, it has an option --parsable2(*) specifically

Re: [slurm-users] How can I get complete field values with without specify the length

Hello, ole, Thank you for your reply. I forgot the -p option. I really works. Problem solved! Regards, Xiaojing > On Mar 9, 2021, at 2:56 PM, Ole Holm Nielsen > wrote: > > On 3/9/21 5:06 AM, xiaojingh...@163.com wrote: >> Hi, guys >> I am doing a parsing job on slurm fields. Sometimes when

Re: [slurm-users] How can I get complete field values with without specify the length

On 3/9/21 5:06 AM, xiaojingh...@163.com wrote: Hi, guys I am doing a parsing job on slurm fields. Sometimes when one field is too long, slum will limit the length with a “+”. But I prefer to get the complete value of that field. Do you know how can I achieve that? I do not want to specify the

[slurm-users] How can I get complete field values with without specify the length

Hi, guys I am doing a parsing job on slurm fields. Sometimes when one field is too long, slum will limit the length with a “+”. But I prefer to get the complete value of that field. Do you know how can I achieve that? I do not want to specify the length either coz it still cannot guarantee that

Re: [slurm-users] [EXTERNAL] --no-alloc breaks mpi?

On Mar 8, 2021, at 1:35 PM, slurm-users-requ...@lists.schedmd.com wrote: What?s happening is that there?s no SLURM_JOBID (my speculation since I don?t have perms to use ?no-alloc) is set, but SLURM_NODELIST may be set, so its confusing ORTE. Coul

Re: [slurm-users] [EXTERNAL] --no-alloc breaks mpi?

Hi Chris, What’s happening is that there’s no SLURM_JOBID (my speculation since I don’t have perms to use –no-alloc) is set, but SLURM_NODELIST may be set, so its confusing ORTE. Could you list which SLURM env variables are set in the shell in which your running the srun command? Howard From

Re: [slurm-users] [External] Submitting to multiple paritions problem with gres specified

Rather than specifying the processor types as GRES, I would recommending defining them as features of the nodes and let the users specify the features as constraints to their jobs. Since the newer processors are backwards compatible with the older processors, list the older processors as featur

[slurm-users] --no-alloc breaks mpi?

Hi, I’m having an issue with srun's --no-alloc flag with mpi which I can reproduce with a fairly simple example. When I run a simple one-core mpi test program as “slurmUser” (the account that has the --no-alloc privilege) it succeeds: srun -p psfehq -n 1 -o logs/test.log -w psana1507 python ~

[slurm-users] Access to slurm job cgroups in prolog/epilog script

Hi, I am wondering about the exact execution order of prolog scripts and plugins in Slurm with the goal to be able to access the freshly created cgroups (by the task/cgroup plugin) in our prolog/epilog scripts, which run with PrologFlags=Alloc to ensure the tranditional batch system behaviour. We

Re: [slurm-users] Submitting to multiple paritions problem with gres specified

Same problem with 20.11.4: ``` [2021-03-08T19:46:09.378] _pick_best_nodes: JobId=1861 never runnable in partition cpu_e5_2650_v2 [2021-03-08T19:46:09.378] debug2: job_allocate: setting JobId=1861 to "BadConstraints" due to a flaw in the job request (Requested node configuration is not available

[slurm-users] Submitting to multiple paritions problem with gres specified

Hi, On this cluster I have version 20.02.6 installed. We have different partitions for cpu type and gpu types. we want to make it easy for the user who not care where there job runs and for the experienced user they can specify the gres type: cpu_type or gpu I have defined 2 cpu partitions: