We've got a LARGE environment. Our Zabbix database is 160+ GB in size. Stopped the server, upgraded to 3.2 and then started the server.
During the database upgrade, which took a LONG TIME, it failed with:
3116:20160921:093100.083 current database version (mandatory/optional): 03000000/03000000
3116:20160921:093100.083 required mandatory version: 03020000
...
3116:20160921:095643.410 [Z3005] query failed: [1206] The total number of locks exceeds the lock table size [insert into event_recovery (eventid,r_eventid) values (131130718,131130815) …..
(excluded a billion values here)
3116:20160921:095643.428 database upgrade failed
and then zabbix restarted the server up again and started the upgrade again. Will this eventually complete or do I need to do something else to get this to work correctly?
All our Zabbix hosts are in VMWare, and I made a snapshot before, so I was able to immediately revert, thankfully.
thanks for the help!
During the database upgrade, which took a LONG TIME, it failed with:
3116:20160921:093100.083 current database version (mandatory/optional): 03000000/03000000
3116:20160921:093100.083 required mandatory version: 03020000
...
3116:20160921:095643.410 [Z3005] query failed: [1206] The total number of locks exceeds the lock table size [insert into event_recovery (eventid,r_eventid) values (131130718,131130815) …..
(excluded a billion values here)
3116:20160921:095643.428 database upgrade failed
and then zabbix restarted the server up again and started the upgrade again. Will this eventually complete or do I need to do something else to get this to work correctly?
All our Zabbix hosts are in VMWare, and I made a snapshot before, so I was able to immediately revert, thankfully.
thanks for the help!
Comment