-
Incident report
-
Resolution: Fixed
-
Major
-
2.2.0
-
None
I have a template with a LLD, just simple "net.if.discovery" with 4 item prototypes (net.if.in[
{#IFNAME},bytes], net.if.out[{#IFNAME},bytes], net.if.in[
{#IFNAME},packets], net.if.out[{#IFNAME},packets]).
I've linked this template to ~600 hosts. After that zabbix queue started to fill with outdated items. I looked into the database and there was a lot of queries like:
| 3403093 | zabbix | 10.2.68.78:53062 | zabbix | Query | 0 | Updating | update ids set nextid=nextid+1 where nodeid=0 and table_name='graphs' and field_name='graphid' | 0 | 0 | 0 |
| 3403067 | zabbix | 10.2.68.78:53002 | zabbix | Query | 0 | Updating | update ids set nextid=nextid+2 where nodeid=0 and table_name='graphs' and field_name='graphid' | 0 | 0 | 0 |
(show_full_processlist.txt in the attachment)
It seems that database is in some kind of lock state and cannot normally run queries.
After I've waited a few minutes and then I restarted zabbix_server. It helped, database operates normal.
Unfortunately I don't know how to describe it better. I haven't found anything interesting in the zabbix_server log.
I can replicate this issue in my environment. I've even tried using completly different LLD templates - result was the same.
The only pattern I can find to replicate this issue is to link LLD template to a quite large number of hosts.
- duplicates
-
-
- Closed
-