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

Trigger housekeeper causes heavy DB load when many triggers are deleted

XMLWordPrintable

    • Icon: Incident report Incident report
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 7.0.17
    • Server (S)
    • Zabbix server 7.0.8
      PostgreSQL 16.6 (RDS)
      Problem table size ~40–50M rows

      Zabbix 6.4+ when a large number of triggers are deleted, the trigger housekeeper tries to clean up related problems/events.
      Deleting triggers causes serious performance issues if the Problem table is large.

      It runs heavy NOT EXISTS queries and fetches all IDs at once, and trigger housekeeper without respecting MaxHousekeeperDelete.
      As a result, DB load becomes extremely high (queries taking tens to hundreds of seconds), and the Zabbix UI/server becomes unresponsive.

        2065:20250806:234807.984 slow query: 23.825564 sec, "select eventid from problem where source=0 and object=0 and not exists (select NULL from triggers where triggerid=objectid)"
  2065:20250806:234930.689 slow query: 22.668523 sec, "select eventid from problem where source=0 and object=0 and not exists (select NULL from triggers where triggerid=objectid)"
  2065:20250806:235052.384 slow query: 21.635644 sec, "select eventid from problem where source=0 and object=0 and not exists (select NULL from triggers where triggerid=objectid)"
  2065:20250806:235206.307 slow query: 13.862464 sec, "select eventid from problem where source=0 and object=0 and not exists (select NULL from triggers where triggerid=objectid)"

        1. Screenshot 2025-09-04 at 10.51.47.png
          73 kB
          Vladislavs Sokurenko

            zabbix.dev Zabbix Development Team
            JKKim Kim Jongkwon
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: