[MDEV-26479] slave_skip_errors ddl_exist_errors Not Picked up Created: 2021-08-25  Updated: 2021-08-25

Status: Open
Project: MariaDB Server
Component/s: Configuration
Affects Version/s: 10.5.12
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Jervin R Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Environment:

When setting slave_skip_errors to include or exclusively to ddl_exist_errors, the correct error codes/names are not picked up.



 Description   

When setting slave_skip_errors to include or exclusively to ddl_exist_errors, the correct error codes/names are not picked up.

$ grep skip /etc/my.cnf
skip-slave-start = '1'
slave_skip_errors = 'ddl_exist_errors'

Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MariaDB connection id is 6
Server version: 10.5.12-MariaDB Source distribution
 
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
 
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
 
MariaDB [(none)]> show global variables like '%skip%';
+----------------------------------+-----------+
| Variable_name                    | Value     |
+----------------------------------+-----------+
| replicate_events_marked_for_skip | REPLICATE |
| skip_external_locking            | ON        |
| skip_name_resolve                | OFF       |
| skip_networking                  | OFF       |
| skip_show_database               | OFF       |
| slave_skip_errors                | OFF       |
| sql_slave_skip_counter           | 0         |
+----------------------------------+-----------+
7 rows in set (0.001 sec)


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