Skip to content

EnforcePartLimits=ANY default#211

Open
elelaysh wants to merge 1 commit intomasterfrom
feat/EnforcePartLimits
Open

EnforcePartLimits=ANY default#211
elelaysh wants to merge 1 commit intomasterfrom
feat/EnforcePartLimits

Conversation

@elelaysh
Copy link
Contributor

@elelaysh elelaysh commented Mar 2, 2026

This will outright reject jobs that requests more nodes or more than MaxMemPerCPU, MaxMemPerNode, MinNodes, MaxNodes, MaxTime, AllocNodes, AllowAccounts, AllowGroups, AllowQOS, and QOS usage than is available in any of the requested partitions.

If submitting to multiple partitions and one partitions fits, it will be used (contrary to EnforcePartLimits=ALL).

This will outright reject jobs that requests more nodes
or more than MaxMemPerCPU, MaxMemPerNode, MinNodes, MaxNodes, MaxTime,
AllocNodes, AllowAccounts, AllowGroups, AllowQOS, and QOS usage
than is available in any of the requested partitions.

If submitting to multiple partitions and one partitions fits, it will
be used (contrary to EnforcePartLimits=ALL).
@elelaysh elelaysh requested a review from a team as a code owner March 2, 2026 13:10
Copy link

@gemini-code-assist gemini-code-assist bot left a 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 introduces EnforcePartLimits: ANY as a new default for the Slurm configuration. This is a sensible change that improves user experience by providing faster feedback on job submissions. The implementation is correct. I've added a specific comment regarding test coverage. Additionally, since this changes a default behavior, please consider documenting this in the project's CHANGELOG or release notes to inform users.

SlurmctldSyslogDebug: info
SlurmdSyslogDebug: info
PropagateResourceLimitsExcept: MEMLOCK
EnforcePartLimits: ANY

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

While this is a sensible new default, changes to default behavior should be accompanied by tests to prevent future regressions. Please consider adding a test that verifies this configuration is correctly applied, for instance by checking the output of scontrol show config in a molecule test.

@elelaysh elelaysh requested a review from sjpb March 2, 2026 13:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant