-
Incident report
-
Resolution: Won't fix
-
Major
-
None
-
1.8.6
-
redhat 5.4
mysql-5.1.59-Percona
Innodb
1.8.6
Number of hosts (monitored/not monitored/templates) 1639 1599 / 25 / 15
Number of items (monitored/disabled/not supported) 68100 59458 / 0 / 8642
Number of triggers (enabled/disabled)[problem/unknown/ok] 17505 15952 / 1553 [555 / 2171 / 13226]
Required server performance, new values per second 700.87 -
----- During conversion to DM.
/usr/sbin/zabbix_server -n 1 -c /etc/zabbix/zabbix_server.conf
Query against the history table
update history set itemid=itemid+100100000000000 where itemid>0
---------------------------------------------------------------------------------------------+
| id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra |
---------------------------------------------------------------------------------------------+
| 1 | SIMPLE | history | range | history_1 | history_1 | 8 | NULL | 314696947 | Using where; Using index |
---------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)
for setups with larger volumes of data, this could potentially stall/lag/hang/crash the Innodb engine. (no separate purge thread).
It would probably be better to parallelize and chunk the queries used for DM conversion.