feat(slurm): support multi-node Dynamo RL jobs - #4
Draft
furionw wants to merge 2 commits into
Draft
Conversation
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.
Based on #3.
Why
The single-node Dynamo launcher owns every process on one host, but Prime's multi-node Slurm template previously could not coordinate one frontend, role-specific workers, shared discovery, and service teardown across ranks. Multi-node aggregate and P/D RL need the parent allocation to own those processes without nested Slurm submissions, while standalone Dynamo inference remains unsupported. Shared-file discovery and explicit completion markers keep worker identity stable and prevent long-lived services from holding a finished allocation.
What Change
Test Plan
Gate evidence:
20260717T181440Z/portable-evidence/summary.jsonpassed both topologies with zero fatal signatures.