~drizzle-trunk/drizzle/development

« back to all changes in this revision

Viewing changes to tests/include/master-slave-reset.inc

  • Committer: Mark Atwood
  • Date: 2011-11-14 07:30:41 UTC
  • Revision ID: me@mark.atwood.name-20111114073041-mo2hgg8ouseo2kpu
releaseĀ 2011.11.29

Show diffs side-by-side

added added

removed removed

Lines of Context:
1
 
connection slave;
2
 
 
3
 
#we expect STOP SLAVE to produce a warning as the slave is stopped
4
 
#(the server was started with skip-slave-start)
5
 
--disable_warnings
6
 
stop slave;
7
 
--wait_for_slave_to_stop
8
 
--enable_warnings
9
 
 
10
 
connection master;
11
 
--disable_warnings
12
 
--disable_query_log
13
 
use test;
14
 
--enable_query_log
15
 
drop table if exists t1,t2,t3,t4,t5,t6,t7,t8,t9;
16
 
--enable_warnings
17
 
reset master;
18
 
connection slave;
19
 
 
20
 
--disable_warnings
21
 
# the first RESET SLAVE may produce a warning about non-existent
22
 
# 'ndb_apply_status' table, because this table is created
23
 
# asynchronously at the server startup and may not exist yet
24
 
# if RESET SLAVE comes too soon after the server startup
25
 
reset slave;
26
 
--enable_warnings
27
 
 
28
 
# Clean up old test tables
29
 
--disable_warnings
30
 
drop table if exists t1,t2,t3,t4,t5,t6,t7,t8,t9;
31
 
--enable_warnings
32
 
 
33
 
--disable_query_log
34
 
eval CHANGE MASTER TO MASTER_USER='root',
35
 
                      MASTER_CONNECT_RETRY=1,
36
 
                      MASTER_HOST='localhost',
37
 
                      MASTER_PORT=$MASTER_MYPORT;
38
 
--enable_query_log
39
 
 
40
 
start slave;