Distributed Recovery connection as one of a number of distributed recovery endpoints, you must include it explicitly in the list specified by  group_replication_advertise_recovery_endpoints . You can put it in the last place so that it acts as a last resort for connection. A group member’s distributed recovery endpoints (or standard SQL client connection if endpoints are not provided) do not need to be added to the Group Replication allowlist specified by the  group_replication_ip_allowlist  (from MySQL 8.0.22) or group_replication_ip_whitelist  system variable. The allowlist is only for the address specified by  group_replication_local_address  for each member. A joining member must have its initial connection to the group permitted by the allowlist in order to retrieve the address or addresses for distributed recovery. The distributed recovery endpoints that you list are validated when the system variable is set and when a  START GROUP_REPLICATION  statement has been issued. If the list cannot be parsed correctly, or if any of the endpoints cannot be accessed on the host because the server is not listening on them, Group Replication logs an error and does not start. From MySQL 8.0.18, you can optionally configure compression for distributed recovery by the method of state transfer from a donor’s binary log. Compression can benefit distributed recovery where network bandwidth is limited and the donor has to transfer many transactions to the joining member. The  group_replication_recovery_compression_algorithms  and group_replication_recovery_zstd_compression_level  system variables configure permitted compression algorithms, and the  zstd  compression level, used when carrying out state transfer from a donor’s binary log. For more information, see Section 4.2.8, “Connection Compression Control” . Note that these compression settings do not apply for remote cloning operations. When a remote cloning operation is used for distributed recovery, the clone plugin’s  clone_enable_compression  setting applies. Compression for Distributed Recovery Replication User for Distributed Recovery SSL and Authentication for Distributed Recovery Distributed recovery requires a replication user that has the correct permissions so that Group Replication can establish direct member-to-member replication channels. The replication user must also have the correct permissions to act as the clone user on the donor for a remote cloning operation. The same replication user must be used for distributed recovery on every group member. For instructions to set up this replication user, see Section 18.2.1.3, “User Credentials For Distributed Recovery” . For instructions to secure the replication user credentials, see Section 18.6.3.1, “Secure User Credentials for Distributed Recovery” . SSL for distributed recovery is configured separately from SSL for normal group communications, which is determined by the server’s SSL settings and the  group_replication_ssl_mode  system variable. For distributed recovery connections, dedicated Group Replication distributed recovery SSL system variables are available to configure the use of certificates and ciphers specifically for distributed recovery. By default, SSL is not used for distributed recovery connections. To activate it, set group_replication_recovery_use_ssl=ON , and configure the Group Replication distributed recovery SSL system variables as described in Section 18.6.3, “Securing Distributed Recovery Connections” . You need a replication user that is set up to use SSL. When distributed recovery is configured to use SSL, Group Replication applies this setting for remote cloning operations, as well as for state transfer from a donor’s binary log. Group Replication 3739