We're updating the issue view to help you get more done.Learn more

sql_slave_skip_counter does not work with GTID

sql_slave_skip_counter seems to be completely ignored when slave is configured to use GTID. It might be not such a bad thing, but then I suppose a warning or an error should be produced on slave start if sql_slave_skip_counter was previously set to a non-zero value.

--source include/have_innodb.inc
--source include/have_binlog_format_statement.inc

--let $rpl_topology=1->2
--source include/rpl_init.inc

--echo [master]
create table t1 (i int) engine=InnoDB;
--save_master_pos

--echo [slave]
--connection server_2
--sync_with_master
--source include/stop_slave.inc
change master to master_use_gtid=current_pos;
set global sql_slave_skip_counter = 4;
--source include/start_slave.inc

--connection server_1
insert into t1 values (1);
insert into t1 values (2);
insert into t1 values (3);
--save_master_pos

--connection server_2
--sync_with_master
select * from t1;
show binlog events;

--connection server_1
#show binlog events;
drop table t1;
--source include/rpl_end.inc

cnf

!include suite/rpl/rpl_1slave_base.cnf
!include include/default_client.cnf

[mysqld.1]
log-slave-updates

[mysqld.2]
log-slave-updates

bzr version-info

revision-id: timour@askmonty.org-20130821075108-33rptvhha6vfjzd8
revno: 3681
branch-nick: 10.0-base

Status