Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5, 10.6, 10.11, 11.4
Description
In mariadb-backup --backup there are multiple mechanisms for ensuring that a sufficient amount of the InnoDB write-ahead log (ib_logfile0) is being copied at the end of the backup.
There is a function backup_wait_for_lsn(), which will wait for the log_copying_thread() to copy a necessary amount. But, we fail to pass the target LSN to log_copying_thread() itself.
The log copying and recovery logic was rewritten in MDEV-14425 and some locking in backup was rewritten in MDEV-32932. Therefore, it is not trivial to apply this fix to earlier versions.
Attachments
Issue Links
- relates to
-
MDEV-34871 BACKUP STAGE BLOCK_COMMIT had better return an InnoDB LSN
-
- Open
-
-
MDEV-14425 Change the InnoDB redo log format to reduce write amplification
-
- Closed
-
-
MDEV-32932 port backup features from MariaDB Enterprise
-
- Closed
-
Activity
Transition | Time In Source Status | Execution Times |
---|
|
4m 42s | 1 |
|
7h 12m | 1 |
|
1d 20h 51m | 2 |
|
14d 21h 38m | 1 |
|
51d 23h 26m | 3 |
|
1m 55s | 1 |
|
4d 5h 56m | 1 |
|
54m 4s | 1 |