[MDEV-23912] Orphan files left after failed relay log initialization (multi-source replication) Created: 2020-10-07  Updated: 2023-04-27

Status: Open
Project: MariaDB Server
Component/s: Replication
Affects Version/s: 10.0, 10.1, 10.2, 10.3, 10.4, 10.5, 10.6
Fix Version/s: 10.4, 10.5, 10.6

Type: Bug Priority: Major
Reporter: Alice Sherepa Assignee: Brandon Nesterenko
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
Duplicate
is duplicated by MDEV-21289 multi_source.multisource and binlog_... Closed
Relates
relates to MDEV-26307 multi-source-replication support mysq... Closed

 Description   

--source include/master-slave.inc
--connection slave
 
CALL mtr.add_suppression("Failed to open the relay log './no_such_log' \\(relay_log_pos 4\\)");
CALL mtr.add_suppression("Could not find target log during relay log initialization");
 
--error ER_RELAY_LOG_INIT
change master 'm2' to relay_log_file='no_such_log';
 
# error is expected, but files like master-m2.info, relay-log-m2.info are created and will exist in datadir. reset slave will not work, as there is no slave 'm2'.
 
#fails because of "Failed to open the relay log './some_log' "
--error 1201
change master 'm2' to  master_user='root';
 
--source include/rpl_end.inc



 Comments   
Comment by Angelique Sklavounos (Inactive) [ 2022-12-07 ]

The behavior of this ticket was fixed in 10.7, specifically with https://github.com/MariaDB/server/commit/4ebaa80f0b26de814e8de27b8ea2188038b7d0f2

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