Skip to content

Multi-node eval hang due to rank-0-only train_loader iteration desynchronization #11

@water-vapor

Description

@water-vapor

In pretrain.py, rank 0 iterates train_loader just to print a length:

URM/pretrain.py

Line 909 in 41de2c3

for set_name, batch, global_batch_size in train_loader:

This advances the dataset iterator only on rank 0. On multi-node runs, ranks become desynced, and the second evaluation hangs at the metric dist.reduce (NCCL timeout) near the end of eval. Removing line 909-910 (and the print statement) fixes the hang. Did you observe similar behaviors with the codebase?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions