What does this failure look like in production?

In production this failure typically appears during the first tens-to-hundreds of training steps: loss curves become non-monotonic, validation metrics plateau above the baseline, and downstream checkpoints either diverge or fail to improve. Engineers frequently misread it as data drift when the underlying mechanism is a single root cause rank encountered a genuine failure (gpu oom, xid 31/79, host oom killer, network link down). Validating against the symptom list in this entry is the fastest way to confirm the diagnosis.

Is this a hardware or a software issue?

Distributed Communication failures can look like either layer depending on the symptom. The discriminator is the resolution of the symptom to the recommended fix: if applying the steps under "How to fix it" eliminates the symptom, this is a software/configuration class issue regardless of the hardware it surfaced on. Repeat the fix on a fresh node to confirm.

How long does the fix typically take?

Most resolutions from this entry take 10 to 30 minutes of engineer time once the diagnosis is confirmed. Long fixes come from skipping the diagnosis step and chasing apparent symptoms (validation drift, memory growth, slow throughput) instead of the actual root cause listed above. Apply the fix in a small experiment first, then roll it forward.

Does this affect inference or only training?

Primarily this is a distributed communication failure observed during training, but the same misconfiguration can leak into downstream evaluation and serving. Treat the prevention checklist as a guardrail: any pipeline that touches a trained checkpoint should re-validate the failure mode before promoting the model.

What's the cheapest way to confirm this is the problem?

Cheapest signal: reproduce the symptom on a 1-GPU toy run with the same configuration. If the toy run exhibits the same behavior, the cause is the configuration rather than the cluster. If only the multi-GPU run is affected, the failure is a distributed interaction, so Large-scale distributed training (64+ GPUs) is the most likely layer to inspect.

Can the Denpex platform detect this automatically?

Yes. Denpex correlates the symptoms in this entry against your training logs in real time and surfaces the failure taxonomy, root cause, and exact remediation command on the console. Three full diagnoses are included free during signup, and the encyclopedia entry you are reading is generated from the same signal library that powers the platform.

What related failures should I check next?

Closely related failures cluster around #nccl, #cascade, #timeout. After applying this fix, validate against the related entries below to confirm no overlapping cause is masking as this one. Engineers routinely discover that the dominant failure mode is actually a second, sibling failure compounded on top.

Will this recur after the fix?

Applied once with the prevention checklist, this failure does not recur under normal operation. The recurring variant most engineers encounter is the re-emergence of the same symptom on a different model or stack after nccl is upgraded. Pin compatible versions and rerun the prevention smoke test on every dependency change.

Is there a fingerprint I can monitor?

Yes. NCCL timeout detected on >50% of ranks in the job is the highest-signal fingerprint. Wire a metric or alert on that signal (or its absence after the fix) so you can detect the recurrence automatically. The Denpex platform encodes this exact fingerprint and surfaces it directly in the dashboard.

What is the official documentation that covers this?

Reference documentation is listed in the References section at the bottom of this entry. The most authoritative URLs are the upstream framework docs and the issue trackers cited; the Denpex entry synthesizes both into the executive, engineer, and on-call perspectives so each audience can act without reading every linked source.

Does this entry include working code?

Yes. The "Code Examples" section contains copy-paste-ready snippets that target the most common stacks (PyTorch, Hugging Face Trainer, DeepSpeed, Megatron-LM, vLLM/Transformers). Each snippet is annotated with why it works so you can adapt the pattern to your own framework without losing fidelity.

NCCL Timeout Cascade from Single Rank Failure

Q: How does this scale from 1 GPU to 1000 GPUs?

At single-GPU scale the symptom usually looks like slow convergence or a single anomalous loss value. At 64+ GPU scale, distributed interactions amplify a single root cause rank encountered a genuine failure (gpu oom, xid 31/79, host oom killer, network link down) through collectives, and the failure can manifest as a full job abort. Always reproduce the fix at the smallest cluster configuration that still exhibits the symptom before promoting to production scale.

A single rank failure cascades into mass NCCL timeouts across most or all ranks as they wait at a collective barrier. The cascade signature is one rank failing first, followed by a wave of timeouts on all other ranks.

Quick answer

A single rank failure cascades into mass NCCL timeouts across most or all ranks as they wait at a collective barrier.

Root cause: A single root cause rank encountered a genuine failure (GPU OOM, Xid 31/79, host OOM killer, network link down). All other ranks are healthy. They only timed out because they were waiting for the failed rank at the collective barrier.
Recommended fix: Find the root cause rank: compare timestamps across all NCCL timeout messages; the earliest is the root
How Denpex helps: Denpex investigates NCCL Timeout Cascade from Single Rank Failure using the evidence you provide or your connected workload collects. Earlier rank, host or application evidence is needed to distinguish an initiating failure from a downstream report.

Distributed Communication#nccl#cascade#timeout#distributed#collective#barrier

What this failure is

NCCL Timeout Cascade from Single Rank Failure is a Distributed Communication failure seen during ML training runs. A single rank failure cascades into mass NCCL timeouts across most or all ranks as they wait at a collective barrier. The cascade signature is one rank failing first, followed by a wave of timeouts on all other ranks. Common tags: Nccl, Cascade, Timeout, Distributed.

Live diagnosis, no signup

Is this what broke your run? Paste your log.

You're reading about NCCL Timeout Cascade from Single Rank Failure. Paste your own traceback and relevant evidence for an investigation of your workload, with a next action or a specific missing fact. A reference entry does not establish your cause. No account or card for the free diagnosis. Review data handling before submitting sensitive logs.

Before uploading, review cloud data handling and local options.

training_logs.txt

No log to hand? Try one:

Upload or drop a plain-text log

Upload your log file. Large files are processed in your browser. Only selected evidence is submitted when you run diagnosis.

3 free diagnoses/day

Why it happens (the mechanism)

A single root cause rank encountered a genuine failure (GPU OOM, Xid 31/79, host OOM killer, network link down). All other ranks are healthy. They only timed out because they were waiting for the failed rank at the collective barrier. The cascade is not a network issue. It is a mathematical certainty: all ranks must participate in every collective. Taken together, these mechanisms explain why the failure is reproducible, why it tends to surface on specific workloads or scales, and why generic mitigation attempts often fall short without addressing the underlying cause.

What you'll observe

Single GPU/rank fails (OOM, Xid, host crash)
All other ranks wait at the next collective barrier for the failed rank
NCCL watchdog timeout fires on every waiting rank simultaneously
Logs show NCCL timeout detected on X/Y ranks where Y is most of the cluster

Common symptoms and what they mean

Symptom	Why it happens
NCCL timeout detected on >50% of ranks in the job	A single root cause rank encountered a genuine failure (GPU OOM, Xid 31/79, host OOM killer, network link down)
One rank consistently has the earliest error timestamp	All other ranks are healthy. They only timed out because they were waiting for the failed rank at the collective barrier
All downstream errors are identical NCCL timeout messages	The cascade is not a network issue. It is a mathematical certainty: all ranks must participate in every collective
No independent errors on the downstream ranks. They only timed out waiting	A single root cause rank encountered a genuine failure (GPU OOM, Xid 31/79, host OOM killer, network link down)

Which systems are affected

Large-scale distributed training (64+ GPUs)
Any NCCL-based training where a single rank failure blocks all collectives
Jobs without elastic training or automatic rank replacement

How to confirm this is the problem

Use this checklist to test the hypothesis against a small reproduction. No single line proves the root cause, so preserve the preceding events and compare one variable at a time.

✓Reproduce the failure from a clean checkpoint/seed: the symptom must appear without warm-up state from a previous run.
✓Verified signal present: NCCL timeout detected on >50% of ranks in the job
✓Verified signal present: One rank consistently has the earliest error timestamp
✓Verified signal present: All downstream errors are identical NCCL timeout messages
✓Verified signal present: No independent errors on the downstream ranks. They only timed out waiting
✓A targeted fix from the "How to fix it" section eliminates or substantially reduces the symptom within one validation pass.

Root cause

A single root cause rank encountered a genuine failure (GPU OOM, Xid 31/79, host OOM killer, network link down)
All other ranks are healthy. They only timed out because they were waiting for the failed rank at the collective barrier
The cascade is not a network issue. It is a mathematical certainty: all ranks must participate in every collective

The fix and how to prevent it

The fix and the prevention pattern

The root cause is on this page and stays free. A free account adds the exact remediation steps, saved history, and the fix on every entry in the encyclopedia.

No credit card. Daily allowance follows verified trust tier. Instant access.

Diagnose this failure in VS Code

Select the traceback or open the failed terminal, then run Denpex locally to see the initiating rank, collateral failures, exact fix, and verification command without uploading the log.

Install the free VS Code extension

NCCL errors in context

NCCL is where a distributed job reports failure, which is not the same as where it failed. The hub lists every common NCCL error next to what it actually indicates, and the environment variables that tell them apart.

Compare every nccl error side by side

Related failures to investigate next

Nccl Timeout often co-occurs with this failure because both share underlying assumptions about distributed communication; if you fix this entry but still see drift, validate the related primary cause next. nccl timeout →

Nccl Net Topology often co-occurs with this failure because both share underlying assumptions about distributed communication; if you fix this entry but still see drift, validate the related neighboring cause next. nccl net topology →

References

Don't just read the fix, diagnose your run

The encyclopedia tells you what went wrong. Denpex tells you what went wrong in YOUR training run. With your logs, your config, and your stack.

Diagnose your logs free Compare a solved incident Browse all failures

Related Distributed Communication errors

NCCL Collective Operation Timeout

Distributed Communication · critical

NCCL Network Topology Lookup Failure (NIC Fusion)

Distributed Communication · high