MaxScale for MariaDB and MySQL hides the complexity of database scaling from the application. To streamline building MaxScale from source and running the test suite, you can automate the process with some useful tools to meet your needs. I have created a Vagrant / Puppet setup I'd like to share with you.
MaxScale 1.0 from SkySQL is now in Beta and there are some cool features in it, I guess some adventurous people has already put it into production. There are still some rough edges and stuff to be fixed, but it is clearly close to GA. One thing missing though are something to manage starting and stopping MaxScale in a somewhat controlled way, which is what this blog is all about.
Here we take a look at how one of the example filters supplied with the MaxScale 1.0 beta can answer that simplest of profiling questions - "Which of my database queries run within the MySQL server for the longest time?".
We all know that in general it's a bad idea to have columns values contain too much "hidden" information, and in particular for primary keys, this is a big no-no, although I know that not everybody agrees here. In some cases though, there is data that at it's heart contains several aspects and we just cannot avoid this, the prime example being data and time values. What I mean here is that a single datetime value has aspects that aren't always obvious from the datetime value itself. Examples include leap year information and weekday.
I spend perhaps too much time generating and reviewing numbers and charts and reports, but the right combination of tools can make this enjoyable (or at least less tedious). For me, that generally means using the pandas data analysis library and the python programming language to analyze data stored in MariaDB or MySQL.
It's time to get to know four of the most commonly used administration commands for your MariaDB server:
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.
You've decided to move from MySQL to MariaDB, but you're a little nervous. The last thing you want is to become mired in a slough of brokenness. Don't worry, because MariaDB is designed to be a drop-in replacement for MySQL. You should be able to install MariaDB over your MySQL server, and then go about your business without drama.
The simplest method follows these steps:
WordPress has evolved from a specialized blogging platform into today's most widely used open source content management software (CMS), with thousands of third-party themes and plugins. WordPress was developed with MySQL as a back end, but because MariaDB is designed as a binary drop-in replacement of the original MySQL, you can replace MySQL with MariaDB for your WordPress installation and take advantage of its better performance, along with new features such as the two new database engines: XtraDB, which replaces InnoDB, and Aria, a crash-safe alternative for MyISAM.
How do you choose the best Linux filesystem for your MariaDB server? The primary factors to look at are data integrity, performance, and ease of administration. Data integrity tops the list because fixing a corrupted database is even less fun than it sounds, and filesystems play a key role in data integrity. Performance is important because faster is better and time is money, and ease of administration matters for the same reasons as performance.