Aerospike memory overflow

1

asadm output:

info
Number of rows: 16

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Namespace Usage Information~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Namespace                                Node      Total    Expirations,Evictions     Stop       Disk    Disk     HWM   Avail%          Mem     Mem    HWM      Stop
        .                                   .    Records                        .   Writes       Used   Used%   Disk%        .         Used   Used%   Mem%   Writes%
ns1         192.168.125.141:3000                 1.974 M   (183.268 K, 0.000)       false         N/E   N/E     50      N/E       35.417 GB   66      70     90
ns1         192.168.125.142:3000                 2.059 M   (190.529 K, 1.018 K)     false         N/E   N/E     50      N/E       36.964 GB   69      70     90
ns1         192.168.125.143:3000                 2.042 M   (188.789 K, 0.000)       false         N/E   N/E     50      N/E       36.604 GB   68      70     90
ns1         192.168.125.144:3000                 2.049 M   (189.515 K, 0.000)       false         N/E   N/E     50      N/E       36.777 GB   69      70     90
ns1         192.168.125.145:3000                 2.051 M   (189.451 K, 0.000)       false         N/E   N/E     50      N/E       36.766 GB   69      70     90
ns1         192.168.126.109:3000                 2.048 M   (189.649 K, 0.000)       false         N/E   N/E     50      N/E       36.826 GB   69      70     90
ns1         192.168.126.110:3000                 1.949 M   (180.437 K, 0.000)       false         N/E   N/E     50      N/E       34.992 GB   65      70     90
ns1         192.168.126.111:3000                 1.949 M   (179.979 K, 0.000)       false         N/E   N/E     50      N/E       34.904 GB   65      70     90
ns1         192.168.127.96:3000                  1.936 M   (179.062 K, 0.000)       false         N/E   N/E     50      N/E       34.750 GB   65      70     90
ns1         192.168.127.97:3000                  1.834 M   (169.105 K, 0.000)       false         N/E   N/E     50      N/E       32.912 GB   61      70     90
ns1         192.168.127.98:3000                  1.725 M   (159.533 K, 0.000)       false         N/E   N/E     50      N/E       30.942 GB   58      70     90
ns1         192.168.127.99:3000                  1.986 M   (184.374 K, 0.000)       false         N/E   N/E     50      N/E       35.594 GB   66      70     90
ns1         192.168.55.131:3000                  2.090 M   (194.905 K, 20.978 K)    false         N/E   N/E     50      N/E       37.751 GB   70      70     90
ns1         192.168.55.86:3000                   1.781 M   (164.857 K, 0.000)       false         N/E   N/E     50      N/E       31.931 GB   60      70     90
ns1         192.168.69.100:3000                  1.912 M   (176.059 K, 0.000)       false         N/E   N/E     50      N/E       34.277 GB   64      70     90
ns1         aerospike-api-p-126108.hz.td:3000    2.034 M   (187.529 K, 0.000)       false         N/E   N/E     50      N/E       36.523 GB   68      70     90
ns1                                             31.419 M   (2.907 M, 21.996 K)               0.000 B                             563.930 GB

top memory used:

KiB Mem : 65809524 total,  2477196 free, 62614424 used,   717904 buff/cache
KiB Swap:        0 total,        0 free,        0 used.  2624452 avail Mem

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
32296 admin     20   0 66.423g 0.058t   1600 S   7.9 94.1   1934:00 asd

aerospike.conf

namespace ns1 {
    replication-factor 1
    memory-size 54G
    default-ttl 90d
    high-water-memory-pct 80
    storage-engine memory
}

I set memory-size with 54G, but the truth memory used 60G+ .

2

The memory-size configuration item is a soft limit for the memory Aerospike uses for data and indexes (which is occupying ~66% of your limit on each node).

3

i set hwm to 65，it cost physical memory 95% usage . the 35% memory space used to replication and migration？does it occur oom ?

4

I’m not sure what you are asking :confused:. The kernel makes the decision to OOM a process, so breaching the soft ‘memory-size’ limit alone will not cause OOM.