multi-node-slurm

Convert single-node Megatron Bridge scripts into multi-node Slurm sbatch jobs.

2.8k|332|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/NVIDIA/skills --skill multi-node-slurm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multi-node-slurm
Source: https://github.com/NVIDIA/skills/tree/main/skills/Megatron-Bridge/multi-node-slurm
Command: npx skills add https://github.com/NVIDIA/skills --skill multi-node-slurm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert single-node Megatron Bridge scripts into scalable multi-node Slurm sbatch jobs and provide structured debugging guidance for common multi-node failures.

Core Features & Use Cases

  • Two-phase launch pattern: srun-native (preferred) and uv run torch.distributed (legacy), with automatic distribution initialization (RANK, WORLD_SIZE, LOCAL_RANK, MASTER_ADDR, MASTER_PORT) derived from SLURM vars.
  • Containerized environments and resource setup, including container mounts, environment variable management, and log organization for multi-node runs.
  • Debugging assistance for NCCL timeouts, OOM sizing for MoE models, and interactive allocation workflows; suitable for scaling Megatron-Bridge scripts to multi-node deployments.

Quick Start

Use when scaling a Megatron-Bridge script from a single node to a multi-node Slurm job, following the two-phase srun workflow.

Frequently Asked Questions about multi-node-slurm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert single-node Megatron Bridge scripts to multi-node Slurm sbatch jobs?

You can convert single-node Megatron Bridge scripts to multi-node Slurm sbatch jobs by applying the two-phase srun-native or uv-run launch pattern, which derives distributed initialization variables like RANK and MASTER_ADDR from Slurm environment variables.

What is the best way to scale distributed training across Slurm cluster nodes?

Scaling distributed training across Slurm nodes is best achieved by generating a structured sbatch job that manages containerized environments, resource allocation, and log organization while ensuring proper distributed initialization for reliable multi-node operations.

Does the multi-node Slurm workflow support both srun-native and uv-run launch methods?

Yes, the multi-node Slurm workflow supports both srun-native, which is the preferred method, and uv run torch.distributed as a legacy approach to initialize distributed training across allocated cluster nodes.

How do I debug NCCL timeouts and OOM sizing for MoE models in distributed training?

You can debug NCCL timeouts and OOM sizing for MoE models during distributed training by utilizing the built-in debugging assistance that provides structured guidance for common multi-node failures and interactive allocation workflows.

Why does my distributed training job fail to initialize across multiple Slurm nodes?

Your distributed training job may fail to initialize across multiple Slurm nodes when environment variables like WORLD_SIZE, LOCAL_RANK, and MASTER_ADDR are not properly derived and configured from the Slurm environment during the launch phase.