Replies: 2 comments 3 replies
-
Thank you for reporting the issue. We can improve the messages log of course. You could implement your Or you can implement your strategy from scratch starting from the |
Beta Was this translation helpful? Give feedback.
2 replies
-
We will add a client identity to better understand the logs. The identifier will be only client side, something like:
So in the logs you will see:
instead of:
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I have some new findings around RMQ producers and streams. I have a variety of stream queues that have a TTL of 21 days. The sum of all queued entities is around 1 billion.
The more data I collect the more I am struggling with RabbitMQ. This has some weird side effect that you can see below.
RabbitMQ Version: 3.13.0-rc.2
Erlang Version: 26.1.2
Client Version: 1.7.4
OS: Windows Server 2019
Now my question: Is there anything I can do to prevent this continuous reconnecting? I have the feeling this is filling up the ETS tables within RabbitMQ until the high watermark is reached, but thats just a guess.

Furthermore is it possible to improve the logging at some points, e.g.
Beta Was this translation helpful? Give feedback.
All reactions