Bug #90601 REPORT_HOST OPTION HAS A LIMIT OF 60 CHARACTERS
Submitted: 24 Apr 2018 10:47 Modified: 16 Apr 2019 18:19
Reporter: Andrew Pryde Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Replication Severity:S3 (Non-critical)
Version:8.0.11 OS:Oracle Linux (Offical Docker image)
Assigned to: CPU Architecture:Any

[24 Apr 2018 10:47] Andrew Pryde 
Description:
Creating an InnoDB GR cluster (via mysqlsh) fails when --report-host exceeds a certain length (likely 61 characters).

2018-04-24T09:53:15.421444Z 18 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Translated 'mysql-cluster-with-3-replicas-0.mysql-cluster-with-3-replicas.apryde' to 172.17.0.2'
2018-04-24T09:53:15.422470Z 18 [Warning] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Automatically adding IPv4 localhost address to the whitelist. It is mandatory that it is added.'
2018-04-24T09:53:15.424506Z 18 [Note] [MY-011694] [Repl] Plugin group_replication reported: 'Initialized group communication with configuration: group_replication_group_name: '4ee2bd0a-47a5-11e8-b8d2-0242ac110002'; group_replication_local_address: 'mysql-cluster-with-3-replicas-0.mysql-cluster-with-3-replicas.apryde:33061'; group_replication_group_seeds: ''; group_replication_bootstrap_group: 'true'; group_replication_poll_spin_loops: 0; group_replication_compression_threshold: 1000000; group_replication_ip_whitelist: '0.0.0.0/0'; group_replication_communication_debug_options: 'GCS_DEBUG_NONE''
2018-04-24T09:53:15.424773Z 18 [Note] [MY-011643] [Repl] Plugin group_replication reported: 'Member configuration: member_id: 1000; member_uuid: "437195f2-47a5-11e8-a38f-0242ac110002"; single-primary mode: "true"; group_replication_auto_increment_increment: 7; '
2018-04-24T09:53:15.495189Z 20 [System] [MY-010597] [Repl] 'CHANGE MASTER TO FOR CHANNEL 'group_replication_applier' executed'. Previous state master_host='', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='<NULL>', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''.
2018-04-24T09:53:15.530311Z 23 [Note] [MY-010581] [Repl] Slave SQL thread for channel 'group_replication_applier' initialized, starting replication in log 'FIRST' at position 0, relay log './mysql-cluster-with-3-replicas-0-relay-bin-group_replication_applier.000001' position: 4
2018-04-24T09:53:15.531694Z 18 [Note] [MY-011670] [Repl] Plugin group_replication reported: 'Group Replication applier module successfully initialized!'
2018-04-24T09:53:15.581373Z 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] XCom protocol version: 3'
2018-04-24T09:53:15.581483Z 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] XCom initialized and ready to accept incoming connections on port 33061'
2018-04-24T09:53:15.770963Z 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Creating new server node 0 host mysql-cluster-with-3-replicas-0.mysql-cluster-with-3-replicas.apryde'
2018-04-24T09:53:15.772243Z 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Installed site start={9f9090c7 0 0} boot_key={9f9090c7 0 0} node 4294967295'
2018-04-24T09:54:15.531852Z 18 [ERROR] [MY-011640] [Repl] Plugin group_replication reported: 'Timeout on wait for view after joining group'
2018-04-24T09:54:15.531952Z 18 [Note] [MY-011649] [Repl] Plugin group_replication reported: 'Requesting to leave the group despite of not being a member'
2018-04-24T09:54:15.531985Z 18 [ERROR] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] The member is leaving a group without being on one.'

2018-04-24T10:01:00.841466Z 18 [Note] [MY-011716] [Repl] Plugin group_replication reported: 'Current debug options are: 'GCS_DEBUG_NONE'.'
2018-04-24T10:01:00.843022Z 18 [Note] [MY-011671] [Repl] Plugin group_replication reported: 'Group communication SSL configuration: group_replication_ssl_mode: "REQUIRED"; server_key_file: "server-key.pem"; server_cert_file: "server-cert.pem"; client_key_file: "server-key.pem"; client_cert_file: "server-cert.pem"; ca_file: "ca.pem"; ca_path: ""; cipher: ""; tls_version: "TLSv1,TLSv1.1,TLSv1.2"; crl_file: ""; crl_path: ""; ssl_fips_mode: "OFF"'
2018-04-24T10:01:00.844041Z 18 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Debug messages will be sent to: asynchronous::/var/lib/mysql/GCS_DEBUG_TRACE'
2018-04-24T10:01:00.847413Z 18 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Translated 'm-0.m.apryde' to 172.17.0.2'
2018-04-24T10:01:00.849051Z 18 [Warning] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Automatically adding IPv4 localhost address to the whitelist. It is mandatory that it is added.'
2018-04-24T10:01:00.850453Z 18 [Note] [MY-011694] [Repl] Plugin group_replication reported: 'Initialized group communication with configuration: group_replication_group_name: '6450b65e-47a6-11e8-acc5-0242ac110002'; group_replication_local_address: 'm-0.m.apryde:33061'; group_replication_group_seeds: ''; group_replication_bootstrap_group: 'true'; group_replication_poll_spin_loops: 0; group_replication_compression_threshold: 1000000; group_replication_ip_whitelist: '0.0.0.0/0'; group_replication_communication_debug_options: 'GCS_DEBUG_NONE''
2018-04-24T10:01:00.850776Z 18 [Note] [MY-011643] [Repl] Plugin group_replication reported: 'Member configuration: member_id: 1000; member_uuid: "58f3b6f7-47a6-11e8-95a8-0242ac110002"; single-primary mode: "true"; group_replication_auto_increment_increment: 7; '
2018-04-24T10:01:00.876675Z 20 [System] [MY-010597] [Repl] 'CHANGE MASTER TO FOR CHANNEL 'group_replication_applier' executed'. Previous state master_host='', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='<NULL>', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''.
2018-04-24T10:01:00.899354Z 18 [Note] [MY-011670] [Repl] Plugin group_replication reported: 'Group Replication applier module successfully initialized!'
2018-04-24T10:01:00.899486Z 23 [Note] [MY-010581] [Repl] Slave SQL thread for channel 'group_replication_applier' initialized, starting replication in log 'FIRST' at position 0, relay log './m-0-relay-bin-group_replication_applier.000001' position: 4
2018-04-24T10:01:01.004112Z 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] XCom protocol version: 3'
2018-04-24T10:01:01.004150Z 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] XCom initialized and ready to accept incoming connections on port 33061'
2018-04-24T10:01:01.122993Z 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Creating new server node 0 host m-0.m.apryde'
2018-04-24T10:01:01.124063Z 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Installed site start={bc9db74a 0 0} boot_key={bc9db74a 0 0} node 0'
2018-04-24T10:01:01.125495Z 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Re-using server node 0 host m-0.m.apryde'
2018-04-24T10:01:01.125702Z 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Installed site start={bc9db74a 1 0} boot_key={bc9db74a 1 0} node 0'
2018-04-24T10:01:04.127729Z 26 [Note] [MY-011623] [Repl] Plugin group_replication reported: 'Only one server alive. Declaring this server as online within the replication group'
2018-04-24T10:01:05.128590Z 0 [Note] [MY-011503] [Repl] Plugin group_replication reported: 'Group membership changed to m-0.m.apryde:3306 on view 15245640631259426:1.'
2018-04-24T10:01:05.129067Z 0 [Note] [MY-011490] [Repl] Plugin group_replication reported: 'This server was declared online within the replication group.'
2018-04-24T10:01:05.129540Z 0 [Note] [MY-011507] [Repl] Plugin group_replication reported: 'A new primary with address m-0.m.apryde:3306 was elected, enabling conflict detection until the new primary applies all relay logs.'
2018-04-24T10:01:05.130066Z 0 [Note] [MY-011510] [Repl] Plugin group_replication reported: 'This server is working as primary member.'
2018-04-24T10:01:06.130964Z 20 [Note] [MY-011485] [Repl] Plugin group_replication reported: 'Primary had applied all relay logs, disabled conflict detection.'

How to repeat:
Run mysql-server --report-host set to a long fully qualified domain name and then run dba.create_cluster('MySQLCluster') in mysqlsh.

Suggested fix:
Pottentially a result of: https://github.com/mysql/mysql-server/blob/8.0/sql/sql_const.h#L49
[25 Apr 2018 15:16] MySQL Verification Team 
Hi,

Thanks for the report! Verified.

all best
Bogdan
[8 Apr 2019 8:08] Gopal Shankar 
Posted by developer:
 
Fixed in wl#12571.
[16 Apr 2019 18:18] Paul DuBois 
Posted by developer:
 
Fixed in 8.0.17.

The maximum permitted length of host names throughout MySQL has been
raised to 255 ASCII characters, up from the previous limit of 60
characters. This applies to, for example, host name-related columns
in the data dictionary, mysql system schema, Performance Schema,
INFORMATION_SCHEMA, and sys schema; the MASTER_HOST value for the
CHANGE MASTER TO statement; the Host column in SHOW PROCESSLIST
statement output; host names in account names (such as used in
account-management statements and in DEFINER attributes); and host
name-related command options and system variables.

Applications that expect host names to be a maximum of 60 characters
should be adjusted to account for this change.
[30 Nov 2021 13:19] MySQL Verification Team 
Bug #87243 marked as duplicate of this one