[MDEV-14171] CLONE - Unable to load replication GTID slave state from mysql.gtid_slave_pos: Table 'mysql.gtid_slave_pos' doesn't exist in engine Created: 2017-10-27 Updated: 2017-10-30 Resolved: 2017-10-30 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Replication |
| Affects Version/s: | 10.0.31 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Minor |
| Reporter: | Søren Thorsen | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | gtid | ||
| Environment: |
CentOS 6.2/6.3 and Ubuntu 16.04 LTS |
||
| Issue Links: |
|
||||||||
| Description |
|
I have the same issue as the original issue, maybe I can help providing debug information My current setup is with a master is MariaDB version 5.5.58 on a CentOS 6.2 and a slave MariaDB version 5.5.58 on a CentOS 6.3 I installed a new MariaDB version 10.0.31 on a Ubuntu 16.04 LTS. Stopped the old slave and copied the datadir to the new server. After I did a `mysql_upgrade` I could start mysql. When I start the slave, it is starting to replicate. The mysql.gtid_slave_pos table exist on the new slave. If I try to create the table on the master matching the table on the slave does not do any change --------------------------------------------------------------------------------------------------------------------- Last_SQL_Error: Unable to load replication GTID slave state from mysql.gtid_slave_pos: Table 'mysql.gtid_slave_pos' doesn't exist in engine So I tried a `mysql_upgrad` which told me to try --force as it looked already up to date, legit, so I tried --force, which gave: mysql.gtid_slave_pos Don't know what to do from now, I expected to mysql_upgrade to fix it þ |
| Comments |
| Comment by Elena Stepanova [ 2017-10-30 ] |
|
There is no need to clone the issue, you can comment on the issue Since you haven't yet provided any here, I'm closing it as a duplicate of The request in the original issue still holds: please paste or attach there (in |