Repository navigation
fix(mi355x): exclude g09 and g16 until their stuck VRAM is reset - #4819
Merged
Merged
Conversation
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
This was referenced Nov 5, 2026
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.
mia1-p01-g09 and mia1-p01-g16 keep 4–7% of VRAM per GPU allocated with no process attached after a job ends, and it does not drain. Two Kimi K3.1 jobs (#4808) sat in the setup hook's drain gate for the full 30 minutes on these nodes and failed. At that level SGLang caps
max_running_requestsbelow the high-concurrency points, so the gate is right to refuse them; the nodes need a GPU reset. Until then, Slurm submissions on mi355x-amds exclude both nodes. Remove the exclusion once they read 0% after a job.