{"id":1518,"date":"2019-08-05T15:50:02","date_gmt":"2019-08-05T18:50:02","guid":{"rendered":"http:\/\/wagnerbianchi.com\/blog\/?p=1518"},"modified":"2021-04-21T18:39:40","modified_gmt":"2021-04-21T21:39:40","slug":"mariadb-maxscale-like-a-pro-setting-up-maxscale-2-3","status":"publish","type":"post","link":"http:\/\/wagnerbianchi.com\/blog\/?p=1518","title":{"rendered":"MariaDB MaxScale like a Pro: Setting up MaxScale 2.3"},"content":{"rendered":"

I created this series of blog posts after being worked with the MariaDB MaxScale for many customers. All the points mentioned here reflect my views; I’ll add links to the online docs so we can have an official reference. I intend to share my experiences working with MaxScale; we need more practical documentation so we improve the MaxScale usage and transfer knowledge.<\/p>\n

First of all<\/strong>, MaxScale 2.3 release, notes, take a look<\/a>.<\/p>\n

Something you need to know before starting with the praxis here – all instances are running Debian 9.<\/p>\n

root@prod-mariadb01:~# lsb_release -a\r\nNo LSB modules are available.\r\nDistributor ID:\tDebian\r\nDescription:\tDebian GNU\/Linux 9.9 (stretch)\r\nRelease:\t9.9\r\nCodename:\tstretch<\/pre>\n
MariaDB MaxScale in a nutshell…<\/strong><\/p>\n
The MariaDB MaxScale is an intelligent database proxy which understands SQL language and has a bunch of bundle modules known as routers or services, monitors, filters, etc. After setting up the MaxScale packages, you have access to all bundle modules, as you need only to add a basic configuration file and start the service. Since version 2.1, you don’t need to elaborate a complete configuration file (\/etc\/maxscale.cnf) to start the service. Once you get a configuration file with the global [maxscale] section and at least one service defined, you can start the MaxScale service.<\/p>\n
What are we going to be doing for setting up the MariaDB MaxScale?<\/p>\n
    \n
  1. Add the MariaDB Official Repository;<\/li>\n
  2. Create the needed users on the database servers (you will see soon that I’m considering you already a Master\/Slave running environment);<\/li>\n
  3. Create the .secrets file so we can encrypt the passwords for the users on the maxscale.cnf;<\/li>\n
  4. Create a basic configuration file for MaxScale and start the process;<\/li>\n
  5. Run dynamic commands so we can create a monitor (MariaDBMon), the servers, a listener, and link created servers with the monitor and the service.<\/li>\n<\/ol>\n
    Moving on…<\/strong><\/p>\n
    By chance, you can be running something like below, which is going to give you the global configuration plus the ReadWtiteSplit Router configured as the service to be configured:<\/p>\n
    #: This is the basic configuration file we can get in place to start maxscale.\r\n#: Notice that we need yet to come back soon to this file so we can add the service \r\n#: encrypted user password (attention to security matters, no clear text passwords, please)\r\n\r\n[maxscale]\r\nthreads                     = auto\r\nlog_augmentation            = 1\r\nms_timestamp                = 1\r\n\r\n[rwsplit-service]\r\ntype                        = service\r\nrouter                      = readwritesplit\r\nuser                        = maxusr\r\npassword                    = <add your encrypted maxusr password here>\r\nversion_string              <\/span>= 5.5.50-MariaDB #:should be used with all 10.1 servers and older<\/span>\r\n<\/pre>\n
    As we need SOP<\/em> or Standard Operational Procedures for everything we perform, the documentation I have for setting up MaxScale considers to always have two users:<\/p>\n