MySQL Bugs: #38989: Slave can not replay relay logs again

Bug #38989	Slave can not replay relay logs again
Submitted:	24 Aug 2008 8:53	Modified:	8 Dec 2009 3:03
Reporter:	Serge Kozlov	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S1 (Critical)
Version:	5.0,5.1,6.0	OS:	Any
Assigned to:	Assigned Account	CPU Architecture:	Any
Tags:	Logs, relay, replay, replication

Description:
Slave can' replay own relay log files as it described at http://dev.mysql.com/doc/refman/5.0/en/change-master-to.html:

CHANGE MASTER TO
  RELAY_LOG_FILE='slave-relay-bin.006',
  RELAY_LOG_POS=4025;
START SLAVE SQL_THREAD;

Server returns: 
1380: Failed initializing relay log position: Could not find target log during relay log initialization

How to repeat:
There are two ways to repeat:
1. Manual. 
 a) Setup replication.
 b) Do something on master and make sure that it appears on slave
 c) stop slave, remove data
 b) try execute CHANGE MASTER

2). Use following test case for mtr:
--source include/master-slave.inc
--connection master
CREATE TABLE t1(a INT NOT NULL PRIMARY KEY, b INT) ENGINE=MyISAM;
INSERT INTO t1 VALUES (1, 100);
SELECT * FROM t1;

--sync_slave_with_master
SELECT * FROM t1;
--let $relay_file=query_get_value(SHOW SLAVE STATUS, Relay_Log_File, 1)
DROP TABLE t1;
STOP SLAVE;
--source include/wait_for_slave_to_stop.inc
--replace_result $relay_file RELAY_FILe
--eval CHANGE MASTER TO RELAY_LOG_FILE='$relay_log_file', RELAY_LOG_POS=4
START SLAVE SQL_THREAD
--sleep 2
SELECT * FROM t1;

Workaround: let slave catch up from master's binary logs instead of from slave's relay logs.  Extra network I/O, but acceptable for most users.

Additional Workaround: adding ./ to beginning of relay log file name in CHANGE MASTER TO statement should allow read of relay log:
CHANGE MASTER TO RELAY_LOG_FILE='./relay_log_file', RELAY_LOG_POS=4

hi,
  Does it relate to Bug #12190?
  I think this is a duplicated one ...

This does appear to be a duplicate of http://bugs.mysql.com/bug.php?id=12190