You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running latest v2.0.2 in a kubernetes cluster (2 replicas). the memory usage is almost constantly growing to absurd values, as you can see on the following graph
In this example it has cleared about 0.5g at one time but still look huge.
I tried to put a memory limit on the container, but as expected this one restart when it hits the limit.
This looks like a memory leak but I'm surprised this hasn't been reported before
edit : FYI the number of connected clients is constant over time
The text was updated successfully, but these errors were encountered:
Looking into this, but haven't been able to reproduce this behaviour yet. Could you please share some more information about how you are using amqproxy? Number of connections (client & upstream), is there high connection churn, etc? How have you configured amqproxy?
Hello,
I'm running latest v2.0.2 in a kubernetes cluster (2 replicas). the memory usage is almost constantly growing to absurd values, as you can see on the following graph
In this example it has cleared about 0.5g at one time but still look huge.
I tried to put a memory limit on the container, but as expected this one restart when it hits the limit.
This looks like a memory leak but I'm surprised this hasn't been reported before
edit : FYI the number of connected clients is constant over time
The text was updated successfully, but these errors were encountered: