Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
10.6, 10.11, 11.4, 11.8, 12.0(EOL)
-
None
-
Not for Release Notes
Description
mariadb-backup creates one background thread to copy innodb redo log.
It does copy all the data file (in main thread and other concurrent threads),
till it explicitly mentions the redo log thread to exit. This redo log copier thread run
keep printing the current states of redo log copied lsn for every 15 seconds.
If BACKUP STAGE command takes time to finish or any stall
during data copy then redo log background continuously emitting the same log copy status
gives the impression that redo log is hanging or stuck
2025-05-30 0:30:38 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:30:53 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:31:08 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:31:23 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:31:38 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:31:53 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:32:08 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:32:23 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:32:38 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:32:53 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:33:08 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:33:23 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:33:38 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:33:53 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:34:08 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:34:23 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:34:38 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:34:53 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:35:08 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:35:23 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:35:38 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:35:53 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:36:08 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:36:23 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:36:38 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:36:53 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:37:08 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:37:23 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:37:38 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:37:53 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:38:08 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:38:23 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:38:38 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:38:53 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
2025-05-30 0:39:08 0 [Note] InnoDB: Read redo log up to LSN=18703453696
|
Attachments
Issue Links
- is blocked by
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-