On 11/5/20 7:14 AM, navin srivastava wrote:
Thank you all for the response.
but my question here is
I have already built a new server slurm 20.2 with the latest DB. my
question is, shall i do a mysqldump into this server from existing server
running with version slurm version 17.11.8 and
Hi Navin,
On 11/4/20 10:14 pm, navin srivastava wrote:
I have already built a new server slurm 20.2 with the latest DB. my
question is, shall i do a mysqldump into this server from existing
server running with version slurm version 17.11.8
This won't work - you must upgrade your 17.11
Thank you all for the response.
but my question here is
I have already built a new server slurm 20.2 with the latest DB. my
question is, shall i do a mysqldump into this server from existing server
running with version slurm version 17.11.8 and then i will upgrade all
client with 20.x followed
We have had a couple of nodes enter a DRAINED state where scontrol
gives the reason as
Reason=slurm.conf
In looking at the SlurmCtlD log we see pairs of lines as follows
update_node: node nid00245 reason set to: slurm.conf
update_node: node nid00245 state set to DRAINED
A search of the
Hi,
We have Hyper-threading/SMT enabled on our cluster. It's challenging to fully
utilize threads, as Brian suggests. We have a few workloads that benefit from
it being enabled, but they represent a minority of our overall workload.
We use SelectTypeParameters=CR_Core_Memory. This
JC,
One thing you will start finding in HPC is that, by it's goal,
hyperthreading is usually a poor fit.
If you are properly utilizing your cores, your jobs will actually be
slowed by using hyperthreading. They are not 'extra' cores, but a
method of swapping a core to a different workload
