1

erlang version = 1:24.0.2-1

rabbitmq-server version = 3.8.16-1

Recently installed latest rabbitmq on Ubuntu20. I verified that all was working fine and consumer was consuming the notification from messaging queue as required.

After approximately a day, rabbbitmq crashed as there was 0 disk space left.

After analysis found that around 10G was consumed by msg_store_transient, to which restarting rabbitmq solved the issue. But after a day, it happens again.

Can someone help me further?

Rajat Jain
  • 201
  • 3
  • 12

2 Answers2

1

most likely you are consuming messages without sending back the basic_ack, see for example here the ch.basic_ack

What to do:

  • check the unacked messages see: enter image description here
  • check if you are using too many not persistent messages
  • check if you are using too many not persistent queues
Gabriele Santomaggio
  • 21,656
  • 4
  • 52
  • 52
0

Issue is Fixed:

  1. We had high number of Ready messages because of which rdq files was taking huge space
  2. There was a bug in code, that was listening to only one queue not all.
Rajat Jain
  • 201
  • 3
  • 12
  • I have the same issue. Can you please share some code around how you solved this bug? – Stuti Verma Jul 29 '21 at 07:36
  • whats are your values for Ready, Unacked and total messages for a queue? My code bug was unrelated to rabbitmq but was more of configuration issue – Rajat Jain Jul 30 '21 at 11:45
  • I resolved the issue. I had a node api that was starting consumer and producer together at every request. Starting consumer at each request lead to several connections. So, after I started the consumer only once after the rmq node starts, and outside the node api, the memory issue resolved. – Stuti Verma Jul 31 '21 at 16:25
  • Great .. Congrats – Rajat Jain Aug 01 '21 at 17:18