Step 6: Test MariaDB Enterprise Server

Overview

This page details step 6 of the 9-step procedure "Deploy Xpand Storage Engine Topology".

This step tests MariaDB Enterprise Server 10.5.

Several actions require connection to MariaDB Enterprise Server. A command-line client (mariadb) was included with your ES installation. These instructions describe connection via Unix domain socket. Alternatively, a different client and connection method could be used.

Interactive commands are detailed. Alternatively, the described operations can be performed using automation.

Test Enterprise Server Service

Use Systemd to test whether the MariaDB Enterprise Server service is running.

This action is performed on each Enterprise Server node.

Check if the MariaDB Enterprise Server service is running by executing the following:

$ systemctl status mariadb

If the service is not running on any node, start the service by executing the following on that node:

$ sudo systemctl start mariadb

Test Local Client Connections

Use MariaDB Client to test the local connection to the Enterprise Server node.

This action is performed on each Enterprise Server node:

$ sudo mariadb
Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MariaDB connection id is 38
Server version: 10.5.13-9-MariaDB-Enterprise MariaDB Enterprise Server

Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MariaDB [(none)]>

The sudo command is used here to connect to the Enterprise Server node using the root@localhost user account, which authenticates using the unix_socket authentication plugin. Other user accounts can be used by specifying the --user and --password command-line options.

Test Xpand Storage Engine Plugin

Query the information_schema.PLUGINS table to confirm that the Xpand storage engine is loaded.

This action is performed on each Enterprise Server node.

Execute the following query:

SELECT PLUGIN_NAME, PLUGIN_STATUS
FROM information_schema.PLUGINS
WHERE PLUGIN_LIBRARY LIKE 'ha_xpand%';
+-------------+---------------+
| PLUGIN_NAME | PLUGIN_STATUS |
+-------------+---------------+
| XPAND       | ACTIVE        |
+-------------+---------------+

The PLUGIN_STATUS column for the Xpand storage engine plugin should contain ACTIVE.

Test Xpand Table Discovery

The Xpand storage engine automatically discovers tables in Xpand when the database exists in Enterprise Server. In Step 3: Test Xpand: Test DDL and DML, the test.contacts table was created in Xpand. To access the table in Enterprise Server, create the test database.

This action is performed on each Enterprise Server node.

Create the test database using the CREATE DATABASE statement:

CREATE DATABASE IF NOT EXISTS test;

Note

In a Xpand Storage Engine Topology, the ES nodes do not synchronize databases automatically. MariaDB Replication can be used to synchronize databases and other objects. Without replication, the database needs to be created separately on each ES node.

Confirm that the test.contacts table can be queried:

SELECT * FROM test.contacts;
+----+------------+-----------+--------------------------+
| id | first_name | last_name | email                    |
+----+------------+-----------+--------------------------+
|  1 | Walker     | Percy     | w.percy@example.com      |
|  2 | Flannery   | O'Connor  | flan.oconnor@example.edu |
+----+------------+-----------+--------------------------+

Next Step

Navigation in the procedure "Deploy Xpand Storage Engine Topology":

  • This page was step 6 of 9.