MariaDB

Creating the Artifactory MariaDB Database

Artifactory provides a script that will execute the SQL commands you need to create your MariaDB database.

The script can be found in $JFROG_HOME/artifactory/app/misc/db/createdb/createdb_mariadb.sql and is displayed below.

You should review the script and modify it as needed to correspond to your specific environment.

CREATE DATABASE artdb CHARACTER SET utf8 COLLATE utf8_bin;
GRANT ALL on artdb.* TO 'artifactory'@'localhost' IDENTIFIED BY 'password';
FLUSH PRIVILEGES;

Once you have verified that the script is correct, you need to run it to create the database and proceed with configuring the database.

CREATE DATABASE artdb CHARACTER SET utf8 COLLATE utf8_bin;
GRANT ALL on artdb.* TO 'artifactory'@'%' IDENTIFIED BY 'password';
FLUSH PRIVILEGES;

Configuring Artifactory to use MariaDB

1. Download the MariaDB JDBC driver (available from the MariaDB website)  and copy the mariadb-java-client-<version>.jar file into $JFROG_HOME/artifactory/var/bootstrap/artifactory/tomcat/lib directory
   

   Permissions

   Make sure your driver has the same permissions as the rest of the files in the $JFROG_HOME/artifactory/var directory. 

2. Adjust the database connection details in the system.yaml configuration file.

   For example

   shared:
     database:
       type: mariadb
       driver: org.mariadb.jdbc.Driver
       url: jdbc:mariadb://<your db server url, for example: localhost:3306>/artdb?characterEncoding=UTF-8&elideSetAutoCommits=true&useSSL=false&useMysqlMetadata=true
       username: artifactory
       password: password

Known Issues

Lightweight Ping Query

The MariaDB Connector/J does not support the special  lightweight "/* ping */" query. JDBC Connection Pools perform regular validity checks on connections in the pool, which use an SQL validation query. 

Increasing MariaDB Default Packet Size

Since some data files (builds, configurations etc.) are stored in MariaDB, it is extremely important to increase the maximum allowed packet size used by MariaDB to avoid errors related to large packets.  

To learn more, please refer to Packet Too Large in the MariaDB.

We recommend changing this parameter in the /etc/my.cnf file as follows:

# The MariaDB server
[MariaDBd]
.
# The maximum size of the binary payload the server can handle
max_allowed_packet=8M
.

SET GLOBAL max_allowed_packet = 134217728;

Tuning MariaDB for Artifactory

When using Artifactory with MariaDB it is recommended to use the InnoDB engine with the following tuning parameters configured in the /etc/my.cnf file:

# The MariaDB server
[mysqld]
.
# By default innodb engine use one file for all databases and tables. We recommend changing this to one file per table.
# NOTE: This will take effect only if Artifactory tables are not created yet! Need to be set and MariaDB restarted before starting Artifactory for the first time.
innodb_file_per_table
 
# Theses are tuning parameters that can be set to control and increase the memory buffer sizes.
innodb_buffer_pool_size=1536M
tmp_table_size=512M
max_heap_table_size=512M
 
# Theses control the innodb log files size and can be changed only when MariaDB is down and MariaDB will not start if there are some innodb log files left in the datadir.
# So, changing theses means removing the old innodb log files before start.
innodb_log_file_size=256M
innodb_log_buffer_size=4M
.

Note that both the XtraDB and InnoDB engines are compatible with the various InnoDB system variables.

Both MySql and MariaDB servers do support the “/* ping */” query, but the MariaDB Connector/J wraps the query as if it was a standard SQL query and transforms it into a “SET STATEMENT...” query, which is illegal in terms of syntax as far as the server is concerned. For this reason, Artifactory uses a generic “SELECT 1” as a validation query for pooled connections when MariaDB is used as a database type. The MySql Connector has no such limitation, and supports the “/* ping */” query.