File: util_tables_drop.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 (51 lines) | stat: -rw-r--r-- 1,965 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
49
50
51
--source connect.inc

#
# Test behavior of ndbcluster and in particular the "ndb binlog thread"
# when its util tables are dropped from NDB.
# - the tables are important for the functionality of binlog and schema
#   distribution
# - currently there are three util tables created by ndbcluster:
#  1) mysql.ndb_schema
#  -- communication between the MySQL Servers during schema distribution
#  -- hidden for both DDL and DML for a MySQL Server user
#  -- schema distribution will be disabled if table is dropped from NDB
#  -- the "ndb binlog thread" will continously attempt to recreate the table
#     in order to enable schema distribution functionality
#  2) mysql.ndb_schema_result
#  -- communication between the MySQL Servers during schema distribution
#  -- hidden for both DDL and DML for a MySQL Server user
#  -- schema distribution will be disabled if table is dropped from NDB
#  -- the "ndb binlog thread" will continously attempt to recreate the table
#     in order to enable schema distribution functionality
#  3) mysql.ndb_apply_status
#  -- keeps a record of the operations that have been replicated
#  -- currently not hidden for either DDL or DML for a MySQL Server user
#  -- if this table is dropped from NDB, the "ndb binlog thread" will
#     have an outage, which means it will:
#  --- stop logging changes from NDB
#  --- write error message(s) to log file
#  --- tear everything down and restart itself
#  --- create the table again while reconnecting to NDB
#

# Silence the expected errors which occur when util tables are dropped
--disable_query_log
let $i = $NUM_MYSQLDS;
while($i)
{
  --connection mysqld$i
  call mtr.add_suppression("An incident event has been written");
  dec $i;
}
--enable_query_log

let $util_table_name = ndb_schema;
--source check_util_table_drop.inc

let $util_table_name = ndb_apply_status;
--source check_util_table_drop.inc

let $util_table_name = ndb_schema_result;
--source check_util_table_drop.inc