Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
As issue described in PXB-1920 case when a backup runs, there is a delay between the following two log items, with no log entry for what it's doing:
190822 00:39:09 Added plugin 'keyring_file.so' to load list. 190822 01:26:27 >> log scanned up to (5174996846993)
you can see here it took almost 50 minutes
Here the user expectation is, the backup log should print progress message in regular intervals so users will know what's the current stage and what it's exactly happening at that time.
Example:
190822 00:39:09 Added plugin 'keyring_file.so' to load list.
-- at this timestamp it's done working on plugins, and should log something like 'starting processing of X...' or whatever, showing what it's doing, especially as it's a potentially very long process.
-- in the middle, progress updates are good, but not strictly necessary
-- then 'completed processing of X' down here by 01:26 to show it finished that step, and that X was what took over 45 minutes.
190822 01:26:27 >> log scanned up to (5174996846993)
-- these are the next log entries (and come rapidly) as in this case data copy started at 01:26:27. the log updates regularly after that, and while a progress % would be nice like you mentioned, it's not critical here. once this bit starts it's pretty clear what's happening until the backup completes.
It appears that this issue is no longer being worked on, so we are closing it for housekeeping purposes. If you believe the issue still exists, please open a new ticket after confirming it's present in the latest release.
Sergei Glushchenko August 30, 2019 at 3:17 PM
Xtrabackup is copying redo log. User probably has large log file size and/or using throttle. Xtrabackup prints log scanned message once it has caught up with the server's current LSN. Once xtrabackup completed initial redo log copying it starts copying of the data files. It is possible to print log scanned message at fixed time or LSN intervals.
As issue described in PXB-1920 case when a backup runs, there is a delay between the following two log items, with no log entry for what it's doing:
190822 00:39:09 Added plugin 'keyring_file.so' to load list.
190822 01:26:27 >> log scanned up to (5174996846993)
you can see here it took almost 50 minutes
Here the user expectation is, the backup log should print progress message in regular intervals so users will know what's the current stage and what it's exactly happening at that time.
Example:
190822 00:39:09 Added plugin 'keyring_file.so' to load list. -- at this timestamp it's done working on plugins, and should log something like 'starting processing of X...' or whatever, showing what it's doing, especially as it's a potentially very long process. -- in the middle, progress updates are good, but not strictly necessary -- then 'completed processing of X' down here by 01:26 to show it finished that step, and that X was what took over 45 minutes. 190822 01:26:27 >> log scanned up to (5174996846993) -- these are the next log entries (and come rapidly) as in this case data copy started at 01:26:27. the log updates regularly after that, and while a progress % would be nice like you mentioned, it's not critical here. once this bit starts it's pretty clear what's happening until the backup completes.Incubator item
PXB progress of backup process in logs