-
Notifications
You must be signed in to change notification settings - Fork 431
Replies: 2 comments · 2 replies
-
Hi, the tag mode, as all UCX APIs, is reliable. Can you pls provide the code (or some snippet) to demonstrate how tag API is used in your application? |
Beta Was this translation helpful? Give feedback.
All reactions
-
I am encountering the same issue. My server must handshake with the client to exchange the worker's address. The client creates an endpoint to the server, then the server invokes ucp_tag_send_nbx and ucp_flush_nbx by the endpoint from the new come-in connection. The client invokes ucp_tag_recv_nbx on the ucp worker to get the server's work address. If the client endpoint's error handler is invoked, the client will reconnect the server. Everything is going well but the client didn't receive the tag message from the server when it restarted several counts. If I use TCP transport, this issue does not occur. It occurred occasionally using the SHM transport. The server prints "send tag message OK" and "flush OK" but the client has not received any message. It has the same issue if I replace TAG API with AM API. @yosefe Could you please provide some suggestions ? |
Beta Was this translation helpful? Give feedback.
All reactions
-
The client showed endpoints created ok but the am handler was not invoked. client:
server:
|
Beta Was this translation helpful? Give feedback.
All reactions
-
If reconnect success. client log:
server log:
|
Beta Was this translation helpful? Give feedback.
-
Hi! I am encountering an issue in my program where it seems that ucp_tag_send_nbx successfully sends data from the sender's side, but the receiver fails to detect the corresponding tag data (packet loss). I am not sure if this is a problem with the tag mode mechanism or if there might be an issue with my code logic.This issue cannot be reproduced consistently
Could anyone please provide some insights or suggestions on how to troubleshoot this issue?
Beta Was this translation helpful? Give feedback.
All reactions