Description:
We hit the issue when setting up replication after running clone. We will use the performance_schema.clone_status table to set up replication after the clone finishes. The gtid_executed field will be used when setting up replication. However, this field has a size limit. For gtid_executed that is larger than the size limit, it will be truncated. So we don't have the full gtid_executed to set up replication, which will lead to a setup failure.

How to repeat:
Run > CLONE INSTANCE FROM 'user'@'host':port identified by '' require ssl;
(The donor should have a large gtid_executed)

Check the performance_schema.clone_status.gtid_executed field. It only has part of the gtid_executed information compared with donor.

Hello Chun Ni,

Thank you for the report and feedback.

regards,
Umesh

Documented fix as follows in the MySQL 8.0.34 and 8.1.0 changelogs:

    The type used for the Performance Schema clone_status table's
    gtid_executed column has been changed from VARCHAR(4096) to
    LONGTEXT.

Closed.