What to do when there are reports of Slurm outages or unexpected behavior?
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
Resolve the issue. Ops has a pretty good handle on these generally. Often we simply restart slurmctld or whatever process is causing the upset.
Tools to investigate causes:
sdiagoutput for remote procedure callssacctfor recent job information- Grafana for node data (https://grafana.ops.rc.uab.edu/grafana/?orgId=1, requires VPN or on-campus)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No target file is named; first locate the documentation structure for operational procedures in this repository. Use the issue's sdiag, sacct, and Grafana references as the investigation starting points, and consider the work done when the response to Slurm outages and unexpected behavior is documented clearly.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100