Details
-
Bug
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
10.11
-
None
-
None
-
Can result in unexpected behaviour
Description
As of 06b2e327fc, changing @@sql_slave_skip_counter raises ER_SLAVE_SKIP_NOT_IN_GTID error when all of these replication mode are set:
- GTID
- multi-domain (@@GLOBAL.gtid_slave_pos has entries of different Domain IDs)
- parallel (@@GLOBAL.slave_parallel_threads > 1)
But the only instance of ER_SLAVE_SKIP_NOT_IN_GTID is in SET @@sql_slave_skip_counter's code - this error can be bypassed (does not emit) as long as @@sql_slave_skip_counter is not set after meeting the criteria:
SET @@GLOBAL.sql_slave_skip_counter= 5; |
SET @@GLOBAL.slave_parallel_threads= 5; |
SET @@GLOBAL.gtid_slave_pos= '1-1-1,2-1-1'; |
CHANGE MASTER TO master_use_gtid= SLAVE_POS; -- no error |
SET @@GLOBAL.gtid_slave_pos= '1-1-1,2-1-1'; -- no error |
SET @@GLOBAL.slave_parallel_threads= 5; -- no error |
SET @@GLOBAL.sql_slave_skip_counter= 5; -- ER_SLAVE_SKIP_NOT_IN_GTID |
Attachments
Issue Links
- relates to
-
MDEV-4937 sql_slave_skip_counter does not work with GTID
-
- Closed
-
-
MDEV-30458 Consolidate Serial Replica to Parallel Replica with 1 Worker Thread
-
- Open
-