Install and Set Up Composer's Metadata Store
Before the Composer components can be installed in the target server, you must install and set up the metadata store that is used in the Composer environment. This must occur regardless of the technique used to install the components (using the installation script or an alternative installation method).
Composeruses a packaged PostgreSQL v12 database instance to store its metadata and strongly recommends using this instance due to the specific configuration and version employed. If you would like to use another PostgreSQL instance, contact Technical Support for further guidance.
The upgrade to Composer 5.9 or later from a Composer or Zoomdata version prior to 5.9, will usually successfully upgrade the PostgreSQL code and your Composer metadata store automatically. In addition, the previous PostgreSQL 9.5 installation is retained to ensure that data is not lost if the upgrade should fail.
Before you attempt to upgrade to Composer 5.9, be sure to back up your metadata store. See Back Up the Metadata Store.
If you are upgrading to Composer 5.9 or later, consider the following possible PostgreSQL migration issues:
No check for available disk space is performed during the upgrade. So the PostgreSQL automatic upgrade might fail if there is not enough available disk space to accommodate it. The Bootstrap installation procedure cannot predict the required amount of free disk space it will need.
If your installation uses an external PostgreSQL instance for Composer's metadata store, you must disable the automatic PostgreSQL upgrade in the Bootstrap procedure before you upgrade Composer.
If either of these migration issues is true for your installation, you can disable the automatic PostgreSQL upgrade using the Bootstrap
ZOOMDATA_POSTGRES_DISABLE_UPGRADE option. This option must be exported before running the Bootstrap procedure (for example by running
export ZOOMDATA_POSTGRES_DISABLE_UPGRADE=TRUE). After running the Bootstrap procedure with the PostgreSQL upgrade disabled, you must manually upgrade your PostgreSQL metadata store to PostgreSQL 12 before you can use Composer 5.9 or later.
Configuring PostgreSQL as the Composer involves defining authentication and connection parameters, restarting PostgreSQL, establishing login credentials for the Composer user, and creating metadata space for the Composer server and microservices. Complete the following steps to install and set up the PostgreSQL metadata store:
- Set Up the PostgreSQL Metadata Store
- Change Metadata Store Authentication to MD5 -- not necessary in Ubuntu environments
- Create the Metadata Store User & Stores
- Configure the Metadata Store for SSL
In addition, Logi Analytics highly recommends that you optimize the PostgreSQL database instance after every upgrade. See Vacuum Composer's Metadata Store.
If you have performance problems with your PostgreSQL metadata store, examine the database settings related to automatic vacuuming, automatic analyzing, and the write-ahead log (WAL). See Optimize Composer's Metadata Store Performance.
Optionally, if the target server on which Composer will be installed does not have Internet access, read Obtain the Installation Package Without Internet Access.