Re: [slurm-users] Sreport Query

2020-11-17 Thread navin srivastava
is there a way to find the utilization per Node? Regards Navin. On Wed, Nov 18, 2020 at 10:37 AM navin srivastava wrote: > Dear All, > > Good Day! > > i am seeing one strange behaviour in my environment. > > we have 2 clusters in our environment one acting as a database server and > have

[slurm-users] Slurm version 20.11.0 is now available

2020-11-17 Thread Tim Wickberg
After 9 months of development and testing we are pleased to announce the availability of Slurm version 20.11.0! Slurm 20.11 includes a number of new features including: - Overhaul of the job step management and launch code, alongside improved GPU task placement support. - A new "Interactive

[slurm-users] Just one node getting job allocations

2020-11-17 Thread La Pulga Encuera y Rabiosa
And if I try to run another job and all resources in that one node are all used then the job is pur to pending. I'm running srun getting pseudo terminals allocations to install some Spack packages. this node has 40 cores (2 sockets @20 cores each). same specs and memory size for the other nodes.

Re: [slurm-users] X11 forwarding issues

2020-11-17 Thread Russell Jones
Thank you! I do have X11UseLocalhost set to no, X11Forwarding set to yes: [root@cluster-cn02 ssh]# sshd -T | grep -i X11 x11displayoffset 10 x11maxdisplays 1000 x11forwarding yes x11uselocalhost no No firewalls on this network between the login node and compute node. On Tue, Nov 17, 2020 at

[slurm-users] NoDecay on accounts (or on GrpTRESMins in general)

2020-11-17 Thread Yair Yarom
Hi all, We have around 50 accounts, each has its own GrpTRES limits. We want to add another set of accounts (probably another 50) with different priority which will have GrpTRESMins, such that users could "buy" TRES*minutes with higher priority. For that we require that the GrpTRESMins won't get

Re: [slurm-users] seff Not Caluculating [FIXED?]

2020-11-17 Thread Diego Zuccato
Il 09/11/20 12:53, Diego Zuccato ha scritto: > Seems my corrections actually work only for single-node jobs. > In case of multi-node jobs, it only considers the memory used on one > node, hence understimates the real efficiency. > Someone more knowledgeable than me can spot the error?Seems I