Skip to content

S26-E7: reject verl with expert parallelism; require fsdp2 strategy - #283

Closed
michaellchung wants to merge 1 commit into
s25-finalfrom
s26-e7-verl-megatron
Closed

michaellchung wants to merge 1 commit into
s25-finalfrom
s26-e7-verl-megatron

Conversation

@michaellchung

Copy link
Copy Markdown
Contributor

Decision record for E7: yeto's verl adapter stays FSDP2-only this round (a Megatron backend would rewrite export, hashing, cuts, sampler updates and resume checks; MoE/EP is served by the Miles backend).

  • verl run config rejects EP>1 with a message pointing to the Miles backend.
  • stage1 rejects a verl backend whose strategy is not fsdp2.

Tests: new unit tests; related files 91 passed. The GPU comparison plan (TE vs SequentialMLP under EP8) is on hold.

🤖 Generated with Claude Code

…ason

The verl Megatron engine (the only verl path with EP) is not wired into
the yeto adapter; EP runs use the Miles backend. check_expert_parallel
now names the decision and the backend to use, and stage1 refuses a
verl trainer.verl.strategy other than fsdp2.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@michaellchung

Copy link
Copy Markdown
Contributor Author

Closing: all commits of s26-e7-verl-megatron (head 41660068) are already in main (verified with git merge-base --is-ancestor; main = 1f83be1d). The content landed through the stacked merges of #269 / #279 / #292. GitHub cannot retarget this PR to main ("no new commits"), so it is closed rather than merged. The branch is kept.

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.

2 participants