botocore ClientError 503 PutObject SlowDown S3 prefix request rate exceeded

S3 throttling (503 SlowDown), request rate exceeded per-prefix limits. This entry explains how to confirm the cause, apply the fix, and separate it from adjacent checkpoint-storage failures.

The literal signature is "botocore ClientError 503 PutObject SlowDown S3 prefix request rate exceeded". It is a data integrity failure associated with distributed checkpoints, object storage, and WebDataset. The line identifies the failing operation or subsystem, while the surrounding evidence decides whether it is the initiating fault or a downstream symptom.

S3 throttling (503 SlowDown), request rate exceeded per-prefix limits. 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 "botocore ClientError 503 PutObject SlowDown S3 prefix request rate exceeded".
• 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.

• distributed checkpoints, object storage, and WebDataset
• 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 "botocore ClientError 503 PutObject SlowDown S3 prefix request rate exceeded" and preserve at least 100 lines before it.
• ✓Identify which rank, node, device, or process emitted the first related warning.
• ✓which prefix is hot (server access logs / CloudWatch 5xxErrors by prefix); request rate vs ~3.5k PUT / 5.5k GET per prefix-second.
• ✓Repeat the same input after the targeted change and require the signature to disappear.
• ✓Resume from retry in place only after the control passes.

botocore ClientError 503 PutObject SlowDown S3 prefix request rate exceeded

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.

exponential backoff (SDK adaptive retry) and cut concurrent writers to the hot prefix. This changes the condition in the causal diagnosis instead of hiding the outer exception. The repeated control proves ownership before recovery from retry in place.

# 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 -- "botocore ClientError 503 PutObject SlowDown S3 prefix request rate exceeded" <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.

• S3 throttling (503 SlowDown), request rate exceeded per-prefix limits.
• The decisive evidence is the first log line that precedes "botocore ClientError 503 PutObject SlowDown S3 prefix request rate exceeded" and differs from a healthy run.
• A nearby failure remains a competing hypothesis until a control separates configuration, capacity, transport, and hardware causes.