Contact usRequest a demo

Additional database-related settings

All the settings below can be added at the schema level. For example, the statistics database can become very large over time, so you may want to use a separate server for the statistics database.

Connection and pool parameters can be added to the configuration file. In such a case, all other schemas would use the default connection pool.

Listing 1. Unblu database configuration reference\:h2\:mem\:unblu

Connection pool

The default JDBC connection pool is HikariCP. It provides improvements in both speed and stability compared to the deprecated EclipseLink connection pool:

  • Connections are closed when not used for a longer period.

  • Connections are validated before using java.sql.Connection.isValid(int) provided by the JDBC Driver. For more information refer to the Java documentation.

  • New connections are opened proactively, not just on demand.

A Grafana dashboard called "Database (HikariCP)" visualizing all HikariCP metrics is automatically deployed with every Unblu cluster installation.

Listing 2. HikariCP default configuration
# Database connection pool (1) (2)
1 Maximum number of connections in the pool.
2 Minimum number of connections that should be idle, new connections are added to the pools when connections are busy up to the configured maximum number of connections.

The configuration above reflects the default settings. Only add a connection pool configuration if you want to deviate from this default. For production setups, the following values may be more appropriate: