Hi David, Thanks for your reply.
Yep, it seems like it's just part of slurm's routine to determine what, if any, resources are available; it seems to look at all nodes, allocated or otherwise, thus many with 'low' free memory. In short, nothing to worry about. As to the verbosity level, I'm also seeing the levels defined on the scontrol man page. I should have done my homework before asking on that one! Cheers, Daniel On 01/08/2013 02:58 PM, Bokassa wrote: > > Hi, I think it is indeed telling you the host does not have enough free > memory as > some it is probably already allocated. You can use 'top -b -n1' to check > the available memory on the host, or some other linux command like > 'free'. This is just a debug message. > > Verbosity level 7 is equivalent to debug3 indeed. The log levels are > enums defined in the log.h file. > > David > > > > > /David/Bigagli > www.davidbigagli.com <http://www.davidbigagli.com> > > > On Tue, Jan 8, 2013 at 2:06 PM, Daniel Petersen > <[email protected] <mailto:[email protected]>> wrote: > > > Greetings! > > When I turn up setdebug verbosity to 7, I'm seeing thousands of entries > in the log like this: > > Jan 8 13:19:25 t-mn02 slurmctld[2013]: debug3: cons_res: _vns: node > t-cn0932 no mem 9000 < 120000 > > Can anyone suggest how this should be interpreted, and if I should care? > > I think I found the source code which generates this message, in > 'job_test.c'. It looks like the first number is 'free' memory from the > node, and the second number is 'min_mem', which it seems is the minimum > memory defined for the node in slurm.conf. > > I suppose it's the first number that's confusing me; it seems like such > a low number for free memory on a system with 128GB. > > As a little aside, it's also a bit confusing that I should only see this > message when verbosity is set to 7, yet the entry says 'debug3'? > > Any insight is appreciated! > > -- > Daniel Petersen > >
