Bug #33481 mysql-test-run --start-and-exit does not establish replication
Submitted: 22 Dec 2007 17:48 Modified: 4 Jan 2008 14:47
Reporter: Philip Stoev Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Tests Severity:S3 (Non-critical)
Version:6.0 OS:Any
Assigned to: Magnus Blåudd CPU Architecture:Any

[22 Dec 2007 17:48] Philip Stoev 
Description:
mysql-test-run --start-and-exit starts two servers, however they are not set up in a master-slave relationship.

This is in contrast with the behavoir in 5.0 when this functionality worked

How to repeat:
$ perl mysql-test-run.pl --start-and-exit rpl_alter
$ ../bin/mysql --socket=var/tmp/slave.sock
$ mysql> show slave status

returns 0 rows.
[22 Dec 2007 17:53] Philip Stoev 
It appears that CHANGE MASTER is required for versions 5.2 and higher, that is, for 6.0

071222 20:51:05 [Warning] The syntax for replication startup options is deprecated and will be removed in MySQL 5.2. Please use 'CHANGE MASTER' instead.
[22 Dec 2007 18:01] Philip Stoev 
The code that connects slave to master is now located include/master-slave-reset.inc and as such only runs when the test itself has run.
[11 Jan 2008 15:11] Magnus Blåudd 
Yes. Then you use --start-and-exit.

The upcoming version of mysql-test-run.pl will have improved support for starting different configurations than the default one.