-
Incident report
-
Resolution: Duplicate
-
Major
-
None
-
2.0.0rc1
-
2xXeon @2.8Ghz, 8GB RAM, RAID10, Mysql+InnoDB (Debian Stable 64bit, Mysql server 5.1.49-3, Apache2 2.2.16-6+squeeze6, PHP5 5.3.3-7+squeeze8)
Patching to 2.0 take too long. Working is only 1 thread on 4 cores.
Patching 13GB DB take 19h30m.
Could you please improve upgrade to run more threads ? Can Zabbix 1.8 run during upgrade db to 2.0 to ?
time ./upgrade zabbix
WARNING: backup your database before performing upgrade
This is an UNSUPPORTED Zabbix upgrade script from 1.8 to 2.0 for MySQL
It does the following things:
1. Updates indexes that might require changes;
2. Patches the database from 1.8 schema to 2.0 schema;
3. Adds 'Disabled' and 'Debug' usergroup if any missing;
4. Checs for hosts not belonging to any group and adds them to one if any found.
Usage: pass required MySQL parameters to this script (like database, user, password etc).
Continue ? (y/n) y
Dropping indexes that might need re-creation...
... dropping of indexes took 0:00:00
Creating possibly missing indexes...
creating of indexes took 0:00:00
Patching the database
... patching of the database took 19:26:34
bash >= 4.1 detected
Checking for 'Disabled' user group... found, not doing anything.
Checking for 'Debug' user group... not found, adding.
Checking for hosts not belonging to any group... not found any
... checking for hosts not belonging to any group took 0:00:00
real 1166m35.917s
user 0m0.260s
sys 0m0.128s
- duplicates
-
ZBX-5359 Database migration to V2 schema too lengthy for preexisting databases and production environments
- Closed