[MDEV-17415] Error 1677, cannot start replication on newly imported sql dump. Created: 2018-10-10 Updated: 2019-10-29 Resolved: 2018-10-25 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Replication |
| Affects Version/s: | 10.2.18 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Alexander Chernov | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Debian Jessie |
||
| Issue Links: |
|
||||||||
| Description |
|
Following a crash which affected our entire cluster (as a result of alter table), I am trying to set up a slave in order to recreate data cleanly and shift everything on new server. After making a dump from galera cluster (thus row based binlog)
I import it on new server, and start the replication.
table structure:
Mysql version, configs are the same on both servers, charset is the same... Any hint? |
| Comments |
| Comment by Elena Stepanova [ 2018-10-10 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
What is the actual statement / row event in the binary log which makes the replication choke? | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Alexander Chernov [ 2018-10-10 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Not sure if I am extracting it right because I can't find any statements related to that table.
Reading contents of relay.log with on coordinates 645 there is nothing?
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Alexander Chernov [ 2018-10-10 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Also, just to be clear: this happens everytime I try to make a new dump. So even if newer dumps are imported (and master log position changes as consequence), I am getting this error. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Alexander Chernov [ 2018-10-12 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
My bad, after import I was resetting master info loosing the position in master binlog, which was causing slave starting from the beginning of master's binary logs and choking on the query which have destroyed cluster in the first place. We can close this since I am unable to provide the query which caused the initial issue. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Aurélien LEQUOY [ 2019-10-29 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I got the same problem : MySQL 5.5.27 => MariaDB 10.4.8
in binlog :
on Master :
on slave :
The problem come from mysqldump who made a convertion without say sth ... when you dump / restore one database | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Aurélien LEQUOY [ 2019-10-29 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
on slave
but it's not help :
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Aurélien LEQUOY [ 2019-10-29 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
everything in latin1 now why try to convert in utf8 ? |