2019-08-14T03:01:52.690466-05:00 7992 [Note] Plugin group_replication reported: 'Group Replication applier module successfully initialized!'
2019-08-14T03:01:52.691143-05:00 0 [Note] Plugin group_replication reported: 'XCom protocol version: 3'
2019-08-14T03:01:52.691173-05:00 0 [Note] Plugin group_replication reported: 'XCom initialized and ready to accept incoming connections on port 21317'
2019-08-14T03:01:52.694865-05:00 0 [ERROR] Plugin group_replication reported: '[GCS] Error on opening a connection to m1:49106 on local port: 21317.'
2019-08-14T03:01:52.695250-05:00 0 [ERROR] Plugin group_replication reported: '[GCS] Error on opening a connection to m3:17662 on local port: 21317.'
2019-08-14T03:01:52.695584-05:00 0 [ERROR] Plugin group_replication reported: '[GCS] Error on opening a connection to m4:32087 on local port: 21317.'
2019-08-14T03:01:52.702251-05:00 0 [ERROR] Plugin group_replication reported: '[GCS] Error on opening a connection to m4:32087 on local port: 21317.'
2019-08-14T03:01:52.702264-05:00 0 [ERROR] Plugin group_replication reported: '[GCS] Error connecting to all peers. Member join failed. Local port: 21317'
2019-08-14T03:01:52.715162-05:00 0 [Warning] Plugin group_replication reported: 'read failed'
2019-08-14T03:01:52.718383-05:00 0 [ERROR] Plugin group_replication reported: '[GCS] The member was unable to join the group. Local port: 21317'
2019-08-14T03:02:52.692643-05:00 7992 [ERROR] Plugin group_replication reported: 'Timeout on wait for view after joining group'
2019-08-14T03:02:52.692734-05:00 7992 [Note] Plugin group_replication reported: 'Requesting to leave the group despite of not being a member'
2019-08-14T03:02:52.692751-05:00 7992 [ERROR] Plugin group_replication reported: '[GCS] The member is leaving a group without being on one.'
2019-08-14T03:02:52.692965-05:00 9584 [Note] Error reading relay log event for channel 'group_replication_applier': slave SQL thread was killed
2019-08-14T03:02:52.693671-05:00 9584 [Note] Slave SQL thread for channel 'group_replication_applier' exiting, replication stopped in log 'FIRST' at position 0
2019-08-14T03:02:52.701523-05:00 9581 [Note] Plugin group_replication reported: 'The group replication applier thread was killed'
解决方法：
初步判定是Local port: 21317 端口，无法开启问题。通过重启mysql解决此类问题
service mysqld restart
root@localhost03:25:13[(none)]>start group_replication ;
Query OK, 0 rows affected (3.15 sec)
root@localhost03:25:32[(none)]>SELECT * FROM performance_schema.replication_group_members
-> ;
+---------------------------+--------------------------------------+-------------+-------------+--------------+
| CHANNEL_NAME | MEMBER_ID | MEMBER_HOST | MEMBER_PORT | MEMBER_STATE |
+---------------------------+--------------------------------------+-------------+-------------+--------------+
| group_replication_applier | 360bfb62-db39-11e8-b641-000c29beb141 | m1 | 13306 | ONLINE |
| group_replication_applier | 360bfb62-db39-11e8-b641-000c29beb142 | m2 | 13306 | ONLINE |
| group_replication_applier | 360bfb62-db39-11e8-b641-000c29beb143 | m3 | 13306 | ONLINE |
+---------------------------+--------------------------------------+-------------+-------------+--------------+
类似问题2：
同事也遇到类似的Xcom通信不通问题，经常逐一判断，最终定位是loose-group_replication_group_name每个节点一样，导致的。
