Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Incomplete
-
5.5(EOL)
-
Server version: 5.5.30-tokudb-7.1.0-MariaDB-log MariaDB Server
Description
What is the upgrade path for MariaDB with Tokudb ?
currently running Production with
Server version: 5.5.30-tokudb-7.1.0-MariaDB-log MariaDB Server
Tried 10.1 - but didn't work
Tried 10.0 - was able to startup with old datafiles - but while creating new tokudb on 5.5 Master it did not show up or replicate to 10.0 Slave ...
IS POSSIBLE TO REPLICATE FROM 5.5 MASTER to A 10.0 SLAVE WITH TOKUDB ?
- can 10.0 Tokudb SLAVE replicate from mysql 5.5 TokuDB MASTER db ??
I know the Tokudb File header structure is different in MySQL 5.5 (FH FileHeader v2.4) and 10.0 has FH v2.7 or something
but
is it possible for a 10.0 Slave database to read from a 5.5 Master ???
- or am I Doomed !! ?
Doing a mysqldump in PROD would take +1 day total down time of Prod MASTER
Copy the massive dump over to new Datacenter
Import dump which would take another day or two ....
Then point the application to start using the new Datacenter ....
This is not really acceptable to be down a couple day switching datacenteers!!
I trying to migrate from one Datacenter with MySQL 5.5 with tokudb storage engine
to a new datacenter with MySQL 10.0 w/ tokudb storage engine
I am trying to do this by building out Slaves in new datacenter reading from Master in Old Datacenter and when they are caught up - have a production outage for a couple minutes
Flush the master logs then switch application to read/write from old to new datacenter where I appoint one of the Slaves to be the new Master
After several attempt I was able to start the replication from 5.5 to 10.0
but I run into error
and I have to do too many GLOBAL skips_counters
so I have a feeling it's not supported to read from Tokudb 5.5 on a 10.0 slave....
Last_SQL_Errno: 1032
Last_SQL_Error: Could not execute Update_rows_v1 event on table YSIUSER.ysi_batch_notices; Can't find record in 'ysi_batch_notices', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log sjcprddbv202-binlog.023152, end_log_pos 9401388
[(none)]> stop slave;
Query OK, 0 rows affected (0.00 sec)
[(none)]> set GLOBAL SQL_SLAVE_SKIP_COUNTER = 1 ;
Query OK, 0 rows affected (0.00 sec)
[(none)]> start slave;
Query OK, 0 rows affected (0.00 sec)
Last_SQL_Errno: 1032
Last_SQL_Error: Could not execute Update_rows_v1 event on table YSIUSER.ysi_batch_notices; Can't find record in 'ysi_batch_notices', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND;