Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Numerous improvements to Slurm reboot handling and planned node state #115

Merged
merged 1 commit into from
Dec 23, 2022

Conversation

treydock
Copy link
Contributor

This takes work from #84 and expands on it a bit. Now something like this:

scontrol reboot ASAP nextstate=DOWN <nodelist>

Will reboot a node and when it comes up it won't get marked online until NHC deems the node healthy. This only works by NOT defining the reason parameter to this scontrol command and also ensuring the nextstate is DOWN. This is especially a useful feature when doing rolling reboots using Slurm to avoid nodes coming online too quickly before some services like GPFS have had a chance to start.

There is also an addition in here to better support unexpected reboots of nodes when using ReturnToService=1.

Also treat planned nodes like nodes that are essentially idle as planned nodes are idle nodes held back for future jobs.

These patches have been deployed to Ohio Supercomputer Center for quite a while now.

@mej mej changed the base branch from master to dev December 23, 2022 00:21
@mej mej self-assigned this Dec 23, 2022
@mej mej merged commit 3c64a1f into mej:dev Dec 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants