Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-16347

Postgresql out of memory using timescaledb

XMLWordPrintable

    • Icon: Problem report Problem report
    • Resolution: Fixed
    • Icon: Major Major
    • 4.4.9rc1, 5.0.1rc1, 5.2.0alpha1, 5.2 (plan)
    • 4.2.4
    • Server (S)
    • Db: CentOS Linux 7, Postgresql 11.4, timescaledb-11-1.2.2
      Server: CentOS Linux 7, zabbix 4.2.4 (from RPM)
    • Team C
    • Sprint 63 (Apr 2020), Sprint 64 (May 2020)
    • 1

      Steps to reproduce:

      1. Install PgSQL 11 + timescaledb
      2. Configure with 9 proxies, with vps ~ 2200
      3. Restart zabbix-server process

      Result:
      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...
      Expected:
      History syncer does not generate queries that exhaust database memory.

       

      Note: this appears to be the same issue reported in ZBX-9722 .

        1. zabbix_server.log
          84 kB
        2. zabbix_server.conf
          17 kB
        3. pgsql.log
          121 kB
        4. image-2020-04-01-11-28-53-520.png
          image-2020-04-01-11-28-53-520.png
          6 kB

            arimdjonoks Artjoms Rimdjonoks
            wsuzabbixapw Aaron Whiteman
            Team C
            Votes:
            34 Vote for this issue
            Watchers:
            50 Start watching this issue

              Created:
              Updated:
              Resolved: