it seems that memory watermark did not work

24 views
Skip to first unread message

4118...@qq.com

unread,
Aug 25, 2023, 8:23:23 PM8/25/23
to rabbitmq-users

server version: 3.6.6
watermark configuration:Memory limit set to 6354MB of 15886MB total(40%).
describe:
The mq process was killed by the Linux OOM, and the system log records that during the kill, the memory usage of mq is as follows:
total-vm:17600196KB,anon-rss:15291812KB

My question is, since I have set the water level of the memory(40%), why does it appear that this control has failed(Before OOM, there were no errors in the logs regarding restrictions on publishers)

Under what circumstances will memory threshold fail?

this is system log:

img_v2_ad72658f-e173-4c87-9570-2688ef51fcbg

  • Before OOM, there were no particularly obvious anomalies observed in Grafana:

image

- the vhost messages in Grafana:

image

mq logs.jpeg

jo...@cloudamqp.com

unread,
Aug 28, 2023, 11:29:47 AM8/28/23
to rabbitmq-users
Hi,
Version 3.6.6 of RabbitMQ brings back memories! 
You need to upgrade to RabbitMQ 3.12.

/Johan
Reply all
Reply to author
Forward
0 new messages