Description:
A previous clone shows:
root@myhost [(none)]> select NOW();
+---------------------+
| NOW() |
+---------------------+
| 2021-10-21 16:55:41 |
+---------------------+
1 row in set (0.00 sec)
root@myhost [(none)]> select * from performance_schema.clone_status;
--
| ID | PID | STATE | BEGIN_TIME | END_TIME | SOURCE | DESTINATION | ERROR_NO | ERROR_MESSAGE | BINLOG_FILE | BINLOG_POSITION | GTID_EXECUTED|
--
| 1 | 0 | Completed | 2021-06-29 19:22:59.155 | 2021-06-30 00:46:19.457
So it took place 3 months ago. I'm debugging a clone issue and would like to know more information about this clone but it's not available.
Precisely I'd like to know:
- hostname
- port
- version of source
- data bytes
- network copy bytes
All of this information would be very helpful because the current server version may be different and because it provides a much better "audit trail". Most of the time you don't need this but sometimes it really helps.
How to repeat:
Have an issue cloning and you want to check the status of the source (not the target) just to get an idea of "where it came from". This information (above) would help.
Suggested fix:
Provide the additional information requested.
Ideally you could APPEND a row on the target if the source had such data. Then you'd get a clone history.
The only thing that to me looks completely broken is having a table with "state" in the performance_schema database which is not supposed to have stateful information... Location of this information does not matter but having it does.
