FWIW, here are the statistics of one of the links at issue: Link <6c92cf7572e:eno12399np0-1423f2c2ed9:enp129s0f0np0> ACTIVE MTU:1500 Priority:10 Tolerance:1500 ms Window:50 packets RX packets:12175437 fragments:9688615/3172386 bundles:106357/731415 TX packets:7688023 fragments:2106920/245873 bundles:202585/676190 TX profile sample:915 packets average:186 octets 0-64:90% -256:2% -1024:6% -4096:1% -16384:1% -32768:0% -66000:0% RX states:2570054 probes:1152299 naks:100121 defs:1057114 dups:210455 TX states:2558618 probes:1151705 naks:275121 acks:139955 retrans:973666 Congestion link:1179509 Send queue max:0 avg:0
And by hang, I mean strace shows the sendmsg() call never returning. I also sometimes see a case where a message goes through one way, but the reply message never arrives, with the same for retransmissions. I do look for the cmsg data on both ends, but I'm not seeing it in these cases. Gary Duzan IT Architect Senior GT.M Core Team ________________________________ From: Duzan, Gary D via tipc-discussion <tipc-discussion@lists.sourceforge.net> Sent: Tuesday, July 15, 2025 10:11 AM To: Duzan, Gary D via tipc-discussion <tipc-discussion@lists.sourceforge.net> Subject: [tipc-discussion] Sends Hanging I'm trying to diagnose an issue with TIPC datagram anycast or group broadcast sends hanging when the receiver processes on another host are waiting in either poll or recvmsg. These are relatively fast machines with 10g ethernet connecting them, and varying amounts of background activity. My first thought was to try adjusting the window settings, but the media/bearer window is maxed out, and the link windows seem to be fixed at 50. Is this the expected behavior? Thanks. Gary Duzan IT Architect Senior GT.M Core Team E: gary.du...@fisglobal.com FIS | Advancing the way the world pays, banks and invests™ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. _______________________________________________ tipc-discussion mailing list tipc-discussion@lists.sourceforge.net https://urldefense.com/v3/__https://lists.sourceforge.net/lists/listinfo/tipc-discussion__;!!AI5hVGByxkJIiw!gZUze6tUrRKCDcInJDYKm1vagC1ieW_kyuGU6w5ahxYwQQ74BR2lGQZJbfo7kkHFFbwX8t8e5tijIBYrQtR2T2B0Dy5SnK4RPidJBPIJ$ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. _______________________________________________ tipc-discussion mailing list tipc-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tipc-discussion
