MySQL Bugs: #109580: Timeout on wait for view after joining group

Bug #109580	Timeout on wait for view after joining group
Submitted:	11 Jan 2023 8:02	Modified:	11 Jan 2023 13:25
Reporter:	zetang zeng	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server: Group Replication	Severity:	S3 (Non-critical)
Version:	5.7.40	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
Deploy three nodes cluster and restart all three nodes at the same time (use ansible like tool), all nodes report log like following and can not auto recover. 

2023-01-11T03:41:27.393871Z 0 [ERROR] Plugin group_replication reported: '[GCS] Error on opening a connection to 10.0.0.253:34061 on local port: 34061.'
2023-01-11T03:41:27.393982Z 0 [ERROR] Plugin group_replication reported: '[GCS] Error on opening a connection to 10.0.0.254:34061 on local port: 34061.'
2023-01-11T03:41:27.393989Z 0 [ERROR] Plugin group_replication reported: '[GCS] Error connecting to all peers. Member join failed. Local port: 34061'
2023-01-11T03:41:27.394130Z 0 [Warning] Plugin group_replication reported: 'read failed'
2023-01-11T03:41:27.399035Z 0 [ERROR] Plugin group_replication reported: '[GCS] The member was unable to join the group. Local port: 34061'
2023-01-11T03:41:43.808426Z 105 [Note] Got an error reading communication packets
2023-01-11T03:42:13.809204Z 286 [Note] Got an error reading communication packets
2023-01-11T03:42:27.371795Z 2 [ERROR] Plugin group_replication reported: 'Timeout on wait for view after joining group'
2023-01-11T03:42:27.371820Z 2 [Note] Plugin group_replication reported: 'Requesting to leave the group despite of not being a member'
2023-01-11T03:42:27.371830Z 2 [ERROR] Plugin group_replication reported: '[GCS] The member is leaving a group without being on one.'

How to repeat:
Deploy three nodes cluster and restart all three nodes at the same time (use ansible like tool)

Suggested fix:
MySQL cluster can auto recover.

Hi Mr. zeng,

Thank you for your bug report.

However, this is not a bug.

You have to have your entire network setup properly for the use of the InnoDB Cluster. If there are problems found in connecting to the ports on specific IP addresses, it is a job for your system administrator.

Next, we do not support Ansible ......

Not a bug.

Sorry that I didn't make it clear. 

The first thing is the network is fine.WHEN THE cluster is deployed, All is fine. After we start three instances at the same time the error show.

The second thing is this bug is not related with ansible.  I mentioned it just because it can restart all three instances at the same time conveniently. You can reproduce it by  Opening three terminal And enter `systemctl restart mysqld` at the same time to get the same situation.