[MDEV-19497] Replication stops because table not found Created: 2019-05-16  Updated: 2019-06-01  Resolved: 2019-05-20

Status: Closed
Project: MariaDB Server
Component/s: Data Manipulation - Update, Replication
Affects Version/s: 10.3.15
Fix Version/s: 10.2.25, 5.5.65, 10.1.41, 10.3.16, 10.4.6

Type: Bug Priority: Major
Reporter: Alex Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: 10.3.15, cluster, replication, update

Issue Links:
Duplicate
duplicates MDEV-19491 update query stopped working after ma... Closed

 Description   

We have upgraded 2 servers of our 4-server-MariaDB-cluster from 10.3.14 to 10.3.15 today and since then we had several slave-stops only on the 10.3.15-nodes because a table could not be found, but the table existed. It was always the same table and a "start slave;" solved the problem - there was no need to skip the query.

Last_Error: Error 'Table 'db1.table1' doesn't exist' on query. Default database: 'db1'. Query: 'UPDATE `table1` AS `cpm` INNER JOIN `table2` AS `cp` ON (`cpm`.`id` = `cp`.`id`) SET `cpm`.`flags` = CONCAT_WS(',', IF(`cpm`.`flags` = '', NULL, `cpm`.`flags`), 'DELETED') WHERE `cp`.`pid` = 1234 AND (`cpm`.`flags` IS NULL || FIND_IN_SET('DELETED', `cpm`.`flags`) = 0)'


Generated at Thu Feb 08 08:52:09 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.