[MDEV-28382] Replication fails when dropping multiple tables with foreign key constraints multiple times Created: 2022-04-21 Updated: 2022-04-25 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Server |
| Affects Version/s: | 10.6.7 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Volker Klasen | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Dropping multiple tables that have foreign key constraints due to which one or some of the tables cannot be dropped and repeating dropping the same tables again will lead to a replication failure. On both primary and replica all tables will be dropped, but the replication stops with an error. How to reproduce:
The second drop table command causes the replication to stop. Cheers |
| Comments |
| Comment by Alice Sherepa [ 2022-04-25 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I could not repeat it, could you please add the output of SHOW SLAVE STATUS; and also SHOW BINLOG EVENTS or attach the binlog file for these events. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Volker Klasen [ 2022-04-25 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Binlog Events:
show replica status:
Maybe an important detail: we're using row-based replication |