[MDEV-19507] In multi-statement: Error 'Table doesn't exist' on MySQL master not picked up by MariaDB slave Created: 2019-05-17 Updated: 2024-02-02 Resolved: 2019-05-20 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Replication |
| Affects Version/s: | 10.3.14 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | susil.behera | Assignee: | Unassigned |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | None | ||
| Environment: |
CentOS 7 |
||
| Description |
|
On a replication setup from MySQL 5.7 master to MariaDB 10.3.14 slave, if we execute multiple statements which drop one existing-table and another non-existing-table then Error 'Table doesn't exist' on master is not picked up by slave. Repro Steps - @master
@slave
@master
@slave
Expected - |
| Comments |
| Comment by Elena Stepanova [ 2019-05-20 ] |
|
I don't see anything wrong in the output that you provided. Please clarify what is the problem here and what you mean by "error is not picked up by slave". Replication replicates schema and data updates, not error messages. |
| Comment by susil kumar behera (Inactive) [ 2019-05-20 ] |
|
elenst, Here are my further observations: I think we at the Clustrix side need to see why are we doing differently from MySQL. Sorry for the trouble. We can close this bug. |