You are here

In this blog we look at how MaxScale helps minimize database access down time for client applications. Following our partner Severalnines’ recent announcement we want to inform the MariaDB community know that there is an automation and management platform available to them, ClusterControl, that will help them deploy and manage MaxScale for MariaDB (which in turn also helps minimize downtime).


Losing temporary tables on a slave when binlog_format is not set to ROW is a well-known problem, and there is even a way to avoid it, as described by the safe slave shutdown procedure in the MySQL documentation. However, the documentation doesn't describe how to fix your slave if you accidentally shut it down while it has temporary tables open. In this blog post, I'll describe how to do that.

The year has flown by so quickly and I am simply stunned that Fall is now upon us. With the changing of seasons it is time for another software release of MariaDB Enterprise (MDBE) as well as MaxScale.

My last row-level security blog post got a few questions, so I decided that it would be good to follow up with more detail. The last blog post described some basic information about row-level security, but row-level security policies are highly dependent on an application's or organization's security requirements. In this blog post, I'm going to walk through an example row-level security implementation in MariaDB 10.0 in a little more detail.

At this week’s re:Invent conference, Amazon Web Services (AWS) announced it is joining the MariaDB community with the introduction of its Relational Database Service (RDS) for MariaDB. Amazon’s decision was driven by the growing demand among its customers for MariaDB, which now has over two million users in 45 countries.


Parallel replication is a much-expected feature of MySQL. It is available in MariaDB 10.0 and in MySQL 5.7. In this 3rd post of the series, we present benchmark results from production environments.

The Convergence of Enterprise-Class and Choice – an Open Source Ecosystem Running on a True Enterprise-Class Platform: MariaDB Enterprise on IBM z Systems

Conservative in-order parallel replication is a great feature in MariaDB 10.0 that improves replication performance by using knowledge of group commit on the master to commit transactions in parallel on a slave. If slave_parallel_threads is greater than 0, then the SQL thread will instruct multiple worker threads to concurrently apply transactions that were committed in the same group commit on the master.

MariaDB and Foedus paths crossed less than a year ago when I met Paolo Messina at a two-day IBM event in Tuscany. IBM invited me, as the MariaDB Italian representative, to introduce MariaDB as an Open Source Solution for the POWER8 platform.

MaxScale 1.2.0 and above can call external scripts on monitor events. In the case of a classic Master-Slave setup, this can be used for automatic failover and promotion using MariaDB Replication Manager. The following use case is exposed using three MariaDB servers (one master, two slaves) and a MaxScale server.