-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
HTTP API endpoint that returns queue metrics runs into an exception #11886
Comments
Sounds similar to #10931. Perhaps this PR solved this problem for some, but not all metrics? |
@mkuratczyk There is a duplicated 'consumers' key, so not the same issue. #10931 deals with elements that contain lists and sorts them. I'm having a look at this one |
@dcorbacho
Which ofc is faulty json and just weird. I assume its somewhere in the logic to query the different nodes (who due to a partition, ended up with different world views), and merging the results, something goes wrong? i.e in say Unfortunately I have not been able to reproduce, or debug while its actually happing. |
@alexnkdev @SimonUnge If you can provide the steps to reproduce, we might be able to look into this. The metrics subsystem is quite complex and is not obvious to me where we are introducing the duplicates. I could not reproduce it either. Also, a patch would be very welcome ;) |
@dcorbacho we have more logs, I'll try to understand what happened and see if we can reproduce |
Describe the bug
We noticed increasing amount of these exceptions in our brokers.
Reproduction steps
Unknown
Expected behavior
No crash
Additional context
Broker is running rabbit 3.13.3
Policy AWS-DEFAULT-CLASSIC-QUEUES-POLICY-CLUSTER-MULTI-AZ definition:
The text was updated successfully, but these errors were encountered: