-
Incident report
-
Resolution: Duplicate
-
Trivial
-
None
-
6.0.0rc2
-
None
-
Debian Bullseye
Steps to reproduce:
- Send more trapper items than preprocessor can handle
- Watch the preprocessor queue grow, and the master processes CPU grow with it (expontential?)
Result:
zabbix 357 77.9 3.4 519676 137988 ? RN 04:25 0:42 /usr/sbin/zabbix_server: preprocessing manager #1 [queued 86761, processed 26 values, idle 0.000000 sec during 5.249426 sec] zabbix 358 0.0 0.1 407544 4788 ? SN 04:25 0:00 /usr/sbin/zabbix_server: preprocessing worker #1 started zabbix 359 0.0 0.1 407544 4788 ? SN 04:25 0:00 /usr/sbin/zabbix_server: preprocessing worker #2 started zabbix 360 0.0 0.1 407544 4788 ? SN 04:25 0:00 /usr/sbin/zabbix_server: preprocessing worker #3 started zabbix 361 0.0 0.1 407544 4788 ? SN 04:25 0:00 /usr/sbin/zabbix_server: preprocessing worker #4 started zabbix 362 0.0 0.1 407544 4788 ? SN 04:25 0:00 /usr/sbin/zabbix_server: preprocessing worker #5 started
- the queue grows, proces
- Processed items (per iteration) shrinks and CPU consumed by the manager increases.
Expected:
- Queue length should be limited
- Preferably the queue should scale better
- is duplicated by
-
ZBX-20567 Preprocessing queue grows indefinitely on Zabbix Proxy
- Closed