- Partial Write Operations
- innodb_doublewrite - an Imperfect Solution
- Atomic Write - a Faster Alternative to innodb_doublewrite
- Enabling Atomic Writes from MariaDB 10.2
- Enabling Atomic Writes in MariaDB 5.5 to MariaDB 10.1
- Devices Supporting Atomic Writes with MariaDB
Partial Write Operations
When Innodb writes to the filesystem, there is generally no guarantee that a given write operation will be complete (not partial) in cases of a poweroff event, or if the operating system crashes at the exact moment a write is being done.
Without detection or prevention of partial writes, the integrity of the database can be compromised after recovery.
innodb_doublewrite - an Imperfect Solution
Since its inception, Innodb has had a mechanism to detect and ignore partial writes via the InnoDB Doublewrite Buffer (also innodb_checksum can be used to detect a partial write).
Doublewrites, controlled by the innodb_doublewrite system variable, comes with its own set of problems. Especially on SSD, writing each page twice can have detrimental effects (write leveling).
Atomic Write - a Faster Alternative to innodb_doublewrite
A better solution is to directly ask the filesystem to provide an atomic (all or nothing) write guarantee. Currently this is only available on a few SSD cards.
Enabling Atomic Writes from MariaDB 10.2
When starting, MariaDB 10.2 and beyond automatically detects if any of the supported SSD cards are used.
When opening an InnoDB table, there is a check if the tablespace for the table is on a device that supports atomic writes and if yes, it will automatically enable atomic writes for the table. If atomic writes support is not detected, the doublewrite buffer will be used.
One can disable atomic write support for all cards by setting the variable
OFF in your my.cnf file. It's
ON by default.
Enabling Atomic Writes in MariaDB 5.5 to MariaDB 10.1
To use atomic writes instead of the doublewrite buffer, add:
innodb_use_atomic_writes = 1
to the my.cnf config file.
About innodb_use_atomic_writes (in MariaDB 5.5 to MariaDB 10.1)
The following happens when atomic writes are enabled
- if innodb_flush_method is neither
O_DIRECT_NO_FSYNC, it is switched to
- innodb_use_fallocate is switched
ON(files are extended using
posix_fallocaterather than writing zeros behind the end of file)
- Whenever an Innodb datafile is opened, a special
ioctl()is issued to switch on atomic writes. If the call fails, an error is logged and returned to the caller. This means that if the system tablespace is not located on an atomic write capable device or filesystem, InnoDB/XtraDB will refuse to start.
- if innodb_doublewrite is set to
innodb_doublewritewill be switched
OFFand a message written to the error log.
Here is a flowchart showing how atomic writes work inside InnoDB: