Configure large message payload support in Apigee hybrid

Stay organized with collections Save and categorize content based on your preferences.

Overview

Starting in version 1.14.2, Apigee hybrid supports large message payloads up to 30MB. The default message payload size is 10MB. See Message payload size.

To enable large message payload support for your hybrid installation, you need to make the following changes to your runtime configuration:

• Increase the heap size to 4Gi.
• Increase runtime.resources.limits.memory to 4Gi.
• Increase runtime.resources.requests.memory to 6Gi.

Configure large message payload support for Apigee hybrid

1. Add the following stanza to your overrides.yaml file:

   runtime:
     cwcAppend:
       bin_setenv_max_mem: 4096m   # Increase max heap size to 4 gigs
     resources:
       requests:
         memory: 4Gi
       limits:
         memory: 6Gi
   

2. Upgrade the apigee-env chart for each environment in your installation:

   Dry run:

   helm upgrade ENV_RELEASE_NAME apigee-env/ \
     --install \
     --namespace APIGEE_NAMESPACE \
     --set env=ENV_NAME \
     -f OVERRIDES_FILE \
     --dry-run=server
   

   • ENV_RELEASE_NAME is a name used to keep track of installation and upgrades of the apigee-env chart. This name must be unique from the other Helm release names in your installation. Usually this is the same as ENV_NAME. However, if your environment has the same name as your environment group, you must use different release names for the environment and environment group, for example dev-env-release and dev-envgroup-release. For more information on releases in Helm, see Three big concepts class="external" in the Helm documentation.
   • ENV_NAME is the name of the environment you are upgrading.
   • OVERRIDES_FILE is your edited overrides.yaml file.

   Upgrade the chart:

   helm upgrade ENV_RELEASE_NAME apigee-env/ \
     --install \
     --namespace APIGEE_NAMESPACE \
     --set env=ENV_NAME \
     -f OVERRIDES_FILE