Browse Source

Render vm_memory_high_watermark for RabbitMQ

RabbitMQ/Erlang do not properly determine available RAM when running in
containerised environment, plus default value for watermark is 0.4, which is
low for nodes running RabbitMQ only.

Some additional information:
https://www.rabbitmq.com/memory.html

Change-Id: I1738c66be0e698568881b2c64d5d456db851af4d
Depends-On: Iadd0529d166ef1dad1697215bbc181104a7b926e
Depends-On: Ibc6e8b91055f411b058505d14c2d83fbc826cdd4
Aleksandr Mogylchenko 2 years ago
parent
commit
0d02edf632
2 changed files with 2 additions and 0 deletions
  1. 1
    0
      service/files/defaults.yaml
  2. 1
    0
      service/files/rabbitmq.config.j2

+ 1
- 0
service/files/defaults.yaml View File

@@ -18,6 +18,7 @@ configs:
18 18
     # How many seconds we give a node before making liveness checks
19 19
     # completely strict
20 20
     node_startup_timeout: 180
21
+    high_watermark_ratio: 0.75
21 22
 
22 23
 url:
23 24
   rabbitmq:

+ 1
- 0
service/files/rabbitmq.config.j2 View File

@@ -23,6 +23,7 @@
23 23
                     {verify,verify_peer},
24 24
                     {fail_if_no_peer_cert,false}]}
25 25
      {% endif %}
26
+     ,{vm_memory_high_watermark, {absolute, {{ (memory_limit|int * rabbitmq.high_watermark_ratio)|int }}}}
26 27
    ]}
27 28
   ,{autocluster, [
28 29
       {dummy_param_without_comma, true}

Loading…
Cancel
Save