Home > database >  Create a mysql InnoDB Cluster times wrong
Create a mysql InnoDB Cluster times wrong

Time:09-26

2018-01-18 T09: earth. 838659 z 21 [Note] the Plugin group_replication reported: 'the Initialized group communication with configuration: group_replication_group_name: "five cb78d58 - fc31 e7-906 - d - 000-11 c29a9ffd8"; Group_replication_local_address: "centos55:13306"; Group_replication_group_seeds: ""; Group_replication_bootstrap_group: true, Group_replication_poll_spin_loops: 0; Group_replication_compression_threshold: 1000000; Group_replication_ip_whitelist: "AUTOMATIC" '
The 2018-01-18 T09: earth. 838735 z 21 [Note] the Plugin group_replication reported: 'Member configuration: member_id: 819131035; "9 c1ac59d member_uuid: - e7 - a4a7 fc2f - 11-000 c29a9ffd8"; Single - primary mode: "true"; Group_replication_auto_increment_increment: 7; '
The 2018-01-18 T09: earth. 839071 z 23 [Note] the Plugin group_replication reported: 'Detected previous RESET MASTER invocation or an issue exists in the group, the replication applier relay the Purging existing applier logs.'
The 2018-01-18 T09: earth. 957541 z 23 [Note] 'CHANGE the MASTER TO the FOR CHANNEL' group_replication_applier 'executed. The Previous state master_host=', master_port=3306, master_log_file=', master_log_pos=4, master_bind="'. The New state master_host='& lt; NULL>=' ' ', master_port=0, master_log_file, master_log_pos=4, master_bind='. '
The T09:2018-01-18 reels. 131648 z 26 [Note] Slave SQL thread for channel 'group_replication_applier' the initialized, starting replication in the log 'FIRST' at position 0, relay log './centos55 - relay - bin - group_replication_applier. 000001 'position: 4
The T09:2018-01-18 reels. 133135 z 21 [Note] the Plugin group_replication reported: 'Group, the Replication applier module successfully initialized. '
The T09:2018-01-18 reels. The 133332 z 0 [Note] the Plugin group_replication reported: 'the state 4338 action xa_init'
The T09:2018-01-18 reels. The 133652 z 0 [Note] the Plugin group_replication reported: 'Unable to bind to 0.0.0.0:13306 (socket=89, errno=13)! '
T09:2018-01-18 reels. The 133737 z 0 [ERROR] Plugin group_replication reported: 'Unable to announce the TCP port 13306. The port already in use? '
The T09:2018-01-18 reels. The 134260 z 0 [ERROR] Plugin group_replication reported: '(GCS) ERROR joining the group, while waiting for the network layer to become ready.'

The T09:2018-01-18 reels. The 134299 z 0 [Note] the Plugin group_replication reported: 'the state 4338 action xa_exit'
The T09:2018-01-18 reels. The 134465 z 0 [Note] the Plugin group_replication reported: 'Exiting xcom thread'
The T09:2018-01-18 reels. The 134498 z 0 [ERROR] Plugin group_replication reported: '(GCS) The member was unable to join The group. The Local port: 13306'

I am sure that no process occupies 13306 port

CodePudding user response:

Recommend a kick-ass tidb distributed database compatible with mysql protocol

CodePudding user response:

I encountered this problem caused by selinux is not closed
  • Related