It's time to get to know four of the most commonly used administration commands for your MariaDB server: mysql, mysqladmin, mysqldump, and mysqlimport.

"In just a short amount of time, I added the functionality I needed and enabled a whole new way of interacting with MaxScale." - MaxScale Team's Intern Markus Mäkelä shares his thoughts on developing for MaxScale.


Mark Riddoch, one of the MaxScale team, describes how a MaxScale plugin was developed for that allows the proxy to be used to reduce the load placed on the master in large MySQL replication environments.

At, we have very wide replication topologies. It is not uncommon to have more than fifty (and sometimes more than a hundred) slaves replicating from the same master. When reaching this number of slaves, one must be careful not to saturate the network interface of the master. A solution exists but it has its weaknesses. We came up with an alternative approach that better fits our needs: the Binlog Server. We think that the Binlog Server can also be used to simplify disaster recovery and to ease promoting a slave as a new master after failure. Read on for more details.

There will come a time when you must search for a particular text string in a field in MariaDB, and you may not know what database or table it might be in. It is somewhat like searching for a needle in a haystack, but fortunately we have good tools for finding our needle. I like to dump the database I'm searching into a text file and do my searches on the file, because it's a fast way to search, and you can mangle the dump file all you want without damaging anything important. When you have the results, you can run SQL queries on the appropriate tables to make the replacements.

This is an introduction to MariaDB Replication and to why we need a binlogs server and what this is. The first part is an introduction to replication basics, and if you know this already, then you want want to skip past the first section or two.

The server weighting feature of MaxScale may initially be seen as a way to influence load balancing for unequal servers, but it can also be useful for other reasons. Here we look at how we can use it to segregate different workloads within a cluster of MariaDB or MySQL servers.

The need for this post became obvious after receiving an increasing amount of questions which were related to linking, library versions and paths in MaxScale. Moreover, I know that there are many who want to make things with their bare hands so it is good to have something which hopefully makes the whole process smoother.

image from This file is licensed under the Creative Commons Attribution-Share Alike 2.0 Generic license.
Elon Musk has “Va Va Voom”. His forward thinking has delivered many successes over the years, from payment provider PayPal, to SpaceX, which manufactures space launch vehicles. No surprise then he has been compared to Tony Stark (Iron Man from the Marvel comic series). However, his latest announcement shows shrewd business judgement, something Musk is renowned for, shining through as he sets his sights on the global car industry.
Read more on open shared innovation in this blog by Patrik Sallner, CEO at SkySQL.

MaxScale is a modular proxy application, the modules can be considered as the building blocks of your proxy implementation within your MySQL database environment. It is important to know what building blocks you have at your disposal. The release of version 1.0 as a beta means that the number of available modules has grown once again. Normally I post about the incremental changes in what is available, but I thought that maybe it was a good time to post a short summary of all the modules. This is not designed to be comprehensive documentation for the functionality available, merely as a summary of what is available.


Newsletter Signup

Subscribe to get MariaDB tips, tricks and news updates in your inbox: