Hello there
For a few weeks now I have been have problems with this query
"SELECT h.* FROM history_uint h WHERE (h.itemid BETWEEN '651600' AND '651651' OR h.itemid BETWEEN '651660' AND '651671' OR h.itemid BETWEEN '651673' AND '651677' OR h.itemid BETWEEN '651681' AND '651750' OR h.itemid BETWEEN '651844' AND '651868' OR h.itemid BETWEEN '651874' AND '651881' OR h.itemid BETWEEN '651883' AND '651889' OR h.itemid BETWEEN '651891' AND '651923' OR h.itemid BETWEEN '651925' AND '651936' OR h.itemid BETWEEN '875746' AND '875750' OR h.itemid BETWEEN '1374509' AND '1374514' OR h.itemid IN ('651653','651654','651655','651657','651658','651 679','651870','651871','736559','741031','741032', '751589','789537','804598','811651','877500','8775 01','953831','957805','957806','961030','985045',' 1041493','1041494','1041495','1109733','1109734',' 1120543','1120544','1144970','1144971','1160945',' 1201127','1380676','1380677','1386334','1418475',' 1492880','1506486','1512747','1539725','1539726',' 1539727')) AND h.clock>='1522033200' AND h.clock<='1522072034' ORDER BY h.clock"
Zabbix keeps sending lots of this same query (changing only the period in the h.clock), and the query keeps geting stuck, making the database CPU go 100%.
I asked the help of a DBA, as I didnt change anything in the zabbix and this problem started out of nowhere, and he tried lots of things, including indexing this select, and the problem continues.
Someone knows what this query does and why zabbix started sending so many of those? I am lost
Thank you
For a few weeks now I have been have problems with this query
"SELECT h.* FROM history_uint h WHERE (h.itemid BETWEEN '651600' AND '651651' OR h.itemid BETWEEN '651660' AND '651671' OR h.itemid BETWEEN '651673' AND '651677' OR h.itemid BETWEEN '651681' AND '651750' OR h.itemid BETWEEN '651844' AND '651868' OR h.itemid BETWEEN '651874' AND '651881' OR h.itemid BETWEEN '651883' AND '651889' OR h.itemid BETWEEN '651891' AND '651923' OR h.itemid BETWEEN '651925' AND '651936' OR h.itemid BETWEEN '875746' AND '875750' OR h.itemid BETWEEN '1374509' AND '1374514' OR h.itemid IN ('651653','651654','651655','651657','651658','651 679','651870','651871','736559','741031','741032', '751589','789537','804598','811651','877500','8775 01','953831','957805','957806','961030','985045',' 1041493','1041494','1041495','1109733','1109734',' 1120543','1120544','1144970','1144971','1160945',' 1201127','1380676','1380677','1386334','1418475',' 1492880','1506486','1512747','1539725','1539726',' 1539727')) AND h.clock>='1522033200' AND h.clock<='1522072034' ORDER BY h.clock"
Zabbix keeps sending lots of this same query (changing only the period in the h.clock), and the query keeps geting stuck, making the database CPU go 100%.
I asked the help of a DBA, as I didnt change anything in the zabbix and this problem started out of nowhere, and he tried lots of things, including indexing this select, and the problem continues.
Someone knows what this query does and why zabbix started sending so many of those? I am lost
Thank you
Comment