LP #1570682: Parallel doublewrite buffer file created when skip-innodb_doublewrite is set
General
Escalation
General
Escalation
Description
Environment
None
Smart Checklist
Activity
Show:
Vy Nguyen Tan September 4, 2019 at 8:59 AM
This bug is still occurring on PS 5.7.27-30.
innodb_doublewrite=OFF.
Lalit Choudhary February 26, 2019 at 5:11 PM
Also reproduciable with PS 8.0.13
log_error_verbosity=3
innodb_doublewrite= OFF
2019-02-26T17:10:30.536392Z 1 [Note] [MY-011825] [InnoDB] Crash recovery did not find the parallel doublewrite buffer at /home/lalit/sandboxes/msb_8_0_13/data/xb_doublewrite
Laurynas Biveinis February 26, 2019 at 2:01 PM
@Lalit Choudhary what is 8.0 status?
Lalit Choudhary February 20, 2019 at 8:30 AM
Hi Sean,
Thank you for the report.
Validated as described against PS 5.7.24-28
Done
Details
Details
Assignee
Kamil Holubicki
Kamil HolubickiReporter
lpjirasync
lpjirasync(Deactivated)Time tracking
2d 59m logged
Priority
LowSmart Checklist
Open Smart Checklist
Smart Checklist
Open Smart Checklist
Created January 24, 2018 at 9:17 AM
Updated March 6, 2024 at 1:56 PM
Resolved September 23, 2019 at 6:23 PM
**Reported in Launchpad by Sean last update 04-05-2016 10:05:05
I use Percona on top of ZFS, so I disable the doublewrite buffer since it's redundant and unnecessary. I do this with skip-innodb_doublewrite in /etc/mysql/my.cnf.
The new Percona 5.7.11-4 has added the new parallel doublewrite buffer feature and according to the log file (next line), this new buffer is being created.
[Note] InnoDB: Created parallel doublewrite buffer at /var/lib/mysql/xb_doublewrite, size 31457280 bytes
I don't think it's actually being used, since an "ls -l" in /var/lib/mysql shows a stale "last updated" timestamp for the xb_doublewrite file.
But it should not be created at all if doublewrites are disabled.