[ZBX-16168] Zabbix Performance (history syncer 100%) Created: 2019 May 23  Updated: 2019 May 23  Resolved: 2019 May 23

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P), Server (S)
Affects Version/s: None
Fix Version/s: None

Type: Problem report Priority: Critical
Reporter: webbix Assignee: Unassigned
Resolution: Commercial support required Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: JPEG File database_12h.jpg     Text File kl-apac-mon-zproxy-01.txt     Text File lx-all-mon-zdb-03.txt     Text File lx-all-mon-zproxy-01.txt     Text File lx-all-mon-zserver-01.txt     Text File lx-bra-mon-zproxy-01.txt     Text File lx-db-mon-app-02.txt     Text File lx-emea-mon-zproxy-01.txt     Text File lx-hq-mon-zproxy-01.txt     Text File lx-lat-mon-zpx-01.txt     Text File singapore-vpstimwe.txt     JPEG File zabbix_cache_1d.jpg     JPEG File zabbix_cache_3d.jpg     JPEG File zabbix_history_syncer_1d.jpg     JPEG File zabbix_history_syncer_3d.jpg     JPEG File zabbix_internal_process_1d.jpg     JPEG File zabbix_internal_process_3d.jpg     JPEG File zabbix_server_performance_1d.jpg     JPEG File zabbix_server_performance_3d.jpg     Text File zabbix_tables.txt    

 Description   

Since November 2018 we have performance problems with Zabbix 3.4.10.
Since this time, we made tuning for tcp connections, tuning in the OS (CentOS 6.9), tuning in the MariaDB conf, tuning in the Zabbix Server conf and tuning in the Zabbix Proxies conf.

The following problem remains:

2 times a day (5:22 p.m. and 8:22 p.m., we have different hours in the past) History Syncer reaches 100% and proxies become "NoDataProcessing".
While history syncer is at 100% several "NoData" alarms start to appear.
To recover, we stop the 2 major proxies, restart the server and raise the 2 proxies with a time interval.

Number of hosts 6679
Number of items 732813
Number of triggers 358638
Required server performance, new values per second 2695.54

Hardwares (VM):

  • Server:
    CPU: 4 CPU
    Memory: 24GB
  • Database (Ver 15.1 Distrib 10.3.4-MariaDB, for Linux (x86_64) using readline 5.1):
    CPU: 8 CPUs
    Memory: 64GB
    Disk: SSD

Infrastructure:

1 Zabbix Server version 3.4.10 (lx-all-mon-zserver-01)
1 Database Ver 15.1 Distrib 10.3.4-MariaDB (lx-all-mon-zdb-03)
6 proxies for machines
1 proxy for Databases monitoring
1 proxy for webchecks

 

Attachments:

Server, proxies and database configurations.
Server and database graphics

 Comments   
Comment by Alexey Pustovalov [ 2019 May 23 ]

Please be advised that this section of the tracker is for bug reports only. The case you have submitted can not be qualified as one, so please reach out to [email protected] for commercial support or consultancy services. Alternatively, you can also use our IRC channel or community forum (https://www.zabbix.com/forum) for assistance. With that said, we are closing this ticket. Thank you for understanding.

Generated at Sat May 11 06:13:11 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.