{disk_free_limit, {mem_relative, 1.0}}

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

{disk_free_limit, {mem_relative, 1.0}}

carlhoerberg
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}]
Reply | Threaded
Open this post in threaded view
|

Re: {disk_free_limit, {mem_relative, 1.0}}

Arun Rao
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 <[hidden email]> 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
[hidden email]
https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss


_______________________________________________
rabbitmq-discuss mailing list
[hidden email]
https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Reply | Threaded
Open this post in threaded view
|

Re: {disk_free_limit, {mem_relative, 1.0}}

carlhoerberg
yes, we do. setting an absolut number works.
yes i know.

rabbitmq 3.3.2, erlang 17


On Friday 13 June 2014 at 09:00, Arun Rao [via RabbitMQ] wrote:

> 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 <[hidden email] (/user/SendEmail.jtp?type=node&node=36189&i=0)> 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 (http://Nabble.com).
> > _______________________________________________
> > rabbitmq-discuss mailing list
> > [hidden email] (/user/SendEmail.jtp?type=node&node=36189&i=1)
> > https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> [hidden email] (/user/SendEmail.jtp?type=node&node=36189&i=2)
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
> If you reply to this email, your message will be added to the discussion below: http://rabbitmq.1065348.n5.nabble.com/disk-free-limit-mem-relative-1-0-tp36187p36189.html 
> To unsubscribe from {disk_free_limit, {mem_relative, 1.0}}, click here (
> NAML (
http://rabbitmq.1065348.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml)



Reply | Threaded
Open this post in threaded view
|

Re: {disk_free_limit, {mem_relative, 1.0}}

Simon MacMullen-2
In reply to this post by carlhoerberg
On 13/06/2014 12:37AM, carlhoerberg 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:

Well, that's embarrassing. mem_relative has been broken since 3.2.0.
It'll get fixed in 3.3.3 and I will kick our test suite.

Cheers, Simon

--
Simon MacMullen
RabbitMQ, Pivotal
_______________________________________________
rabbitmq-discuss mailing list
[hidden email]
https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss