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
{{ message }}
This repository has been archived by the owner on Dec 4, 2023. It is now read-only.
I see that with link routing, we have two endpoints in the router and each of them has a "peer". When router stats are read, these two endpoints are taken into account so sender++ and receiver++, the reason why we have Senders=1, Receivers=1 even if I attach only a receiver but considering that it's link routing we have also a sender (on the broker) ... so it's right but ... it shouldn't be the stats that the user would see right ? The user would see the only one receiver taken into account.
Then the stats are got two times in a row. It's because the same information are taken from the co-located router deployed with the broker. The function for getting counters is executed twice (one for every router). So the reason why Senders=2, Receivers=2.
So what I see is that in router_stats.js the routers list has two entries, so the count_by_address function is executed twice and there for the topic link both the in/out endpoints are counted as sender/receiver.
From @ppatierno on April 6, 2017 13:18
When a receiver attaches on a topic, the "addresses" tab reports Senders = 2, Receivers = 2 as values.
Copied from original issue: EnMasseProject/routilities#3
The text was updated successfully, but these errors were encountered: