-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
$SYS PUBLISH counters not working for QoS 1 and 2 #1968
Milestone
Comments
ralight
added a commit
that referenced
this issue
Dec 18, 2020
… 1, 2 Closes #1968. Thanks to promahn.
Thank you, I'm surprised this hasn't been noticed before. I've pushed fixes on the |
fAuernigg
pushed a commit
to fAuernigg/mosquitto
that referenced
this issue
Jan 4, 2021
… 1, 2 Closes eclipse#1968. Thanks to promahn.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hey, we are currently trying to find some issue in our setup regarding messages not being correctly forwarded to subscribers on a topic.
To find the issue we where trying to make use of the PUBLISH counters that can be found under
$SYS/broker/publish/messages/dropped
,$SYS/broker/publish/messages/received
and$SYS/broker/publish/messages/sent
.However we noticed that the counters do not seem to increase.
You can see that only when subscribing via QoS 0 the value of
messages/sent
increments by one meaning that only in that case the message we are receiving by subscribing is counted.For the value of
messages/received
I can see that it only increments for messages published via QoS 0 and 1. Messages with QoS 2 do not increment the count.I'm not sure about the
messages/dropped
counter as I was unable to easily produce a test case but we did not observe the count ever going up while we are pretty sure that we hitmax_queued_messages
because of the low default value in the older version.We started with version 1.6.3 and decided to upgrade to 2.0.3 after we noticed the issue. However we can observe the same issue with the newer version.
The text was updated successfully, but these errors were encountered: