You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This bug was reported by a user on the official Zenoh Discord server. Their use-case has 4 publishers put 5Mb messages at 30Hz each, and one session declares a subscriber for each topic.
In this case, one or multiple publishers eventually get stuck in a dropping loop, where all PUT messages are dropped by congestion control and the subscriber does not receive any sample on the respective topics.
To reproduce
Create 4 sessions that declare one publisher each, 30Hz, 5Mb per message.
Create one session that declares 4 subscribers, one for each topic, and recv on each subscriber with a 5 second timeout.
Depending on the machine's specs, you may need to artificially increase its CPU load.
Eventually one or multiple publishers will drop all of their messages, and their respective subscribers will timeout every 5 seconds.
System info
Ubuntu 24.04
Tested on both x86 and ARM CPUs.
Zenoh 1.1.1
The text was updated successfully, but these errors were encountered:
Describe the bug
This bug was reported by a user on the official Zenoh Discord server. Their use-case has 4 publishers put 5Mb messages at 30Hz each, and one session declares a subscriber for each topic.
In this case, one or multiple publishers eventually get stuck in a dropping loop, where all PUT messages are dropped by congestion control and the subscriber does not receive any sample on the respective topics.
To reproduce
System info
The text was updated successfully, but these errors were encountered: