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

Proxy poller processes will summon OOM killer if all proxies are not available for some reason

XMLWordPrintable

    • Icon: Problem report Problem report
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • 5.0.13, 5.4.2, 6.0.0alpha1
    • Server (S)
    • None
    • RHEL 8.4
      Zabbix LTS 5.0.13

      Steps to reproduce:

      1. Use 50+ passive proxies with required amount of proxy pollers with configuration sync interval every 1 minute;
      2. Get some unplanned network outage, all proxies are not reachable;
      3. OOM killer;

      Result:
      PSS consumption:

      Proxy poller are jumping from 8mb to 150mb+:

      Private + Shared:
        8.3 MiB + 129.5 KiB =   8.4 MiB	/usr/sbin/zabbix_server: proxy poller #7 [exchanged data with 0 proxies in 0.000017 sec, idle 1 sec]
      
      150.1 MiB + 139.5 KiB = 150.2 MiB	/usr/sbin/zabbix_server: proxy poller #6 [exchanged data with 0 proxies in 0.000014 sec, idle 1 sec]
      

      From performance perspective:

      1. not needed work for database to retrieve full configuration each time for each proxy;
      2. unpredictable memory consumption;

      Expected:
      Server continue to work, monitoring system should not kill itself with OOM just because some proxies are died or not reachable.

            zabbix.dev Zabbix Development Team
            edgar.akhmetshin Edgar Akhmetshin
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: