You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rabbitmqctl set_vm_memory_high_watermark 1.0
Setting memory threshold on 'rabbit@rmq0-rmq-swapping' to 1.0
rabbitmqctl eval'vm_memory_monitor:get_vm_memory_high_watermark().'
1.0
# I expect the memory limit to be set to 1038778368, but instead:
rabbitmqctl eval'vm_memory_monitor:get_memory_limit().'
415511347
erl -noshell -eval 'io:format("~p~n", [1038778368 * 0.4]).' -eval 'init:stop()'
415511347.20000005
When setting an absolute memory that is higher than the available memory:
set_vm_memory_high_watermark absolute 2000MB
Setting memory threshold on 'rabbit@rmq0-rmq-swapping' to 2000000000 bytes
rabbitmqctl eval'vm_memory_monitor:get_vm_memory_high_watermark().'
{absolute,2000000000}
rabbitmqctl eval'vm_memory_monitor:get_memory_limit().'
1038778368
The text was updated successfully, but these errors were encountered:
gerhard
changed the title
Setting the vm_memory_high_watermark to >0.(9) defaults to 0.4
Setting the vm_memory_high_watermark to >0.(9) should default to total available memory
Jul 7, 2017
gerhard
changed the title
Setting the vm_memory_high_watermark to >0.(9) should default to total available memory
Setting the vm_memory_high_watermark to >0.(9) defaults to total available memory
Jul 7, 2017
gerhard
added a commit
to rabbitmq/rabbitmq-common
that referenced
this issue
Jul 10, 2017
Prior to this change, setting the vm_memory_high_watermark to a value
higher than 1 (inclusive), would default to 0.4. This is different from
the behaviour when setting an absolute value, namely defaulting to the
total memory available.
Extracted common memory-related macros & records so that they can be
shared by tests.
re rabbitmq/rabbitmq-server#1285
[finishes #148470947]
gerhard
changed the title
Setting the vm_memory_high_watermark to >0.(9) defaults to total available memory
Setting the vm_memory_high_watermark to > 1 defaults to total available memory
Jul 10, 2017
This is meant to add a missing integration test that wraps up #1285
It's not a unit test and it can't run in paralle, but
set_disk_free_limit does the same wrong thing. We should either remove
them both or leave them as they are.
[#148470947]
Expected:
Unexpected:
When setting an absolute memory that is higher than the available memory:
The text was updated successfully, but these errors were encountered: