Bug #91347 Start GR results in crash if group_name is invalid
Submitted: 21 Jun 2018 9:04 Modified: 9 Aug 2018 13:08
Reporter: Dhruthi Komarlu Vasudeva Murthy Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Group Replication Severity:S2 (Serious)
Version:8.0.13 OS:Any
Assigned to: CPU Architecture:Any

[21 Jun 2018 9:04] Dhruthi Komarlu Vasudeva Murthy 
Description:
Starting GR on a server with invalid group_replication_group_name results in crash.

How to repeat:
./bin/mysqld --no-defaults --datadir=$PWD/d0 --basedir=$PWD --initialize-insecure

./bin/mysqld --no-defaults --basedir=$PWD --datadir=$PWD/d0 --socket=/tmp/mysql.0.sock --log-bin=mysql-bin-1.log --server_id=1 --port=3308  --enforce-gtid-consistency --log-slave-updates --gtid-mode=on --transaction-write-set-extraction=XXHASH64 --binlog-checksum=NONE --master-info-repository=TABLE --relay_log_info_repository=TABLE --plugin-dir=lib/plugin/ --plugin-load=group_replication.so --relay-log-recovery=on --general_log=on --group_replication_group_name="" --group_replication_local_address="localhost:10301" --group_replication_group_seeds="localhost:10301,localhost:10302,localhost:10303,localhost:10304,localhost:10305" --group_replication_start_on_boot=1 --group_replication_bootstrap_group=1 --group_replication_single_primary_mode=TRUE --group_replication_enforce_update_everywhere_checks=FALSE 2>&1 | tee ./d0/serv1.err
[9 Aug 2018 13:08] David Moss 
Posted by developer:
 
Thank you for your feedback, this has been fixed in upcoming versions and the following was added to the 8.0.13 changelog:
If Group Replication was started on server with an invalid <literal role="sysvar">group_replication_group_name</literal>, the server would stop unexpectedly.