n srivastava
> > *Sent:* Friday, July 10, 2020 6:24 AM
> > *To:* Slurm User Community List
> > *Subject:* Re: [slurm-users] changes in slurm.
> > Thank you for the answers.
> >
> > is the RealMemory will be decided on the Total Memory value or total
> >
To:* Slurm User Community List
*Subject:* Re: [slurm-users] changes in slurm.
Thank you for the answers.
is the RealMemory will be decided on the Total Memory value or total
usable memory value.
i mean if a node having 256GB RAM but free -g will tell about only 251 GB.
deda1x1591:~
If you run slurmd -C on the compute node, it should tell you what slurm
thinks the RealMemory number is.
Jeff
From: slurm-users on behalf of navin
srivastava
Sent: Friday, July 10, 2020 6:24 AM
To: Slurm User Community List
Subject: Re: [slurm-users
Thank you for the answers.
is the RealMemory will be decided on the Total Memory value or total usable
memory value.
i mean if a node having 256GB RAM but free -g will tell about only 251 GB.
deda1x1591:~ # free -g
total used free sharedbuffers cached
Mem:
Navin,
1. you will need to restart slurmctld when you make changes to the
physical definition of a node. This can be done without affecting
running jobs.
2. You can have a node in more than one partition. That will not hurt
anything. Jobs are allocated to nodes, not partitions, the
Hi Team,
i have 2 small query.because of the lack of testing environment i am unable
to test the scenario. working on to set up a test environment.
1. In my environment i am unable to pass #SBATCH --mem-2GB option.
i found the reason is because there is no RealMemory entry in the node
definition
