Skip to content

Cluster Database Configuration

QIE uses in-memory tables to communicate information between nodes in the cluster. The backend database needs to be configured to support the in-memory tables before a cluster can be brought online. See Alternate Database for the environment variables that configure QIE's connection to the back-end database.

Microsoft SQL Server

By default, Microsoft SQL Server (MSSQL) does not have in-memory tables enabled. To ensure proper QIE cluster functionality, you must execute a specific script on your database schema before connecting QIE.

Important: Certain cloud-hosted MSSQL database tiers (e.g. in AWS and Microsoft Azure) may not support in-memory tables. If you encounter this limitation, you must upgrade to a higher-tier database instance.

For detailed instructions on running the script, see Setup In-Memory Tables (High Availability Only) in the Install Guide.

MariaDB/MySQL

MariaDB and MySQL installations typically have in-memory tables enabled by default. However, some cloud providers, such as AWS, may disable this feature on their free-tier database offerings. If you are using AWS Aurora, ensure you select a database tier that supports in-memory tables.

MySQL JDBC Driver

Due to MySQL licensing constraints, QIE does not include the JDBC driver. Therefore, you must manually download and install it before connecting QIE to a MySQL database.

Installation Instructions:

  1. Download the latest MySQL Connector/J driver from: https://dev.mysql.com/downloads/connector/j/.

  2. Select the "Platform Independent" operating system option.

  3. Download the "Zip Archive." (You can skip the login/signup prompt by selecting "No thanks, just start my download.")

  4. Extract the downloaded ZIP file.

  5. Locate the mysql-connector-java-{version}.jar file within the extracted folder.

  6. Extract the contents of the .jar file (treat it as a ZIP archive) into a directory.

  7. Mount this directory to '/java/qie/jdbcDriver'. This ensures the QIE service can access the driver and verify session table creation.

Alternative: You can create a custom QIE image with the extracted .jar contents already placed in the '/java/qie/jdbcDriver' directory, eliminating the need for mounting.