Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
None
Description
Since MDEV-23855 InnoDB can do checkpoints much more rarely. This improves performance under write-heavy load, but makes mariadb-backup create huge incremental backups (since the last checkpoint).
One way to solve it would be to let mariadb-backup to force an InnoDB checkpoint before a backup. There are many ways of doing it, innodb.page_cleaner test shows one of them, marko knows more. Perhaps it should be optional, but, likely, enabled by default.
Alternatively, InnoDB can force a checkpoint automatically when entering a certain backup stage.
Attachments
Issue Links
- relates to
-
MDEV-24537 innodb_max_dirty_pages_pct_lwm=0 lost its special meaning
-
- Closed
-
-
MDEV-24949 Enabling idle flushing (possible regression from MDEV-23855)
-
- Closed
-
-
MDEV-26626 InnoDB fails to advance the log checkpoint
-
- Closed
-
-
MDEV-34062 mariadb-backup --backup is extremely slow at copying ib_logfile0
-
- Closed
-
-
MDEV-31410 mariadb-backup prepare crash with InnoDB: Missing FILE_CREATE, FILE_DELETE or FILE_MODIFY before FILE_CHECKPOINT
-
- Closed
-
-
MDEV-31446 mariabackup loop on Read redo log up to LSN
-
- Open
-
-
MDEV-33838 Data still present in backup / on disk after table delete or/and import from sql
-
- Open
-
-
MDEV-35298 Issues with --extra-lsndir in MariaDB Incremental Backups Not Updating LSN as Expected
-
- Open
-
-
MDEV-35791 mariadb-backup 10.11.10 failed to create backup
-
- Closed
-
-
MDEV-36159 mariabackup failed after upgrade 10.11.10
-
- Stalled
-
-
MDEV-36254 Document MDEV-30000: make mariadb-backup force an innodb checkpoint
-
- Open
-
-
MDEV-36270 mariabackup.incremental_compressed fails in 10.11+
-
- Closed
-
- links to
Activity
Transition | Time In Source Status | Execution Times |
---|
|
44m 19s | 1 |
|
75d 9h 42m | 2 |
|
129d 23h 24m | 3 |
|
564d 8h 16m | 2 |
|
74d 1h 27m | 2 |
|
4h 23m | 1 |
|
3d 1h 54m | 1 |
|
22m 35s | 1 |
|
2d 16h 14m | 1 |