[MDEV-25157] Replication ignores --slave_skip_error option and stops with "CONNECT Unsupported command" Created: 2021-03-16  Updated: 2023-04-27

Status: Open
Project: MariaDB Server
Component/s: Replication, Storage Engine - Connect
Affects Version/s: 10.2, 10.3, 10.4, 10.5
Fix Version/s: 10.4, 10.5

Type: Bug Priority: Major
Reporter: Alice Sherepa Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: None

Issue Links:
Relates
relates to MDEV-15498 replication connect engine Slave: Acc... Closed

 Description   

To reproduce in mtr run test case from MDEV-15498 +
add an option file with --slave_skip_errors=1148 or --slave_skip_errors=all

--source include/master-slave.inc
--source include/have_innodb.inc
--source include/have_binlog_format_row.inc
 
connection slave;
show variables like 'slave_skip_errors';
CREATE USER u@'%' IDENTIFIED BY 'password';
GRANT ALL ON db1.* TO u@'%' IDENTIFIED BY 'password';
flush privileges;
 
create database db1;
CREATE TABLE db1.t1c ( id int primary key, msg varchar(100)) ENGINE=innodb;
INSERT INTO  db1.t1c VALUES (1, 'initial');
 
connection master;
 
eval CREATE TABLE test.t1 ( id int primary key, msg varchar(100))
ENGINE=CONNECT DEFAULT CHARSET=utf8 
  CONNECTION='mysql://u:password@127.0.0.1:$SLAVE_MYPORT/db1/t1c'
  TABLE_TYPE=MYSQL;
 
select * from test.t1;
 
connection master;
--sync_slave_with_master
 
select * from test.t1;
 
connection master;
 
insert into test.t1 VALUES(2,'test');
select * from test.t1; 
 
--sync_slave_with_master
 
select * from test.t1;
select * from db1.t1c;


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