disk_free_limit issue

[RajanAOz]

I am facing an issue with the disk_free_limit parameter. It seems that this feature is not working like it should, or I do not understand what this parameter supposed to do.

I am able to publish messages to a (durable) queue even when the free_disk_limit threshold is exceeded! The messages I am sending through the rabbitmq management console and the delivery mode is persistent. Please advice.

**/etc/rabbitmq/rabbitmq.config**
[
  {kernel, [

  ]},
  {rabbit, [
    {disk_free_limit, "32GB"},
    {tcp_listen_options, [binary, {packet,raw},
                                  {reuseaddr,true},
                                  {backlog,128},
                                  {nodelay,true},
                                  {exit_on_close,false},
                                  {keepalive,false}]},
    {loopback_users, [<<"monitoring">>]},
    {default_user, <<"guest">>},
    {default_pass, <<"guest">>},
    {heartbeat, 580}
  ]}
].

Actual free size on disk

Filesystem           1K-blocks    Used Available Use% Mounted on
/dev/mapper/VolGroup-lv_root
                      39645804 6434336  **31190912**  18% /

rabbitmq logfile

=INFO REPORT==== 8-Jul-2016::08:32:17 ===
Memory limit set to 196MB of 490MB total.

=INFO REPORT==== 8-Jul-2016::08:32:17 ===
Disk free limit set to 32000MB

=INFO REPORT==== 8-Jul-2016::08:32:17 ===
Disk free space insufficient. Free bytes:31939354624 Limit:32000000000

=WARNING REPORT==== 8-Jul-2016::08:32:17 ===
disk resource limit alarm set on node 'rabbit@shared-rmq-001'.

**********************************************************
*** Publishers will be blocked until this alarm clears ***
**********************************************************

[michaelklishin]

Please post questions to rabbitmq-users or Stack Overflow. RabbitMQ uses GitHub issues for specific actionable items engineers can work on, not questions. Thank you.

[michaelklishin]

Connections are blocked after they publish a message (a basic.publish, content headers, or content body frame is processed) because we don't want to block consumers.