CPU E5-2690 v2 x 2
CPU E5-2690 v4 x 2
Huawei all flass storage system
Average utilisation of the hardware : < 30% with stuck on 100% history syncer.
50 history syncers
Steps to reproduce:
- install and use monitoring system
- try to scale up using proxies
- use built-in functionality like aggregated items
- history syncers become at 100% load
Up to 1/3 of the Mutex locks will fail of the valuecache and configuration cache. For example for 5 minutes:
Strace output will be full of the:
11414 17:14:50.190574 futex(0x7fcde87bf140, FUTEX_WAIT, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable) <0.000007>
Mostly high count of trapper/history syncer processes are useless on high loaded instance due to the locking problems. Dedicated hardware is not loaded at all - so vertical scale is not happening.
The amount of processes allowed to be launched should correlate with the ability to handle workload on high performance hardware.
ZBXNEXT-8058 History syncer is frequently blocked by waiting on configuration cache to be free
ZBX-21537 Internal zabbix ineffective locking to calculate stats
- mentioned in