Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add time sync checks across all nodes to verify nodes aren't drifting apart. #180

Closed
DarkSector opened this issue Mar 6, 2024 · 3 comments
Labels

Comments

@DarkSector
Copy link
Contributor

In rare cases, PyTorch will timeout due to drift in system clock across nodes. A pre-check may be useful to diagnose this issue before training run starts.

Add test to hyperpod-precheck.py

@sean-smith
Copy link
Contributor

We can run the command:

srun -N 16 bash -c 'echo "$(hostname): $(date)"' | sort -k2,3

And somehow programmatically make sure the dates are within 1 sec or each other.

Copy link

github-actions bot commented Apr 7, 2024

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Apr 7, 2024
Copy link

github-actions bot commented Jun 6, 2024

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions github-actions bot closed this as completed Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants