Details
-
New Feature
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
Description
In the current MDEV-34705 binlog_storage_engine=innodb implementation, binary log events are written twice, once to the InnoDB write-ahead log and another time to the page-oriented binary log files. Moving the binary log to be stored in just the innodb_log_archive=ON (MDEV-37949) log would both help improve performance by removing a redundant write, as well as likely other benefits from the reduced complexity of having two separate logs.
We should implement a setting and tools that will allow the binary log events to be stored only inside the innodb_log_archive=ON files using the InnoDB log record format that was introduced in MDEV-34705. In this mode, the page oriented binary log file format that was introduced in MDEV-34705 would continue to exist, but only in a virtual form, not written to any persistent files.
Implementing this would also trivially solve MDEV-8813, because the upgraded tooling would necessarily have to be compatible with the current innodb_encrypt_log=ON format (MDEV-36024).
Attachments
Issue Links
- is blocked by
-
MDEV-37949 Implement innodb_log_archive
-
- Approved
-
- is duplicated by
-
MDEV-39053 Implement an option for binlog inside innodb_log_archive
-
- Closed
-
- relates to
-
MDEV-8813 Allow mysqlbinlog read encrypted binary logs
-
- Open
-
-
MDEV-16589 default value for sync_binlog should be the safer value 1 instead of 0
-
- Stalled
-
-
MDEV-34705 Improving performance of binary logging by removing the need of syncing it
-
- Closed
-