Incident Library
Applied filters ComponentGPU hardware and memoryFactorUnverified assumptionOrganisationAlibaba GroupClear allEvery case under the filters, with no sentence; newest first.
Suggested filters Search, and the values found in your words appear here.

Graph

  • Root cause
  • Component
  • Symptom
  • Contributing factor
  • Case

Cases1 case

1 to 1 of 1

  1. Symptoms

    Large LLM training jobs on Alibaba's AI clusters crashed again and again and had to restart from the last valid checkpoint. One of the largest jobs, on 4,096 GPUs in a newly deployed cluster, crashed 40 times in one month, and most crashes reached users only as "NCCL Errors".

    Root cause
    Component
    Contributing factor
    Detection

    Before C4D, users found crashes through NCCL errors and could stay unaware of a stalled job for up to 30 minutes until the PyTorch elastic agent killed it; C4D later detects hangs and slowdowns from collective communication timings within tens of seconds.

    Remediation
    • Allocated 64 backup GPUs on 8 servers for every 1024 GPUs on 128 servers, so that parallel training on any 128 servers of the 136-server pool keeps the same communication and performance
    • Deployed C4D to detect faulty nodes automatically, isolate them and restart the job from the most recent valid checkpoint
    • Saved checkpoints more often, every 10 minutes, to cut the work lost after each crash
    • Enhanced cooling with higher fan speeds and better air conditioning to keep GPUs from overheating
    • Identified and enhanced the most vulnerable components of the system, lowering the average error rate 3.33 times
    Action items
    • Take load variation into account in C4D for more precise slow detection
    Lessons

    Most crash causes are confined to specific nodes or devices, so isolating the faulty component quickly and restarting, while leaving root cause analysis for offline work, removes most of the error-induced downtime. Because synchronous training makes many different faults look like the same communication error, diagnosis has to use the regular rhythm of the workers at synchronisation points rather than the error message, and frequent checkpoints matter because error rates in large clusters are high.

Check your cluster for this

This case involves GPU hardware and memory and NCCL. kubegap audits a Kubernetes cluster for gaps like these, read-only, from Claude Code or Codex; its checks cite public reports like the ones in this library.

By root cause1