Installing TokuDB

Note that ha_tokudb is not included in binaries built with the "old" glibc. Binaries built with glibc 2.14+ do include it.

The following sections detail how to install and enable TokuDB.

Installing TokuDB

Until MariaDB versions 5.5.39 and 10.0.13, before upgrading TokuDB, the server needed to be cleanly shut down. If the server was not cleanly shut down, TokuDB would fail to start. Since 5.5.40 and 10.0.14, this has no longer been necessary. See MDEV-6173.

TokuDB has been included with MariaDB since and and does not require separate installation. Proceed straight to Check for Transparent HugePage Support on Linux. For older versions, see the distro-specific instructions below.

Installing TokuDB on Fedora, RedHat, & CentOS

In , , and starting from TokuDB is in a separate RPM package called MariaDB-tokudb-engine and is installed as follows:

Installing TokuDB on Ubuntu & Debian

On Ubuntu, TokuDB is available on the 64-bit versions of Ubuntu 12.10 and newer. On Debian, TokuDB is available on the 64-bit versions of Debian 7 "Wheezy" and newer.

The package is installed as follows:

In some earlier versions, from and , TokuDB is in a separate package calledmariadb-tokudb-engine-x.x, where x.x is the MariaDB series (5.5 or10.0). The package is installed, for example on 5.5, as follows:

libjemalloc

TokuDB requires the libjemalloc library (currently version 3.3.0 or greater).

libjemalloc should automatically be installed when using a package manager, and is loaded by restarting MariaDB.

It can be enabled, if not already done, by adding the following to the my.cnf configuration file:

If you don't do the above, you will get an error similar to the following one in your error file

Check for Transparent HugePage Support on Linux

Transparent hugepages is a feature in newer linux kernel versions that causes problems for the memory usage tracking calculations in TokuKV and can lead to memory overcommit. If you have this feature enabled, TokuKV will not start, and you should turn it off.

You can check the status of Transparent Hugepages as follows:

If the path does not exist, Transparent Hugepages are not enabled and you may continue.

Alternatively, the following are returned:

indicating Transparent Hugepages are not enabled and you may continue. If the following is returned:

Transparent Hugepages are enabled, and you will need to disable them.

To disable them, pass "transparent_hugepage=never" to the kernel in your bootloader (grub, lilo, etc.). For example, for SUSE, add transparent_hugepage=never to Optional Kernel Command Line Parameter at the end, such as after "showopts", and press OK. The setting will take effect on the next reboot.

You can also disable with:

On Centos or RedHat you can do:

Add line GRUB_CMDLINE_LINUX_DEFAULT="transparent_hugepage=never" to file /etc/default/grub

Update grub (boot loader):

For more information, see

Enabling TokuDB

Attempting to enable TokuDB while Linux Transparent HugePages are enabled will fail with an error such as:

See the section above; .

The before attempting to enable TokuDB. Strictly speaking, the XA code requires two XA-capable storage engines, and this is checked at startup. In practice, this requires InnoDB and the binary log to be active. If it isn't, the following warning are returned and XA features are disabled:

MariaDB's default my.cnf files come with a section for TokuDB. To enable TokuDB just remove the '#' comment markers from the options in the TokuDB section.

A typical TokuDB section looks like the following:

By default, the plugin-load option is commented out. Simply un-comment it as in the example above.

Don't forget to also enable jemalloc in the config file.

With these changes done, you can restart MariaDB to activate TokuDB.

Enabling TokuDB on Fedora

Instead of putting the TokuDB section in the main my.cnf file, it is placed in a separate file located at: /etc/my.cnf.d/tokudb.cnf

Enabling TokuDB on Ubuntu & Debian

Instead of putting the TokuDB section in the main my.cnf file, it is placed in a separate file located at: /etc/mysql/conf.d/tokudb.cnf

Enabling TokuDB Manually From the mysql Command Line

Generally, it is recommended to use one of the above methods to enable the TokuDB storage engine, but it is also possible to enable it manually as with other plugins. To do so, launch the mysql command-line client and connect to MariaDB as a user with the SUPER privilege and execute the following command:

TokuDB are installed until someone executes .

Temporarily Enabling TokuDB When Starting MariaDB

If you just want to test TokuDB, you can start the mysqld server with TokuDB with the following command:

See Also

• .

_{This page is licensed: CC BY-SA / Gnu FDL}