NCCL P2P Communication Issue
NCCL peer-to-peer (P2P) communication issues cause pipeline parallelism and tensor parallelism to fail or be slow.
NCCL peer-to-peer (P2P) communication issues cause pipeline parallelism and tensor parallelism to fail or be slow.
What this failure is
NCCL P2P Communication Issue is a Communication failure seen during ML training runs. NCCL peer-to-peer (P2P) communication issues cause pipeline parallelism and tensor parallelism to fail or be slow. Common tags: Nccl, P2p, Nvlink, Communication.
Is this what broke your run? Paste your log.
You're reading about NCCL P2P Communication Issue. Paste your own crash log or traceback below and get the real root cause for YOUR run, not this generic entry. No account, no card. Logs are masked at ingress and never saved to account history.
Want 14 days on the Scale plan?
Request a work-email trial for up to 50 diagnoses a day, alerts, history, and follow-up questions. No credit card or automatic subscription.
Why it happens (the mechanism)
GPUs not connected via NVLink. P2P not enabled in NVIDIA driver. MIG configuration prevents P2P. GPU topology not optimal for P2P. 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
- P2P transfer between GPUs fails
- GPU-to-GPU communication uses PCIe instead of NVLink
- Pipeline parallelism is slow
Common symptoms and what they mean
| Symptom | Why it happens |
|---|---|
| NCCL WARN net send/recv setup | GPUs not connected via NVLink |
| P2P transfer falls back to slower path | P2P not enabled in NVIDIA driver |
| GPU direct access not available | MIG configuration prevents P2P |
Which systems are affected
- Multi-GPU training with NVLink
- Pipeline parallel training
- Tensor parallel training within node
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 WARN net send/recv setup
- ✓Verified signal present: P2P transfer falls back to slower path
- ✓Verified signal present: GPU direct access not available
- ✓A targeted fix from the "How to fix it" section eliminates or substantially reduces the symptom within one validation pass.
The fix and the prevention pattern
The root cause is on this page and stays free. A free account adds the exact remediation steps, keeps your diagnoses instead of discarding them, and unlocks the fix on every entry in the encyclopedia.
Sign up free. Unlock the full analysisNo credit card · 3 free diagnoses · 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 extensionNCCL 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 sideRelated failures to investigate next
Root cause
- GPUs not connected via NVLink
- P2P not enabled in NVIDIA driver
- MIG configuration prevents P2P
- GPU topology not optimal for P2P
The fix and how to prevent it
Unlock the full remediation runbook
14 days on the Scale plan, up to 50 diagnoses a day. Step-by-step remediation, the RMA evidence payload, and multi-node correlation on your own logs. No card, and it does not roll into a subscription.
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.