Bug #111626 The MGR configuration is partially incorrect as expected

• Submitted: 30 Jun 2023 7:09
• Modified: 30 Jun 2023 13:26
• Reporter: huichao chen
• Status: Can't repeat
• Category: MySQL Server
• Severity: S3 (Non-critical)
• Version: 8.0.23-commercial
• OS: Any
• Assigned to: MySQL Verification Team
• CPU Architecture: Any
• Tags: config, mgr

[30 Jun 2023 7:09] huichao chen

Description:
I have two IDC rooms. Room A is a formal environment and Room B is a Dr Environment

The MGR cluster in equipment room A is running properly. After the MGR active node instance in Equipment room B is started, the parameters of the group_rep1ication_group_name and group_replication_local address variables are inconsistent with those set in the configuration file

my profile information
~~~
loose-group_rep1ication_group_name='5t79d556-44dc-aabb-07bf61930fee'
loose-group_replication_local_address="192.168.0.18:24901"
~~~

instance variable information 
~~~
loose-group_rep1ication_group_name     adcc60f5-0ff6-11ee-b452-525421414eac
loose-group_replication_local_address  192.168.0.18:33061
~~~

However, after I deleted the auto.cnf file in the datadir directory and restarted the instance, the variable obtained the same value as in the configuration file

I checked the following information
1. The configuration file read is correct
2. The performance_schema.persisted_variables table does not set relevant parameter information
3. Log no error

How to repeat:
The instance in equipment room B is set up by using clone A

after I deleted the auto.cnf file in the datadir directory and restarted the instance, the variable obtained the same value as in the configuration file

[30 Jun 2023 13:26] MySQL Verification Team

Hi Mr. chen,

Thank you for your bug report.

First of all, your release is too old and is not supported any more.

Second and more important, this is. a forum for the fully repeatable test cases that demonstrate a bug.

Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.mysql.com/how-to-report.php 

If you can provide more information, feel free to add it to this bug and change the status back to 'Open'.  

Thank you for your interest in MySQL.