Disk alarm

broken image
broken image

11:04:54.002 Disabling disk free space monitoring 12:02:11.564 Disk free limit set to 950MBįree disk space monitoring will be deactivated on unrecognised platforms, causing an entry such as the one below: 12:02:11.564 Enabling free disk space monitoring The free space of the drive or partition that the broker database uses will be monitored at least every 10 seconds to determine whether the disk alarm should be raised or cleared. A more conservative approach would be to set the limit to the same as the amount of memory installed on the system (see the configuration below).Īn alarm will be triggered if the amount of free disk space drops below a configured limit.

broken image

If the disk alarm is set too low and messages are paged out rapidly, it is possible to run out of disk space and crash RabbitMQ in between disk space checks (at least 10 seconds apart). Transient messages, which aren't normally persisted, are still paged out to disk when under memory pressure, and will use up the already limited disk space. To reduce the risk of filling up the disk, all incoming messages are blocked. The goal is to avoid filling up the entire disk which will lead all write operations on the node to fail and can lead to RabbitMQ termination. When free disk space drops below a configured limit (50 MB by default), an alarm will be triggered and all producers will be blocked.

broken image