Server: performance improvements (ZBXNEXT-318)

[ZBXNEXT-338] Slow update of IDS tables by db syncers Created: 2010 Apr 29  Updated: 2017 May 31  Resolved: 2010 May 13

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: None
Affects Version/s: None
Fix Version/s: 1.8.3

Type: Change Request (Sub-task) Priority: Major
Reporter: Alexei Vladishev Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Comments   
Comment by Alexander Vladishev [ 2010 Apr 29 ]

14538:20100429:163933.426 Slow query: 262.591837 sec, "update ids set nextid=nextid+1 where nodeid=0 and table_name='events' and field_name='
eventid'"
14531:20100429:163942.081 Slow query: 106.971386 sec, "update ids set nextid=nextid+1 where nodeid=0 and table_name='events' and field_name='
eventid'"
14529:20100429:163954.606 Slow query: 180.310498 sec, "update ids set nextid=nextid+1 where nodeid=0 and table_name='events' and field_name='
eventid'"
14540:20100429:164010.791 Slow query: 126.616977 sec, "update ids set nextid=nextid+1 where nodeid=0 and table_name='events' and field_name='
eventid'"
14539:20100429:164026.615 Slow query: 133.093000 sec, "update ids set nextid=nextid+1 where nodeid=0 and table_name='events' and field_name='
eventid'"
14537:20100429:164044.422 Slow query: 102.160601 sec, "update ids set nextid=nextid+1 where nodeid=0 and table_name='events' and field_name='
eventid'"
14532:20100429:164109.743 Slow query: 180.720213 sec, "update ids set nextid=nextid+1 where nodeid=0 and table_name='events' and field_name='
eventid'"
14487:20100429:164147.708 Slow query: 151.830678 sec, "update ids set nextid=nextid+1 where nodeid=0 and table_name='events' and field_name='
eventid'"
14487:20100429:164147.712 Sending list of active checks to [::ffff:192.168.3.2] failed: host [localhost] not found
14534:20100429:164147.713 Slow query: 177.742693 sec, "update ids set nextid=nextid+1 where nodeid=0 and table_name='events' and field_name='
eventid'"
14536:20100429:164234.889 Slow query: 316.659795 sec, "update ids set nextid=nextid+1 where nodeid=0 and table_name='events' and field_name='
eventid'"
14483:20100429:164335.317 Slow query: 135.042823 sec, "update ids set nextid=nextid+1 where nodeid=0 and table_name='events' and field_name='
eventid'"

Comment by Alexander Vladishev [ 2010 May 13 ]

Available in version pre1.8.3, r11965.

Comment by chloe [ 2011 Sep 29 ]

Hi,

As GDE mentioned on Zabbix forum, this bug is still here in version 1.8.6.

During a stress test we obtained lot of slow query and for large amount of services : server crash

27106:20110926:120928.425 Slow query: 120.509592 sec, "update ids set nextid=nextid+256 where nodeid=0 and table_name='events' and field_name='eventid'"
27101:20110926:120928.498 Slow query: 66.452517 sec, "update ids set nextid=nextid+256 where nodeid=0 and table_name='events' and field_name='eventid'"
27107:20110926:120931.416 Slow query: 62.458832 sec, "update ids set nextid=nextid+256 where nodeid=0 and table_name='events' and field_name='eventid'"
27123:20110926:120934.875 Slow query: 108.504381 sec, "update ids set nextid=nextid+256 where nodeid=0 and table_name='events' and field_name='eventid'"

GDE quote :

our database is a postgresql 9.0.4 hosted on a seperate machine from zabbix server.

strangely, this doesn't happen when we test the first 100 hosts.

These results have an impact on zabbix. From the frontend, we see a queue for items that are supposed to be checked by zabbix_agent (or internal) that gets ever increasing until the script stop.
We've also noticed that once the queries are done (which happens a couple minutes after the end of the test, obviously) all graphs get updated.

Thank's in advance

Generated at Fri Apr 19 15:10:58 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.