File: rpl_slave_start_after_clone.test

package info (click to toggle)
mysql-8.0 8.0.43-3
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 1,273,924 kB
  • sloc: cpp: 4,684,605; ansic: 412,450; pascal: 108,398; java: 83,641; perl: 30,221; cs: 27,067; sql: 26,594; sh: 24,181; python: 21,816; yacc: 17,169; php: 11,522; xml: 7,388; javascript: 7,076; makefile: 2,194; lex: 1,075; awk: 670; asm: 520; objc: 183; ruby: 97; lisp: 86
file content (30 lines) | stat: -rw-r--r-- 929 bytes parent folder | download 
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
 
# ==== Purpose ====
#
# This server proves that if correctly configured we can clone a
# a slave and it will start replicating on server start.
#
# ==== Implementation ====
#
# 1. Set up a replication connection from server 1 to server 2
# 2. Create a table for testing
# 3. Install clone on server 2
#    Configure server 3 to invoke clone
# 4. Execute a transaction on server 1, check 3 received it
# 5. Cleanup
#
# ==== References ====
#
# Bug#29995256: PRIVILEGE_CHECKS_USER NOT CLONED FOR RECOVERY CHANNEL
#

--source include/have_mysqld_monitoring_process.inc
--source include/have_clone_plugin.inc
# Test requires master-info-repository=TABLE, relay-log-info-repository=TABLE
--source include/have_slave_repository_type_table.inc

--source include/master-slave.inc

--source extra/rpl_tests/rpl_replica_start_after_clone.inc
--source extra/rpl_tests/rpl_replica_start_after_clone_cleanup.inc

--source include/rpl_end.inc