Details
-
New Feature
-
Status: Stalled (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
The default variable for sync_binlog is 0 for MariaDB, where Oracle changed it to 1 starting with 5.7.7. I think we should also change the default to 1, as running a master with sync_binlog=0 is risky - any crash of server or mysqld will create inconsistent slaves 99% of the time.
Attachments
Issue Links
- is blocked by
-
MDEV-18959 Engine transaction recovery through persistent binlog
-
- Stalled
-
-
MDEV-24386 MDEV-16589 benchmark & analysis
-
- Closed
-
- relates to
-
MDEV-34705 Storing binlog in InnoDB
-
- In Progress
-
1.
|
MDEV-16589 benchmark & analysis |
![]() |
Closed | Axel Schwenke |
Nice graphs sujatha.sivakumar. So 8-16 threads the throughput is higher. Still suffering on latency, particularly insert.
https://mariadb.org/fest2020/ssd/ at 10:48 offset - talking about fsync (redo, but same applies to binlog), that each fsync can be on the same data sector. Aligning every binlog unit to a beginning of a new 4k (discoverable fstat - blksize) block on disk after a fsync acceptable/show gains? And/or piggy back on the io_uring (
MDEV-24883) implementation to have the kernel processing both binlog and other fsyncs for a transaction at the same tiem.