Thomas Plant writes:
> Today I had time to look at the error, removed the duplicate ID from
> the table and started the slave thread again using 'start slave;'.
>
> But now I get another error:
>
> Last_IO_Error: Got fatal error 1236 from master when reading data from
> binary log: 'Error: connec
slave-skip-errors = all = I don't care about my data.
You almost certainly do not want to be using this. Really the only use-case for
this is skipping specific errors when there is no chance of getting it fixed,
i.e. legacy applications. Even then it's not a great idea.
Rhys
About replication, I dont let it stop on duplicate keys, I prefer to use
slave-skip-errors = all and let the primary key on the tables take care of
duplicate records.
Replication will only stop if something is corrupted, which may be your
case. Some position the the binlog got lost in the power
Hi Thomas,
Could you please show the output of SHOW SLAVE STATUS and SHOW VARIABLES
LIKE 'gtid%' ?
Thanks
Guillaume Lefranc
signal18.io consulting
Le mer. 4 juil. 2018 à 12:31, Thomas Plant a écrit :
> Hello,
>
> I'd have a question about MariaDB 10.1 replication, which has been
> interrupted
Hello,
I'd have a question about MariaDB 10.1 replication, which has been
interrupted by a power outage in our datacenter.
We started the master server and had a duplicate id in a table on the
slave, so replication stopped. We did not have time to adjust this at
the moment, there were a lot of
5 matches
Mail list logo
