Increasing the memory allocation for the management database

You can increase the maximum memory allocation for the management database in a running deployment.

Before you begin

When increasing the memory allocation, complete a manual backup of the management database and Portal subsystem just prior to changing the allocation. Note that this backup is in addition to any scheduled backups that you have configured. The manual backup ensures that any data changes that occurred after the most recent scheduled backup are captured.

For details on creating a backup, see Backing up the management database in a Kubernetes environment and Backing up and restoring the Developer Portal.

About this task

Starting with API Connect version 2018.4.1.3, you can increase the maximum memory allocation for the management database in a running deployment. This procedure works for both Kubernetes and OVA environments. All the pods in the API Connect cluster must be up and running to increase the maximum memory value in a running deployment.

Procedure

  1. Ensure all pods are up and running using the kubectl get pods command.
  2. Use the following apicup command to increase the maximum memory: 
    apicup subsys set <MANAGEMENT_SUBSYS_NAME> cassandra-max-memory-gb <new_value>
  3. Reinstall the management subsystem to push the change to the cluster. This may take several minutes as each pod updates. 
    apicup subsys install <MANAGEMENT_SUBSYS_NAME>