[MDEV-9759] MaraiDB 10.0 with Tokudb Slave can not replicaste from Master MairaDB 5.5 with Tokudb 7.1.0 Created: 2016-03-18 Updated: 2021-02-27 Resolved: 2016-04-15 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - TokuDB |
| Affects Version/s: | 5.5 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | ye | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | need_feedback | ||
| Environment: |
Server version: 5.5.30-tokudb-7.1.0-MariaDB-log MariaDB Server |
||
| Description |
|
What is the upgrade path for MariaDB with Tokudb ? Tried 10.1 - but didn't work IS POSSIBLE TO REPLICATE FROM 5.5 MASTER to A 10.0 SLAVE WITH TOKUDB ?
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
Doing a mysqldump in PROD would take +1 day total down time of Prod MASTER I trying to migrate from one Datacenter with MySQL 5.5 with 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 After several attempt I was able to start the replication from 5.5 to 10.0 Last_SQL_Errno: 1032 [(none)]> stop slave; [(none)]> set GLOBAL SQL_SLAVE_SKIP_COUNTER = 1 ; [(none)]> start slave; Last_SQL_Errno: 1032 |
| Comments |
| Comment by Elena Stepanova [ 2016-03-18 ] |
The 5.5 server that you are using is an ancient build created by a company that no longer exists, I can't find the downloadable binary and check what exactly can go wrong there. Of course, for every point above there can be bugs that we are not aware of, which prevent things from working correctly; if you encounter them, please create bug reports. For the rest of your complaints in the description, please formulate them in a readable manner if you want us to analyze them.
Tried to do what? To run the server on the old datadir? To replicate? Did not work how? Did it crash? Did it refuse to start? What did it say?
What did the slave status say? Was there an error? What did the error log say? What exactly was the CREATE statement? Did it use the syntax which is different between MariaDB and Tokutek (see the link above)?
Are you sure that on the master you have ALL binary logs from the begining of time? If you don't, you are very likely to get the problem you described next:
This is a generic replication error which most likely has nothing to do with TokuDB specifically, it just means that your data on master and slave wasn't consistent by the time the event was processed, which is not surprising considering your rough path to this point. |
| Comment by Elena Stepanova [ 2016-04-15 ] |
|
Please comment to re-open if you have further information on the issue. |