ZeROStage3ParamStatusException: Parameter in Partitioned state, expected Available

ZeRO-3 keeps parameters sharded until they are gathered for use. Code touched a parameter outside a gather context, so it was still partitioned, typically custom forward logic, weight tying, or an initialization step that reads .data directly. This entry explains how to confirm the cause, apply the fix, and separate it from adjacent deepspeed failures.

The literal signature is "ZeROStage3ParamStatusException: Parameter in Partitioned state, expected Available". It is a distributed training failure associated with DeepSpeed ZeRO and optimizer sharding. The line identifies the failing operation or subsystem, while the surrounding evidence decides whether it is the initiating fault or a downstream symptom.

ZeRO-3 keeps parameters sharded until they are gathered for use. Code touched a parameter outside a gather context, so it was still partitioned, typically custom forward logic, weight tying, or an initialization step that reads .data directly. The failure becomes visible at this call site because the operation first requires the missing resource, valid state, healthy peer, or correct result. Earlier log lines and a known-good control carry more causal value than the final wrapper exception.

• The workload stops or loses forward progress after emitting "ZeROStage3ParamStatusException: Parameter in Partitioned state, expected Available".
• A retry on the same configuration reproduces the failure because the causal state has not changed.
• The outer framework exception can hide the rank, node, allocation, or dependency that failed first.
• Increasing timeouts or reducing workload size can suppress the symptom without correcting the cause.

• DeepSpeed ZeRO and optimizer sharding
• production-shaped multi-accelerator workloads
• containerized and bare-metal deployments of the same stack

Apply the following checklist to a small reproduction: each box below is a positive signal that you are looking at this exact failure rather than a sibling in the same taxonomy.

• ✓Find the first occurrence of "ZeROStage3ParamStatusException: Parameter in Partitioned state, expected Available" and preserve at least 100 lines before it.
• ✓Identify which rank, node, device, or process emitted the first related warning.
• ✓the exception names the parameter id; map it back with [ (n,p.ds_id) for n,p in model.named_parameters() ]. Look for direct .data / .weight reads outside forward(), custom weight init after deepspeed.initialize(), tied embeddings, or a checkpoint-load path that assigns weights directly.
• ✓Repeat the same input after the targeted change and require the signature to disappear.
• ✓Resume from job start only after the control passes.

ZeROStage3ParamStatusException: Parameter in Partitioned state, expected Available

Timestamps and exact values vary across runs, but the pattern. An info-level start, an early WARN, an ERROR carrying the symptom. Is the actual fingerprint you should alert on. The Denpex platform flags this combination automatically.

wrap the access in a gather, with deepspeed.zero.GatheredParameters([param], modifier_rank=0): ..., around the code that touches the weight. This changes the condition in the causal diagnosis instead of hiding the outer exception. The repeated control proves ownership before recovery from job start.

# Preserve evidence before restarting
rg -n -i 'error|exception|timeout|failed' <log-file>
nvidia-smi
python -m torch.utils.collect_env

# Find the exact signature in the complete log
rg -n -F -- "ZeROStage3ParamStatusException: Parameter in Partitioned state, expected Available" <log-file>

Adapt the snippet to your framework. The same pattern holds for PyTorch Lightning, Hugging Face Trainer, DeepSpeed, Megatron-LM, and vLLM training wrappers. Where the wrapper exposes a config flag (for examplelr_scheduler_type in Trainer), prefer the flag over the imperative API to keep the schedule declarative and reproducible.

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.

• ZeRO-3 keeps parameters sharded until they are gathered for use. Code touched a parameter outside a gather context, so it was still partitioned, typically custom forward logic, weight tying, or an initialization step that reads .data directly.
• The decisive evidence is the first log line that precedes "ZeROStage3ParamStatusException: Parameter in Partitioned state, expected Available" and differs from a healthy run.
• A nearby failure remains a competing hypothesis until a control separates configuration, capacity, transport, and hardware causes.