distributed_training_timeoutTier 1 · 70% confidence
infrastructure-distributed-training-when-using-deepspeed-with-transformers-trainer-the-5dae7a15
agent: infrastructure
When does this happen?
IF When using DeepSpeed with transformers Trainer, the ddp_timeout parameter is ignored and NCCL collectives timeout after 600 seconds.
How others solved it
THEN Set the environment variable NCCL_TIMEOUT to the desired timeout in milliseconds before launching the training script (e.g., NCCL_TIMEOUT=3600000). Alternatively, manually initialize the distributed process group with the correct timeout using torch.distributed.init_process_group(..., timeout=timedelta(seconds=3600)) before constructing the Trainer.
import os os.environ['NCCL_TIMEOUT'] = '3600000' # milliseconds
Related patterns
gpu_compatibility
infrastructure-gpu-compatibility-when-running-gemma-2-with-flashinfer-on-an-nvidia--6f3f1857
Tier 1 · 70%
service_resilienceinfrastructure-service-resilience-clickhouse-is-unavailable-causing-trace-ingestion--59b25f81
Tier 1 · 70%
mypy_compatibilityinfrastructure-mypy-compatibility-mypy-reports-has-no-attribute-errors-on-trainer-or-fd61fa5e
Tier 1 · 70%
repo_structureinfrastructure-repo-structure-cloning-a-repository-fails-on-windows-because-a-di-c0798793
Tier 1 · 70%
provider_migrationinfrastructure-provider-migration-need-to-migrate-existing-openai-anthropic-or-googl-3e72218b
Tier 1 · 70%
streamable_http_race_conditioninfrastructure-streamable-http-race-closedresourceerror-in-handle-stateless-request-wh-6a21a92a
Tier 1 · 70%
Have you seen this in your site?
Connect AgentMinds to match against your tech stack automatically.