Bug #106733 Request to make clone_progress + clone_status tables persistent
Submitted: 15 Mar 9:25
Reporter: Shane Bester (Platinum Quality Contributor) Email Updates:
Status: Verified Impact on me:
Category:MySQL Server: Clone Plugin Severity:S4 (Feature request)
Version:8.0.28 OS:Any
Assigned to: CPU Architecture:Any

[15 Mar 9:25] Shane Bester
It would be useful if performance_schema tables for clone plugin could be persisted across restarts.   That will be convenient to provide a history of clones.

Since clone_progress is typically only available on the recipient whose dataset is wiped out on each clone, this means the persisted data needs to be kept on the Donor server.

Also provide the Donor/recipient versions in the clone_status table.

How to repeat:
[15 Mar 9:26] MySQL Verification Team
[16 Mar 9:46] Simon Mudd
I'm not entirely sure of your analysis.
On the recipient we need the information of the new clone that took place. That server may be replaced and thus the history lost, but if this server is promoted to being a master/primary then other systems may be copied from it so the history is needed locally and any new cloned servers from this one will inherit the history of the server they clone from.

So I'm not entirely sure that a history is required on the source.  The information may be useful and some people may not want to keep it or we may want to remove older entries that are no longer of interest.

Certainly adding this information especially if it includes version of the source would be useful as you'll see the upgrade state as MySQL gets upgraded through different versions and have an insight to this information over the whole running cluster.