File: rpl_multi_source_block_receiver.result

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 (48 lines) | stat: -rw-r--r-- 2,658 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
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
include/rpl_init.inc [topology=1->2,3->2,4->2]
Warnings:
Note	####	Sending passwords in plain text without SSL/TLS is extremely insecure.
Note	####	Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.
Warnings:
Note	####	Sending passwords in plain text without SSL/TLS is extremely insecure.
Note	####	Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.
Warnings:
Note	####	Sending passwords in plain text without SSL/TLS is extremely insecure.
Note	####	Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.
[connection server_1]
CREATE TABLE t1 (c1 INT) ENGINE=InnoDB;
INSERT INTO t1 VALUES(1);
[connection server_2]
include/start_slave.inc [FOR CHANNEL 'channel_1']
# Adding debug point 'updating_received_transaction_set' to @@GLOBAL.debug
[connection server_1]
INSERT INTO t1 VALUES(2);
[connection server_2]
SET DEBUG_SYNC="now WAIT_FOR reached_updating_received_transaction_set";
# Removing debug point 'updating_received_transaction_set' from @@GLOBAL.debug
[connection server_4]
CREATE TABLE t4 (c1 INT) ENGINE=InnoDB;
INSERT INTO t4 VALUES(1);
DROP TABLE t4;
[connection server_2]
START SLAVE FOR CHANNEL 'channel_4';
Warnings:
Warning	1287	'START SLAVE' is deprecated and will be removed in a future release. Please use START REPLICA instead
Wait until channel_4 be synchronized with master
[connection server_3]
CREATE TABLE t2 (a int);
INSERT INTO t2 VALUES(1);
INSERT INTO t2 VALUES(2);
[connection server_2]
include/assert.inc [Restoring backup is successful]
SET DEBUG_SYNC="now SIGNAL continue_updating_received_transaction_set";
[connection server_1]
DROP TABLE t1;
include/sync_slave_sql_with_master.inc [FOR CHANNEL 'channel_1']
include/start_slave.inc [FOR CHANNEL 'channel_3']
[connection server_3]
DROP TABLE t2;
include/sync_slave_sql_with_master.inc [FOR CHANNEL 'channel_3']
include/rpl_end.inc
RESET REPLICA ALL FOR CHANNEL 'channel_1';
RESET REPLICA ALL FOR CHANNEL 'channel_3';
RESET REPLICA ALL FOR CHANNEL 'channel_4';