Skip to content

Deployment of DeepseekV3 on 2*H100 nodes is getting stuck. #4857

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

Open
abhay-tih opened this issue Mar 28, 2025 · 4 comments
Open

Deployment of DeepseekV3 on 2*H100 nodes is getting stuck. #4857

abhay-tih opened this issue Mar 28, 2025 · 4 comments
Assignees

Comments

@abhay-tih
Copy link

Hi all,
I am trying to deploy DeepSeek-V3 on two H100 nodes, but the deployment gets stuck at a certain point. I have already set the required environment variables, including:

  • NCCL_SOCKET_IFNAME
  • NCCL_IB_GID_INDEX=3

Image

When I tried to look into the error using NCCL_DEBUG env variable , the last lines shows this

[Node-A]:[PID]:[Thread] [0] NCCL WARN NET/IB : Got completion from peer [PRIVATE_IP] with error 12, opcode 0, len 0, vendor err 129 (Recv)  
localGid ::ffff:[MASKED_IP] remoteGid ::ffff:[MASKED_IP]  

[Node-A]:[PID]:[Thread] [0] NCCL INFO transport/net.cc:1302 -> 6  
[Node-A]:[PID]:[Thread] [0] NCCL INFO proxy.cc:698 -> 6  
[Node-A]:[PID]:[Thread] [0] NCCL INFO proxy.cc:878 -> 6 [Progress Thread]  

[Node-A]:[PID]:[Thread] [0] NCCL WARN NET/IB : Got completion from peer [PRIVATE_IP] with error 5, opcode 29989, len 29993, vendor err 244 (Recv)  
localGid ::ffff:[MASKED_IP] remoteGid ::ffff:[MASKED_IP]  

[Node-A]:[PID]:[Thread] [0] NCCL INFO transport/net.cc:1302 -> 6  
[Node-A]:[PID]:[Thread] [0] NCCL INFO proxy.cc:698 -> 6  
[Node-A]:[PID]:[Thread] [0] NCCL INFO proxy.cc:878 -> 6 [Progress Thread]  

I am using NCCL version 2.21.5

Has anyone encountered a similar issue, or does anyone have insights on resolving this? Any guidance would be appreciated!

@fzyzcjy
Copy link
Collaborator

fzyzcjy commented Mar 29, 2025

Hi, could you please use py-spy dump -s -p PID_OF_YOUR_PARENT_PROCESS to have a quick check about where it gets stuck?

@HermitSun
Copy link
Contributor

After upgrading to v0.4.4, I also encountered this issue. It returned to normal after rolling back to v0.4.3.

@HermitSun
Copy link
Contributor

And after I disabled cuda graph, it also returned to normal.

@cynial
Copy link

cynial commented Apr 13, 2025

I've encountered a similar situation before, and I resolved it by setting:

export NCCL_SOCKET_IFNAME=bond1  
export NCCL_IB_GID_INDEX=3  

I'm not sure what your NCCL_SOCKET_IFNAME is currently set to, but perhaps you could try changing it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants