We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Discarded event bus messages are still counted as pending. When a message is discarded, the pending count should be corrected.
The text was updated successfully, but these errors were encountered:
Handle event bus discarded messages - closes #96 - fixes #97
fb372bd
e7bef38
cc @jotak
Sorry, something went wrong.
@vietj While fixing this on micrometer I had a quick look on dropwizard too and I thought it was already handled, see https://github.com/vert-x3/vertx-dropwizard-metrics/blob/master/src/main/java/io/vertx/ext/dropwizard/impl/EventBusMetricsImpl.java#L280-L282 => pending gauges are reset.
Or, is there some situations where messages are discarded without the handler being removed?
For micrometer, I believe vert-x3/vertx-micrometer-metrics#98 did fix it, pending count being reset on unregistration.
@jotak yes it happens when a consumer is paused and messages are dropped due to overflow, e.g
MessageConsumer<String> consumer = eventBus.consumer("foo"); consumer.setMaxBufferedMessages(10); consumer.pause(); consumer.handler(msg -> ...); for (int i = 0;i < 10;i++) { eventBus.send("foo", "msg-" + i); } eventBus.send("foo", "msg-11"); // Shall be discarded due to overflow without consumer being unregistered
vietj
No branches or pull requests
Discarded event bus messages are still counted as pending. When a message is discarded, the pending count should be corrected.
The text was updated successfully, but these errors were encountered: