Install and Configure MariaDB for Cloudera Software
To use a MariaDB database, follow these procedures. For information on compatible versions of MariaDB, see CDH and Cloudera Manager Supported Databases.
Installing MariaDB Server
- Install MariaDB server:
OS Command RHEL compatible sudo yum install mariadb-server
SLES sudo zypper install mariadb-server
Ubuntu sudo apt-get install mariadb-server
If these commands do not work, you might need to add a repository or use a different yum install command, particularly on RHEL 6 compatible operating systems. For more assistance, see the following topics on the MariaDB website:- RHEL compatible: Installing MariaDB with yum
- SLES: MariaDB Package Repository Setup and Usage
- Ubuntu: Installing MariaDB .deb Files
Configuring and Starting the MariaDB Server
- Stop the MariaDB server if it is running:
- RHEL 7 compatible:
sudo systemctl stop mariadb
- RHEL 6 compatible, Ubuntu, SLES:
sudo service mariadb stop
- RHEL 7 compatible:
- If they exist, move old InnoDB log files /var/lib/mysql/ib_logfile0 and /var/lib/mysql/ib_logfile1 out of /var/lib/mysql/ to a backup location.
- Determine the location of the option file, my.cnf (/etc/my.cnf by default).
- Update my.cnf so that it conforms to the following requirements:
- To prevent deadlocks, set the isolation level to READ-COMMITTED.
- The default settings in the MariaDB installations in most distributions use conservative buffer sizes and memory usage. CDH roles need high write throughput because they might insert many records in the database. Cloudera recommends that you set the innodb_flush_method property to O_DIRECT.
- Set the max_connections property according to the size of your cluster:
- Fewer than 50 hosts - You can store more than one database on the same host. If you do this, you should:
- Put each database on its own storage volume.
- Allow 100 maximum connections for each database and then add 50 extra connections. For example, for two databases, set the maximum connections to 250. If you store five databases on one host, set the maximum connections to 550.
- More than 50 hosts - Do not store more than one database on the same host. Use a separate host for each database/host pair. The hosts do not need to be reserved exclusively for databases, but each database should be on a separate host.
- Fewer than 50 hosts - You can store more than one database on the same host. If you do this, you should:
- Although binary logging is not a requirement for CDH installations, it provides benefits such as MariaDB replication or point-in-time incremental recovery after a database restore. The provided example configuration enables the binary log. For more information, see The Binary Log.
Here is an option file with Cloudera recommended settings:
[mysqld] datadir=/var/lib/mysql socket=/var/lib/mysql/mysql.sock transaction-isolation = READ-COMMITTED # Disabling symbolic-links is recommended to prevent assorted security risks; # to do so, uncomment this line: symbolic-links = 0 # Settings user and group are ignored when systemd is used. # If you need to run mysqld under a different user or group, # customize your systemd unit file for mariadb according to the # instructions in http://fedoraproject.org/wiki/Systemd key_buffer = 16M key_buffer_size = 32M max_allowed_packet = 32M thread_stack = 256K thread_cache_size = 64 query_cache_limit = 8M query_cache_size = 64M query_cache_type = 1 max_connections = 550 #expire_logs_days = 10 #max_binlog_size = 100M #log_bin should be on a disk with enough free space. #Replace '/var/lib/mysql/mysql_binary_log' with an appropriate path for your #system and chown the specified folder to the mysql user. log_bin=/var/lib/mysql/mysql_binary_log #In later versions of MariaDB, if you enable the binary log and do not set #a server_id, MariaDB will not start. The server_id must be unique within #the replicating group. server_id=1 binlog_format = mixed read_buffer_size = 2M read_rnd_buffer_size = 16M sort_buffer_size = 8M join_buffer_size = 8M # InnoDB settings innodb_file_per_table = 1 innodb_flush_log_at_trx_commit = 2 innodb_log_buffer_size = 64M innodb_buffer_pool_size = 4G innodb_thread_concurrency = 8 innodb_flush_method = O_DIRECT innodb_log_file_size = 512M [mysqld_safe] log-error=/var/log/mariadb/mariadb.log pid-file=/var/run/mariadb/mariadb.pid # # include all files from the config directory # !includedir /etc/my.cnf.d
- If AppArmor is running on the host where MariaDB is installed, you might need to configure AppArmor to allow MariaDB to write to the binary.
- Ensure the MariaDB server starts at boot:
OS Command RHEL 7 compatible sudo systemctl enable mariadb
RHEL 6 compatible sudo chkconfig mariadb on
SLES sudo chkconfig --add mariadb
Ubuntu sudo chkconfig mariadb on
- Start the MariaDB server:
- RHEL 7 compatible:
sudo systemctl start mariadb
- RHEL 6 compatible, Ubuntu, SLES:
sudo service mariadb start
- RHEL 7 compatible:
- Run /usr/bin/mysql_secure_installation to set the MariaDB root password and other security-related settings. In a new installation, the root password is blank. Press the Enter key when you're prompted for the root password. For the rest of the prompts, enter the responses listed below
in bold:
sudo /usr/bin/mysql_secure_installation [...] Enter current password for root (enter for none): OK, successfully used password, moving on... [...] Set root password? [Y/n] Y New password: Re-enter new password: [...] Remove anonymous users? [Y/n] Y [...] Disallow root login remotely? [Y/n] N [...] Remove test database and access to it [Y/n] Y [...] Reload privilege tables now? [Y/n] Y [...] All done! If you've completed all of the above steps, your MariaDB installation should now be secure. Thanks for using MariaDB!
Installing the MySQL JDBC Driver for MariaDB
The MariaDB JDBC driver is not supported. Follow the steps in this section to install and use the MySQL JDBC driver instead.
Install the JDBC driver on any hosts running services that require database access. For more information on Cloudera software that uses databases, see Required Databases.
OS | Command |
---|---|
RHEL |
|
SLES |
sudo zypper install mysql-connector-java |
Ubuntu or Debian |
sudo apt-get install libmysql-java |
Creating Databases for Cloudera Software
- Each Hive metastore
- Sentry Server
- Sqoop Server
- Hue
- Oozie
The databases must be configured to support the MySQL utf8 character set encoding.
Record the values you enter for database names, usernames, and passwords. You will need them to configure the individual services later.
- Log in as the root user, or another user with privileges to create database and grant privileges:
mysql -u root -p Enter password:
- Create databases for each service you are using from the below table:
MariaDB [(none)]> CREATE DATABASE <database> DEFAULT CHARACTER SET utf8 DEFAULT COLLATE utf8_general_ci; Query OK, 1 row affected (0.00 sec) MariaDB [(none)]> GRANT ALL ON <database>.* TO '<user>'@'%' IDENTIFIED BY '<password>'; Query OK, 0 rows affected (0.00 sec)
You can use any value you want for <database>, <user>, and <password>. The following examples are the suggested names, but you are not required to use them:Databases for Cloudera Software Service Database User Hue hue hue Hive Metastore Server metastore hive Sentry Server sentry sentry Oozie oozie oozie - Confirm that you have created all of the databases:
MariaDB [(none)]> SHOW DATABASES;
You can also confirm the privilege grants for a given user by running:MariaDB [(none)]> SHOW GRANTS FOR '<user>'@'%';
Install CDH Packages
After completing the above instructions to install and configure MariaDB databases for Cloudera software, continue to Step 4: Install CDH Packages.