Edit File: rpl_recovery_replicate_same_server_id.result
include/master-slave.inc Warnings: Note #### Sending passwords in plain text without SSL/TLS is extremely insecure. Note #### Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information. [connection master] [connection slave] call mtr.add_suppression("Failed to initialize the master info structure"); call mtr.add_suppression("Error during --relay-log-recovery *"); CREATE TABLE t1 ( n INT); RESET MASTER; include/stop_slave.inc include/wait_for_slave_to_stop.inc CHANGE MASTER TO MASTER_PORT=SLAVE_PORT; START SLAVE IO_THREAD; include/wait_for_slave_io_to_start.inc include/rpl_stop_server.inc [server_number=2] include/rpl_start_server.inc [server_number=2 parameters: --skip_slave_start=FALSE --master-info-repository=TABLE --relay-log-info-repository=TABLE --relay-log-recovery=1] Matching lines are: --TIME-- [ERROR] Error during --relay-log-recovery: replicate_same_server_id is in use and sql thread's positions are not initialized, hence relay log recovery cannot happen. Occurrences of the Error during --relay-log-recovery in the input file : 1 include/rpl_restart_server.inc [server_number=2 parameters: --master-info-repository=TABLE --relay-log-info-repository=TABLE --relay-log-recovery=0] DROP TABLE t1; change master to master_port=MASTER_PORT; include/start_slave.inc include/rpl_end.inc