-
Notifications
You must be signed in to change notification settings - Fork 781
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
Incoming and outgoing messages count do not match #316
Comments
I also noticed the same behaviour. |
One scenario I can think of is that you send messages in batches but receive either in smaller batches or one-by-one. |
I have the same behaviour and think it depends on the ReceiveMode. |
Hi @JelmerOffenberg Did you ever get an answer to this question? I am seeing the same in our SB queue more outgoing messages then incoming. |
We are seeing the same behavior, has anyone found an answer to this? |
Any progress with this strange behavior? Is there a viable explanation of this variance of values? |
Team, Is there is resolution or fix for this issue. I am also facing mismatch in sum of Incoming Messages and Outgoing messages. The messages are being pushed to topic one by one, where as, there is a webjob sceduled to read messages from topic in bulk mode. However, this behavior is strange. If i stop reading the messages, push all the messages, and then start reading the messages, then count of Incoming and Outgoing messages match. |
@RobertPinson unfortunately this problem was never resolved for us! We contacted Microsoft support but we received no satisfying answer. Seems like another one of those unexplainable features of Azure services. |
Because these metrics are aggregated in time intervals these can be skewed, for example due to slightly different clocks and retry mechanisms, especially when using a Sum aggregation. We recommend using the Average metric instead. Moreover, this is expected behavior when using topics, as each message in a topic will be replicated to one or more subscriptions. If you run into a specific instance where you see this kind of behavior which can not be explained by the above, please open a new issue, with reproduction steps. |
Description
Queue has session enabled with 5 min lock duration for easy test. I'm reading messages with ISessionClient.AcceptMessageSessionAsync
I'm completing messages when they arrive (no processing delay)
No message lock is lost. My code receives the exact number of messages it sent (no message duplication received)
Actual Behavior
Expected Behavior
Is this how Service Bus works by design? maybe to accomplish the session work? or is the client library actually receiving duplicates and not sending them to my code? or is it just bad metrics on the azure portal?
Thanks
The text was updated successfully, but these errors were encountered: