Repository navigation
fix(mi355x): stop excluding g09, g14 and g16 - #4828
Merged
Merged
Conversation
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reverts the node exclusions from #4819 and #4824. Those nodes weren't broken: they kept 3–7% VRAM per GPU allocated after a vLLM job, then drained on their own. g09 now reads 0%, and g14 reads 0–2%.
The cluster's Slurm epilog now holds each node in COMPLETING until its GPUs read ≤2% VRAM, for up to 60 minutes. So a node no longer takes the next job until the previous job's memory is released. The job-side gate from #4814/#4827 stays as a backstop. Excluding nodes is no longer needed, and it was costing 3 of the cluster's 10 usable nodes.