deepseek-ai/DeepEP
1
0
Fork 0
mirror of https://github.com/deepseek-ai/DeepEP.git synced 2026-11-05 00:47:32 +00:00
Code Issues 308 Projects Packages Wiki Activity

[GH-ISSUE #570] Timeout message is printed in barrier_block #350

New issue
Open
opened 2026-10-26 09:58:58 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-10-26 09:58:58 +00:00
Owner
Copy link

Originally created by @yanminjia on GitHub (Jan 21, 2026).
Original GitHub issue: https://github.com/deepseek-ai/DeepEP/issues/570

When we train MoE LLM by going with Megatron empowered by DeepEP for EP communication, Megatron will hang randomly with below error messages printed in the output log:

DeepEP timeout check failed: rank = 6, thread = 0, value = 0)
DeepEP timeout check failed: rank = 6, thread = 1, value = 0)
DeepEP timeout check failed: rank = 6, thread = 2, value = 0)
DeepEP timeout check failed: rank = 6, thread = 3, value = 0)
DeepEP timeout check failed: rank = 6, thread = 4, value = 0)
DeepEP timeout check failed: rank = 6, thread = 5, value = 1024)
DeepEP timeout check failed: rank = 6, thread = 6, value = 0)
DeepEP timeout check failed: rank = 6, thread = 7, value = 0)
DeepEP timeout check failed: rank = 2, thread = 0, value = 0)
DeepEP timeout check failed: rank = 2, thread = 1, value = 0)
DeepEP timeout check failed: rank = 2, thread = 2, value = 0)
DeepEP timeout check failed: rank = 2, thread = 3, value = 0)
DeepEP timeout check failed: rank = 2, thread = 4, value = 0)
DeepEP timeout check failed: rank = 2, thread = 5, value = 1024)
DeepEP timeout check failed: rank = 2, thread = 6, value = 0)
DeepEP timeout check failed: rank = 2, thread = 7, value = 0)

In this case, with CP enabled, the EP communiction group is unfolded along CP dimention.

By checking DeepEP code, we understood that this message is printed by barrier_block which used to sync up NVL ranks within a node. As shown in the above message, it looks the rank with local id 5 failed to go into the barrier_block.

We can duplicate this situation, within a 2-nodes environment by training a customized small LLM, when get a RNIC port down. But in our large-scaled cluster, we didn't observe the alarms of port up/down events when this problem happened.

In our cluster environment, NVSHMEM 3.3.9 is used.

It would be highly appreciated if any other clue or thought. Many thanks.

Originally created by @yanminjia on GitHub (Jan 21, 2026). Original GitHub issue: https://github.com/deepseek-ai/DeepEP/issues/570 When we train MoE LLM by going with Megatron empowered by DeepEP for EP communication, Megatron will hang randomly with below error messages printed in the output log: > DeepEP timeout check failed: rank = 6, thread = 0, value = 0) > DeepEP timeout check failed: rank = 6, thread = 1, value = 0) > DeepEP timeout check failed: rank = 6, thread = 2, value = 0) > DeepEP timeout check failed: rank = 6, thread = 3, value = 0) > DeepEP timeout check failed: rank = 6, thread = 4, value = 0) > DeepEP timeout check failed: rank = 6, thread = 5, value = 1024) > DeepEP timeout check failed: rank = 6, thread = 6, value = 0) > DeepEP timeout check failed: rank = 6, thread = 7, value = 0) > DeepEP timeout check failed: rank = 2, thread = 0, value = 0) > DeepEP timeout check failed: rank = 2, thread = 1, value = 0) > DeepEP timeout check failed: rank = 2, thread = 2, value = 0) > DeepEP timeout check failed: rank = 2, thread = 3, value = 0) > DeepEP timeout check failed: rank = 2, thread = 4, value = 0) > DeepEP timeout check failed: rank = 2, thread = 5, value = 1024) > DeepEP timeout check failed: rank = 2, thread = 6, value = 0) > DeepEP timeout check failed: rank = 2, thread = 7, value = 0) In this case, with CP enabled, the EP communiction group is unfolded along CP dimention. By checking DeepEP code, we understood that this message is printed by barrier_block which used to sync up NVL ranks within a node. As shown in the above message, it looks the rank with local id 5 failed to go into the barrier_block. We can duplicate this situation, within a 2-nodes environment by training a customized small LLM, when get a RNIC port down. But in our large-scaled cluster, we didn't observe the alarms of port up/down events when this problem happened. In our cluster environment, NVSHMEM 3.3.9 is used. It would be highly appreciated if any other clue or thought. Many thanks.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
hybrid-ep
chore/remove-clang-format-yapf
v2.5
nvDev
try-fix-cu128
mori-ep
antgroup-opt
compat-old-torch
add-linter
eager-rdma
v1.2.1
Labels
Clear labels   
pull-request
Mirrored from GitHub Pull Request

No labels
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
deepseek-ai/DeepEP#350
No description provided.