Hi Marcin, Try with sdiag for getting info about how scheduling is doing:
watch -n1 sdiag Maybe you can improve the situation tweaking the scheduling configurable parameters. On 02/27/2013 08:06 PM, Marcin Stolarek wrote: > Hi all, > > I have a problem with our slurm installation, in slurmctld logs I see > a lot of: > > Feb 27 18:18:29 sqot slurmctld[2123]: Warning: Note very large > processing time from _slurm_rpc_dump_jobs: usec=122273169 > Feb 27 18:18:30 sqot slurmctld[2123]: debug2: _slurm_send_timeout: > Socket no longer there > Feb 27 18:18:30 sqot slurmctld[2123]: debug3: slurm_msg_sendto: peer > has disappeared for msg_type=2004 > Feb 27 18:18:30 sqot slurmctld[2123]: server_thread_count over limit > (256), waiting > Feb 27 18:18:30 sqot slurmctld[2123]: debug3: Processing RPC: > REQUEST_JOB_INFO from uid=0 > > any hint how to fix this situation? > > cheers, > marcin > WARNING / LEGAL TEXT: This message is intended only for the use of the individual or entity to which it is addressed and may contain information which is privileged, confidential, proprietary, or exempt from disclosure under applicable law. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, you are strictly prohibited from disclosing, distributing, copying, or in any way using this message. If you have received this communication in error, please notify the sender and destroy and delete any copies you may have received. http://www.bsc.es/disclaimer
