Hi Ole,
thanks for your reply.
The curious thing is that when I run "scontrol reboot nextstate=RESUME
", the drain flag of that node is not set (sinfo shows mix@ and
"scontrol show node " shows no DRAIN in State, just
MIXED+REBOOT_REQUESTED), yet no jobs are scheduled on that node until
Hi Tim,
I think the scontrol manual page explains the "scontrol reboot" function
fairly well:
reboot [ASAP] [nextstate={RESUME|DOWN}] [reason=]
{ALL|}
Reboot the nodes in the system when they become idle using the
RebootProgram as
Hi Chris,
thanks a lot for your response.
I just realized that I made a mistake in my post. In the section you
cite, the command is supposed to be "scontrol reboot nextstate=RESUME"
(without ASAP).
So to clarify: my problem is that if I type "scontrol reboot
nextstate=RESUME" no new jobs
On 10/24/23 12:39, Tim Schneider wrote:
Now my issue is that when I run "scontrol reboot ASAP nextstate=RESUME
", the node goes in "mix@" state (not drain), but no new jobs get
scheduled until the node reboots. Essentially I get draining behavior,
even though the node's state is not "drain".
Hi,
from my understanding, if I run "scontrol reboot ", the node
should continue to operate as usual and reboots once it is idle. When
adding the ASAP flag (scontrol reboot ASAP ), the node should go
into drain state and not accept any more jobs.
Now my issue is that when I run "scontrol
