File: gr_group_name_validation_on_boot.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 (15 lines) | stat: -rw-r--r-- 1,144 bytes parent folder | download 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
 
SET GLOBAL group_replication_group_name= "aeaeaeae-aeae-aeae-aeae-aeaeaeaeaeae";
SET SESSION sql_log_bin=0;
call mtr.add_suppression("is not a valid UUID");
call mtr.add_suppression("'group_replication' init function returned error");
SET SESSION sql_log_bin=1;

[connection server1]
[ON SERVER1]
include/start_and_bootstrap_group_replication.inc
# restart:--group-replication-start-on-boot=1 --group-replication-group-name=aaaaaaaa-aaaa-aaaa-aaaa-invalidvalueused --group_replication_local_address=GROUP_REPLICATION_LOCAL_ADDRESS --group_replication_group_seeds=GROUP_REPLICATION_GROUP_SEEDS --group_replication_bootstrap_group=1
# Asserting that the error due to invalid group name is being thrown.
Occurrences of 'is not a valid UUID' in the input file: 1
# restart:--group-replication-start-on-boot=0 --group_replication_local_address=GROUP_REPLICATION_LOCAL_ADDRESS --group_replication_group_seeds=GROUP_REPLICATION_GROUP_SEEDS --group_replication_bootstrap_group=1
SET GLOBAL group_replication_group_name="aaaaaaaa-aaaa-aaaa-aaaa-invalidvalueused";
ERROR 42000: The group_replication_group_name is not a valid UUID, its length is too big