Type: Problem report
Affects Version/s: 4.2.4
Component/s: Server (S)
Environment:Db: CentOS Linux 7, Postgresql 11.4, timescaledb-11-1.2.2
Server: CentOS Linux 7, zabbix 4.2.4 (from RPM)
Sprint:Sprint 63 (Apr 2020), Sprint 64 (May 2020)
Steps to reproduce:
- Install PgSQL 11 + timescaledb
- Configure with 9 proxies, with vps ~ 2200
- Restart zabbix-server process
On restart, the zabbix server sends a large UPDATE query that eventually exhausts available memory on the pgsql Server. Server is configured with 64Gb RAM, 40Gb Swap, with large work_mem to satisfy requirements of zabbix select queries.
When this occurs, the history syncer processes do not update history and the database/server falls behind, generating multiple triggers and alerts.
See log file...
See memory dump...
History syncer does not generate queries that exhaust database memory.
Note: this appears to be the same issue reported in