If you want to use TokuDB with MariaDB, MySQL, or Percona Server, you will need to disable support for transparent hugepages in Linux.

Fortunately, this is very easy to check, and to change.

An easy way to check is with:

cat /sys/kernel/mm/transparent_hugepage/enabled

This will return something like:

[always] madvise never

Note the word surrounded by “[]” is what this option is set to. So the above is set to “always”. To disable it, we want it set to “never”.

I’ve found the easiest way to change/set this is to add the below to your /etc/rc.local file (and then reboot your system):

if test -f /sys/kernel/mm/transparent_hugepage/enabled; then
   echo never > /sys/kernel/mm/transparent_hugepage/enabled
fi
if test -f /sys/kernel/mm/transparent_hugepage/defrag; then
   echo …

TokuDB is gaining more and more popularity and many people are finding it very helpful for certain cases.

Using/enabling it in some distributions can be quite a pain, but enabling it in MariaDB is easy as 1-2-…, well, only 1-2, since that’s all there is to it!

1. Ensure you have the correct MariaDB version:

• MariaDB 5.5.36+
• MariaDB 10.0.9+
• Note: Linux 64-bit systems only – specific packages include: Ubuntu, Debian, Fedora, CentOS, Red Hat
• Note: If using the Linux tarball – it must be the version built with glibc 2.14+

2. Run this command:

INSTALL SONAME 'ha_tokudb';

or update my.cnf file with:

[mysqld]
plugin-load=ha_tokudb

There is one requirement from TokuDB, which is to have transparent …

There are several ways to upgrade MySQL. In this post, we will use a combination of shell scripts and the mysqldump application to export our MySQL data, and then re-import it back into the upgraded version of MySQL.

In this example, we will be doing a minor version upgrade. We will be going from 5.6.17 to 5.6.19. This method may not work if you are upgrading from one major release to another – from 5.1 to 5.5, or 5.5 to 5.6. You will want to check each version and review the new features/functions and also what features/functions have been deprecated. We are also assuming that no one will be using the database during the time it takes for us to do the upgrade.

If you want to upgrade from a …

MySQL 5.5.39 was recently released (it is the latest MySQL 5.5, is GA), and is available for download here:

http://downloads.skysql.com/archive/index/p/mysql/v/5.5.39

This release, similar to the last 5.5 release, is mostly uneventful.

There were two “Functionality Added or Changed” and 24 bugs fixed.

The “Functionality Added or Changed” changes are:

• CMake support was updated to handle CMake version 3.
• The timed_mutexes system variable has no effect and is deprecated.

Out of the 24 bugs, most seemed rather minor or obscure, but here are the ones I think are worth noting (crashing, security, wrong results, deadlock):

• InnoDB: Opening a parent table that has thousands of child tables could result in a long semaphore wait condition.
• …

The MySQL Utilities Team is pleased to announce the latest GA release of MySQL Utilities, release-1.4.4. This release includes improvements in terms of usability, stability, security and an overall improvement regarding the comprehensibility of the provided error messages.

Improvements

The following highlights a few of the more significant improvements.

• mysqlrpladmin errant transactions for switchover have been improved. Note : The errant transactions check requires all servers in the topology to have GTID’s enabled.
• Failed MySQL server connection error messages now display the actual error returned from the failed connection.
• Error messages that occur during automatic slave discovery (–discover-slaves-login) have been improved. Now the –verbose option generates specific information for each slave, including their respective errors.
• mysqlserverinfo utility can now start …

PodcastsGeneral

This week we complete our series on Common Schema by talking about QueryScript. Special guest co-host Jon Day of SkySQL joins us. Ear Candy is some MySQL security tips and At the Movies is a humorous look at value chain mapping.

Last week we released Connector/Python v2.0 (alpha); today we publish the source on GitHub. Yes, we are using Git internally and are now able to push it out on each release. Previous versions are still available through LaunchPad.

Here is the full process to get Connector/Python installed in a virtual environment. You’ll need Git installed of course.

shell> git clone https://github.com/oracle/mysql-connector-python.git cpy
shell> virtualenv ENVCPY
shell> source ENVCPY/bin/activate
(ENVCPY)shell> cd cpy
(ENVCPY)shell> python setup.py install
(ENVCPY)shell> python
>>> import mysql.connector
>>> mysql.connector.__version__ …

It dawned on me that most folks are using the Installer these days.

As I need quick access to every MySQL version,  using an Installer is never an option.
And for folks wanting 100% control over their setups, they may not want an installer doing things.

So this shows how to setup an instance manually.

1. download non-installer .zip version from dev.mysql.com
2. create a directory c:\mysql and c:\mysql\tmp
3. unzip the .zip into c:\mysql
4. move the data directory into c:\mysql for easier future upgrades
5. create a basic my.ini
6. install the service
7. start the service

Here I'll show each step with more detail.   I purposely leave out things like post-installation security, to keep it simple.
1.  Create a directory. Decide where you will put the installation and datadir.  I …

MySQL plays a critical role in OpenStack. It serves as the host database supporting most components such as Nova, Glance, and Keystone and is the most mature guest database in Trove. Many OpenStack operators use Percona open source software including the MySQL drop-in compatible Percona Server and Galera-based Percona XtraDB Cluster as well as tools such as Percona XtraBackup and Percona Toolkit. We see a need in the community to understand how to improve MySQL performance …

[…] Read this article: Prewarm your EBS backed EC2 MySQL slaves | DBA Dojo […]