Planning the analytics profile, storage class, and storage type
Begin planning your IBM® API Connect analytics deployment by choosing a deployment profile, a Kubernetes storage class, and an OpenSearch storage type.
Decide which deployment
profile you want to use, the available profiles are
listed on Analytics component deployment profile limits.
Kubernetes storage class
Before you install analytics, you must choose a storage class.
Local Volume are all supported; however,
Volume is most suitable for analytics. The analytics subsystem provides internal data
replication and HA support, so the additional HA capabilities that
Block storage might give you are not needed. In addition, analytics requires a high
throughput of disk I/O operations to successfully handle the analytics data load from the gateway.
Local Volume is the best-performing option in this area.
GlusterFSstorage is not supported for analytics. If you use this option, you might encounter severe performance degradation, and possibly loss of data.
OpenSearch storage type
- Shared storage
A single pod provides data storage and OpenSearch cluster management. Shared storage is the default option, and the only option on a one replica deployment.
- Dedicated storage OpenSearch data storage and cluster management functions are split, and run in separate pods on each worker node:
storage-os-master- Runs an OpenSearch
manager eligiblenode that manages the OpenSearch cluster, but does not store any API event data.
storage- Runs an OpenSearch
datanode that stores API event data.
storagepod replicas in order to scale horizontally (you do not need to increase the number of
storage-os-masterreplicas). Dedicated storage also provides greater stability and allows some OpenSearch configuration changes to be made without downtime.
You can change storage type after installation, see Changing storage type between shared and dedicated.