File: schema_dist_participant_timeout.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 (26 lines) | stat: -rw-r--r-- 924 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
 
# Current value of ndb-schema-dist-timeout
select @@ndb_schema_dist_timeout;
@@ndb_schema_dist_timeout
5
set @@ndb_schema_dist_timeout = 120;
ERROR HY000: Variable 'ndb_schema_dist_timeout' is a read only variable
#
# Test participant timeout during schema operation
#
CREATE TABLE t1(
a int primary key
) engine = NDB;
# Setup participant to timeout when schema operation starts
set GLOBAL debug="+d,ndb_schema_op_start_timeout";
# Expect warning printed on node where schema operation is started
call mtr.add_suppression("Schema dist coordinator detected timeout");
# Run schema operation to trigger participant timeout
ALTER TABLE t1 ALGORITHM=copy, ADD COLUMN b int;
Warnings:
Warning	1296	Node <nodeid> 'Participant timeout'
# Reset participant to not timeout anymore
set GLOBAL debug="-d,ndb_schema_op_start_timeout";
# Check that schema operation suceeded on another MySQL Server
SELECT * FROM t1;
a	b
DROP TABLE t1;