create --progress capability
General
Escalation
General
Escalation
Description
Environment
None
Activity
Show:
Julia Vural 7 hours ago
With the reduced lock feature it is not as essential to see the progress of backup.
On the other hand, it is still a good feature to have so that people can see if it is stuck or not.
We can track current progress of backup to be consumed by external tools, such as pmm/dbaas backup manager .
This can be used with --history to link the ID of the history with the ID of the progress table.
high level idea is to validate how much data we need to copy at the start of the backup and keep an atomic counter of the amount of data we already copied.
Redo log should be excluded as we will reach 100% once we copied the last non-innodb file.
Check if page-tracking can give us an precise estimation based on number of pages * page_size.
With regards to redo log ( we can keep track the amount of redo log copied based on LSN. LSN at the start of backup and current LSN is the amount of data we copied on redo)