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

Multi-source: Behavior of "RESET SLAVE 'name'" is inconsistent with the normal RESET SLAVE

Description

"RESET SLAVE 'masterX'" totally removes the masterX configuration.
It's inconsistent with normal "RESET SLAVE" behavior, which clears the replication position, but keeps the configuration (while "RESET SLAVE ALL" removes everything). In our case, when the name is provided, "RESET SLAVE 'name'" and "RESET SLAVE 'name' ALL" seem to be identical.

Below is a test case for RESET SLAVE (no result file yet, because the test case fails at line 35 with "1617: There is no master connection 'master1":

cat suite/multi_source/reset_slave.test

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 --enable_connect_log --connect (slave,127.0.0.1,root,,,$SERVER_MYPORT_3) --replace_result $SERVER_MYPORT_1 MYPORT_1 eval change master 'master1' to master_port=$SERVER_MYPORT_1, master_host='127.0.0.1', master_user='root'; start slave 'master1'; set default_master_connection = 'master1'; --source include/wait_for_slave_to_start.inc --connect (master1,127.0.0.1,root,,,$SERVER_MYPORT_1) --disable_warnings drop table if exists t1; --enable_warnings create table t1 (i int) engine=MyISAM; insert into t1 values (1),(2); --save_master_pos --connection slave --sync_with_master 0,'master1' stop slave 'master1'; --wait_for_slave_to_stop --replace_result $SERVER_MYPORT_1 MYPORT_1 show slave 'master1' status; reset slave 'master1'; --replace_result $SERVER_MYPORT_1 MYPORT_1 show slave 'master1' status; reset slave 'master1' all; --error WARN_NO_MASTER_INFO show slave 'master1' status; # Cleanup drop table t1; --connection master1 drop table t1; --disconnect slave --disconnect master1

Environment

None

Status

Assignee

Michael Widenius

Reporter

Elena Stepanova

Labels

None

External issue ID

None

External issue ID

None

Priority

Major