-
Notifications
You must be signed in to change notification settings - Fork 19
Stop slurmd during slurmctld restart #200
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
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @priteau, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request introduces a critical stability improvement for Slurm clusters by ensuring that slurmd
services are temporarily stopped on compute nodes before slurmctld
is restarted due to configuration updates. This proactive measure prevents potential invalid states on compute nodes that could arise from slurmctld
restarting while slurmd
is still active, thereby making Slurm configuration changes safer and more robust without impacting ongoing workloads.
Highlights
- Improved Slurm Stability: This change prevents compute nodes from entering an invalid state when
slurmctld
is restarted due to configuration changes whileslurmd
services are still running. - Conditional
slurmd
Stoppage: A new Ansible task has been added to conditionally stop theslurmd
service on relevant hosts beforeslurmctld
is restarted, specifically when Slurm or GRES configuration files have changed. - No Impact on Running Jobs: The implemented solution has been tested and confirmed not to affect running jobs during the
slurmd
stoppage andslurmctld
restart process.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point by creating a comment using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands on the current page.
Feature | Command | Description |
---|---|---|
Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in pull request comments and review comments. |
Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/
folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request correctly identifies a potential issue with restarting slurmctld
while slurmd
is running and implements a sound strategy to mitigate it by stopping slurmd
services beforehand. The use of flush_handlers
to orchestrate the service restarts is a good approach. My review focuses on a minor inconsistency in the conditions that trigger the slurmd
stop, which could leave a gap in the protection this change provides. I've provided a specific suggestion to address this.
Some Slurm configuration changes can cause compute nodes to go into invalid state if slurmctld is restarted while slurmd services are still running. Stop slurmd services while slurmctld is being restarted. This has been tested not to affect running jobs. Closes #199
e51919d
to
59e1222
Compare
Some Slurm configuration changes can cause compute nodes to go into invalid state if slurmctld is restarted while slurmd services are still running.
Stop slurmd services while slurmctld is being restarted. This has been tested not to affect running jobs.
Closes #199