[rabbitmq-discuss] {disk_free_limit, {mem_relative, 1.0}}

Fri Jun 13 01:57:40 BST 2014

The location of the parameter also matters, is your rabbitmq.config file
similar to this?

[
{rabbit, [
...
{disk_free_limit, {mem_relative,1.0}}
...
]}
].

Also setting this relative to memory sets really "low watermark". For
example, If you have 16G RAM and 100G Hard disk. Setting this relative to
RAM makes low watermark set at 16GB. This means that Publishers are blocked
when your available disk space approaches 84GB (100-16). So I set this
value to 0.1 and now publishers are not blocking in case of backup until
98.4 (100-1.6). HTH

On Thu, Jun 12, 2014 at 4:37 PM, carlhoerberg <carl.hoerberg at gmail.com>
wrote:

> It doesn't seems like we're able to configure disk_free_limit with
> {mem_relative, 1.0} (as described here:
> http://www.rabbitmq.com/configure.html). The mgmt interface reports "(not
> available)" and the sasl log reports:
>
>
> =CRASH REPORT==== 9-Jun-2014::15:17:09 ===
>   crasher:
>     initial call: rabbit_disk_monitor:init/1
>     pid: <0.251.0>
>     registered_name: []
>     exception exit: {badarith,
>                         [{rabbit_disk_monitor,interval,1,[]},
>                          {rabbit_disk_monitor,start_timer,1,[]},
>                          {rabbit_disk_monitor,init,1,[]},
>                          {gen_server,init_it,6,
>                              [{file,"gen_server.erl"},{line,306}]},
>                          {proc_lib,init_p_do_apply,3,
>                              [{file,"proc_lib.erl"},{line,239}]}]}
>       in function  gen_server:init_it/6 (gen_server.erl, line 330)
>     ancestors: [rabbit_disk_monitor_sup,rabbit_sup,<0.96.0>]
>     messages: []
>     links: [<0.250.0>]
>     dictionary: []
>     trap_exit: false
>     status: running
>     heap_size: 6772
>     stack_size: 27
>     reductions: 40670
>   neighbours:
>
> =SUPERVISOR REPORT==== 9-Jun-2014::15:17:09 ===
>      Supervisor: {local,rabbit_disk_monitor_sup}
>      Context:    start_error
>      Reason:     {badarith,
>                      [{rabbit_disk_monitor,interval,1,[]},
>                       {rabbit_disk_monitor,start_timer,1,[]},
>                       {rabbit_disk_monitor,init,1,[]},
>                       {gen_server,init_it,6,
>                           [{file,"gen_server.erl"},{line,306}]},
>                       {proc_lib,init_p_do_apply,3,
>                           [{file,"proc_lib.erl"},{line,239}]}]}
>      Offender:   [{pid,undefined},
>                   {name,rabbit_disk_monitor},
>                   {mfargs,
>
> {rabbit_disk_monitor,start_link,[{mem_relative,1.0}]}},
>                   {restart_type,{transient,1}},
>                   {shutdown,4294967295},
>                   {child_type,worker}]
>
>
>
>
> --
> View this message in context:
> http://rabbitmq.1065348.n5.nabble.com/disk-free-limit-mem-relative-1-0-tp36187.html
> Sent from the RabbitMQ mailing list archive at Nabble.com.
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140612/f4987372/attachment.html>