CacheSize is currently configured for 8GB. Server dies when the limit is exceeded and indicates that the CacheSize should be increased. Server fails to start when CacheSize is configured for greater than 8GB.

Our zabbix server process starts and runs fine for 10-15 days, after which I'm speculating perhaps the memory allocated for the cache becomes more and more fragmented, causing an increased cache utilization. I see there have been historical issues to increase the size when the limit was lower. Is there a way the upper limit on the cache size can be removed altogether, leaving it to the sysadmin to determine the appropriate max size?

1868:20190314:034026.792 __mem_malloc: skipped 48828 asked 12903760 skip_min 256 skip_max 12857992
1868:20190314:034026.792 file:dbconfig.c,line:94 zbx_mem_realloc(): out of memory (requested 12903760 bytes)
1868:20190314:034026.792 file:dbconfig.c,line:94 zbx_mem_realloc(): please increase CacheSize configuration parameter
1868:20190314:034026.792 === memory statistics for configuration cache ===
1868:20190314:034026.792 free chunks of size 32 bytes: 8
1868:20190314:034026.792 free chunks of size 48 bytes: 8
1868:20190314:034026.792 free chunks of size 80 bytes: 1
1868:20190314:034026.793 free chunks of size 96 bytes: 1592
1868:20190314:034026.793 free chunks of size 104 bytes: 3
1868:20190314:034026.793 free chunks of size 112 bytes: 1
1868:20190314:034026.805 free chunks of size >= 256 bytes: 48828
1868:20190314:034026.805 min chunk size: 32 bytes
1868:20190314:034026.805 max chunk size: 12857992 bytes
1868:20190314:034026.805 memory of total size 8589934216 bytes fragmented into 22273991 chunks

mysql> select type, count from items group by type order by type;
--------------+

type

count

--------------+

--------------+
12 rows in set (13.30 sec)