Env:
Zabbix 1.8.9(Upgraded from 1.8.7)
RedHat 6.1
MySQL 5.1
I am using the Zabbix API fairly heavily(update/create or delete 50-100 items at a time). The issue I am running into is when there are a bunch of new items are created via some discovery scripts I have written, the web interface stops responding. A look into MySQL processlist shows the following:
| 327126 | zabbix | localhost | zabbix | Query | 0 | Updating | UPDATE ids SET nextid=nextid+1 WHERE nodeid=0 AND table_name='auditlog' AND field_name='auditid' |
| 327476 | zabbix | localhost | zabbix | Query | 0 | Updating | UPDATE ids SET nextid=nextid+1 WHERE nodeid=0 AND table_name='auditlog' AND field_name='auditid' |
| 328163 | zabbix | localhost | zabbix | Query | 0 | Updating | UPDATE ids SET nextid=nextid+1 WHERE nodeid=0 AND table_name='auditlog' AND field_name='auditid' |
| 328694 | zabbix | localhost | zabbix | Query | 0 | Updating | UPDATE ids SET nextid=nextid+1 WHERE nodeid=0 AND table_name='auditlog' AND field_name='auditid' |
| 328695 | zabbix | localhost | zabbix | Query | 0 | Updating | UPDATE ids SET nextid=nextid+1 WHERE nodeid=0 AND table_name='auditlog' AND field_name='auditid' |
| 328779 | zabbix | localhost | zabbix | Query | 0 | Updating | UPDATE ids SET nextid=nextid+1 WHERE nodeid=0 AND table_name='auditlog' AND field_name='auditid' |
| 328790 | zabbix | localhost | zabbix | Query | 0 | Updating | UPDATE ids SET nextid=nextid+1 WHERE nodeid=0 AND table_name='auditlog' AND field_name='auditid' |
| 328793 | zabbix | localhost | zabbix | Query | 0 | Updating | UPDATE ids SET nextid=nextid+1 WHERE nodeid=0 AND table_name='auditlog' AND field_name='auditid' |
| 328794 | zabbix | localhost | zabbix | Query | 0 | Updating | UPDATE ids SET nextid=nextid+1 WHERE nodeid=0 AND table_name='auditlog' AND field_name='auditid' |
| 328810 | zabbix | localhost | zabbix | Query | 0 | Updating | UPDATE ids SET nextid=nextid+1 WHERE nodeid=0 AND table_name='auditlog' AND field_name='auditid' |
| 328845 | zabbix | localhost | zabbix | Query | 0 | Updating | UPDATE ids SET nextid=nextid+1 WHERE nodeid=0 AND table_name='auditlog' AND field_name='auditid' |
| 328861 | zabbix | localhost | zabbix | Query | 0 | Updating | UPDATE ids SET nextid=nextid+1 WHERE nodeid=0 AND table_name='auditlog' AND field_name='auditid' |
These queries never die off, and while this is happening the web interface and the API cannot service requests. Anybody else running into this? The only other time I see this is while (occasionally)deleting many items at once via the web interface (150+), though this method is less consistent.
Any help would be great.
Zabbix 1.8.9(Upgraded from 1.8.7)
RedHat 6.1
MySQL 5.1
I am using the Zabbix API fairly heavily(update/create or delete 50-100 items at a time). The issue I am running into is when there are a bunch of new items are created via some discovery scripts I have written, the web interface stops responding. A look into MySQL processlist shows the following:
| 327126 | zabbix | localhost | zabbix | Query | 0 | Updating | UPDATE ids SET nextid=nextid+1 WHERE nodeid=0 AND table_name='auditlog' AND field_name='auditid' |
| 327476 | zabbix | localhost | zabbix | Query | 0 | Updating | UPDATE ids SET nextid=nextid+1 WHERE nodeid=0 AND table_name='auditlog' AND field_name='auditid' |
| 328163 | zabbix | localhost | zabbix | Query | 0 | Updating | UPDATE ids SET nextid=nextid+1 WHERE nodeid=0 AND table_name='auditlog' AND field_name='auditid' |
| 328694 | zabbix | localhost | zabbix | Query | 0 | Updating | UPDATE ids SET nextid=nextid+1 WHERE nodeid=0 AND table_name='auditlog' AND field_name='auditid' |
| 328695 | zabbix | localhost | zabbix | Query | 0 | Updating | UPDATE ids SET nextid=nextid+1 WHERE nodeid=0 AND table_name='auditlog' AND field_name='auditid' |
| 328779 | zabbix | localhost | zabbix | Query | 0 | Updating | UPDATE ids SET nextid=nextid+1 WHERE nodeid=0 AND table_name='auditlog' AND field_name='auditid' |
| 328790 | zabbix | localhost | zabbix | Query | 0 | Updating | UPDATE ids SET nextid=nextid+1 WHERE nodeid=0 AND table_name='auditlog' AND field_name='auditid' |
| 328793 | zabbix | localhost | zabbix | Query | 0 | Updating | UPDATE ids SET nextid=nextid+1 WHERE nodeid=0 AND table_name='auditlog' AND field_name='auditid' |
| 328794 | zabbix | localhost | zabbix | Query | 0 | Updating | UPDATE ids SET nextid=nextid+1 WHERE nodeid=0 AND table_name='auditlog' AND field_name='auditid' |
| 328810 | zabbix | localhost | zabbix | Query | 0 | Updating | UPDATE ids SET nextid=nextid+1 WHERE nodeid=0 AND table_name='auditlog' AND field_name='auditid' |
| 328845 | zabbix | localhost | zabbix | Query | 0 | Updating | UPDATE ids SET nextid=nextid+1 WHERE nodeid=0 AND table_name='auditlog' AND field_name='auditid' |
| 328861 | zabbix | localhost | zabbix | Query | 0 | Updating | UPDATE ids SET nextid=nextid+1 WHERE nodeid=0 AND table_name='auditlog' AND field_name='auditid' |
These queries never die off, and while this is happening the web interface and the API cannot service requests. Anybody else running into this? The only other time I see this is while (occasionally)deleting many items at once via the web interface (150+), though this method is less consistent.
Any help would be great.