Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2.2
Description
MariaDB 10.2.2 imported MySQL 5.7.9, which introduced separate log files, for server startup to determine if any tables or undo tablespace need "truncate fixup".
There is no logic in Mariabackup to deal with this.
A cleaner solution would be to remove the separate log files and to make the InnoDB redo log self-contained with respect to the truncate operations. This would likely require writing a new redo log record type MLOG_FILE_CREATE that would cause the file to be initialized from the scratch, followed by some page-level redo log records that would initialize the page contents.
This would also remove the need for a redo log checkpoint during the truncate operations.
MDEV-13563 proposes a Mariabackup option that could be used to prevent TRUNCATE TABLE from occurring during backups. It would not prevent undo tablespace truncation from happening.
Attachments
Issue Links
- blocks
-
MDEV-14481 Execute InnoDB crash recovery in the background
- Closed
- causes
-
MDEV-17816 InnoDB: Failing assertion: trx->dict_operation_lock_mode == RW_X_LATCH upon TRUNCATE TABLE after converting to REDUNDANT
- Closed
-
MDEV-17849 Undo tablespace truncation recovery fails to shrink file
- Closed
-
MDEV-17885 TRUNCATE on temporary table causes ER_GET_ERRNO and "Could not remove temporary table" in the log
- Closed
-
MDEV-18836 Race conditions in TRUNCATE TABLE
- Closed
-
MDEV-19449 1030: Got error 168 "Unknown (generic) error from engine" for valid TRUNCATE (temporary) TABLE
- Closed
-
MDEV-21496 Downgrade from current 10.2 to 10.2.19: InnoDB: Failing assertion: trx->dict_operation_lock_mode == RW_X_LATCH
- Closed
-
MDEV-23705 Assertion `table->data_dir_path || !space' failed in row_drop_table_for_mysql on TRUNCATE after DISCARD TABLESPACE
- Closed
-
MDEV-24532 Table corruption ER_NO_SUCH_TABLE_IN_ENGINE or ER_CRASHED_ON_USAGE after ALTER on table with foreign key
- Closed
-
MDEV-26450 Corruption due to innodb_undo_log_truncate
- Closed
- is blocked by
-
MDEV-14717 RENAME TABLE in InnoDB is not crash-safe
- Closed
- is duplicated by
-
MDEV-9459 Truncate table causes innodb stalls
- Closed
- relates to
-
MDEV-9459 Truncate table causes innodb stalls
- Closed
-
MDEV-14585 Automatically remove #sql- tables in innodb dictionary during recovery
- Closed
-
MDEV-16557 Remove INNOBASE_SHARE::idx_trans_tbl
- Closed
-
MDEV-17049 Enable --suite=innodb_undo on buildbot
- Closed
-
MDEV-17138 Reduce redo log volume for undo tablespace initialization
- Closed
-
MDEV-17158 TRUNCATE is not atomic after MDEV-13564
- Closed
-
MDEV-17780 innodb.truncate_recover crashes in recovery due to out-of-bounds page read
- Closed
-
MDEV-17794 Do not assign persistent ID for temporary tables
- Closed
-
MDEV-17831 Assertion `supports_instant()' failed in dict_table_t::prepare_instant upon ADD COLUMN on table with KEY_BLOCK_SIZE
- Closed
-
MDEV-18739 crash (long semaphore wait)
- Closed
-
MDEV-19769 Mariabackup should write warning during backup if server does not have innodb_safe_truncate=ON set
- Open
-
MDEV-22733 XA PREPARE breaks MDL in pseudo_slave_mode=1
- Stalled
-
MDEV-24532 Table corruption ER_NO_SUCH_TABLE_IN_ENGINE or ER_CRASHED_ON_USAGE after ALTER on table with foreign key
- Closed
-
MDEV-25051 Race condition between persistent statistics and RENAME TABLE or TRUNCATE
- Closed
-
MDEV-25710 Dead code os_file_opendir() in the server
- Closed
-
MDEV-33112 innodb_undo_log_truncate=ON is blocking page writes
- Closed
-
MDEV-9459 Truncate table causes innodb stalls
- Closed
-
MDEV-13563 lock DDL for mariabackup in 10.2+
- Closed
-
MDEV-14481 Execute InnoDB crash recovery in the background
- Closed
-
MDEV-14545 Backup fails due to MLOG_INDEX_LOAD record
- Closed
-
MDEV-15154 WSREP: BF lock wait long after a TRUNCATE TABLE
- Closed
-
MDEV-15522 Change galera suite MTR tests to use mariabackup instead of xtrabackup
- Closed
-
MDEV-16306 TRUNCATE waits for metadata lock on the tables when a SELECT is executing on it
- Open
-
MDEV-16465 Invalid (old?) table or database name or hang in ha_innobase::delete_table and log semaphore wait upon concurrent DDL with foreign keys
- Closed
-
MDEV-17043 Purge of indexed virtual columns may cause hang on table-rebuilding DDL
- Closed
-
MDEV-17304 Replace use of XtraBackup with MariaDB Backup
- Closed
-
MDEV-18654 Failing assertion: sym_node->table != NULL in buildbot with innodb_fts.sync_ddl and outside
- Closed
-
MDEV-18960 Assertion `!omits_virtual_cols(*form->s)' failed after upgrade from 10.0/10.1 with PERSISTENT generated column
- Closed