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 Use Kubernetes Operator to deploy rabbitmq-cluster. (cluster-operator:2.11.0)
We first built our cluster on rabbitmq:3.10.2 and have been going through 3.11 and 3.12 to upgrade to 3.13.7.
Steps to reproduce the behavior in question
we load this json on startup
(permission and users are removed)
After searching, the expected behavior of my settings is that when a message is received, it is moved to disk after a period of time, so there seems to be no reason why it should be kept in RAM. However, ra_log_ets keeps growing in use and does not get smaller. rabbitmq does nothing until it reaches a high watermark and stops forwarding messages.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Community Support Policy
RabbitMQ version used
3.13.7
Erlang version used
26.2.x
Operating system (distribution) used
Kubernetes 1.29
How is RabbitMQ deployed?
Kubernetes Operator(s) from Team RabbitMQ
rabbitmq-diagnostics status output
See https://www.rabbitmq.com/docs/cli to learn how to use rabbitmq-diagnostics
Logs from node 1 (with sensitive values edited out)
See https://www.rabbitmq.com/docs/logging to learn how to collect logs
Logs from node 2 (if applicable, with sensitive values edited out)
See https://www.rabbitmq.com/docs/logging to learn how to collect logs
Logs from node 3 (if applicable, with sensitive values edited out)
See https://www.rabbitmq.com/docs/logging to learn how to collect logs
rabbitmq.conf
See https://www.rabbitmq.com/docs/configure#config-location to learn how to find rabbitmq.conf file location
Steps to deploy RabbitMQ cluster
I Use Kubernetes Operator to deploy rabbitmq-cluster. (cluster-operator:2.11.0)
We first built our cluster on rabbitmq:3.10.2 and have been going through 3.11 and 3.12 to upgrade to 3.13.7.
Steps to reproduce the behavior in question
we load this json on startup
(permission and users are removed)
advanced.config
See https://www.rabbitmq.com/docs/configure#config-location to learn how to find advanced.config file location
Application code
# PASTE CODE HERE, BETWEEN BACKTICKS
Kubernetes deployment file
What problem are you trying to solve?
After searching, the expected behavior of my settings is that when a message is received, it is moved to disk after a period of time, so there seems to be no reason why it should be kept in RAM. However, ra_log_ets keeps growing in use and does not get smaller. rabbitmq does nothing until it reaches a high watermark and stops forwarding messages.
What settings might affect this issue?
Beta Was this translation helpful? Give feedback.
All reactions