Configure Cassandra for production

You are currently viewing version 1.8 of the Apigee hybrid documentation.This version is end of life. You should upgrade to a newer version. For more information, seeSupported versions.

This topic describes steps you must take to configure the Cassandra database component for an Apigee hybrid production installation.

Configure storage and heap settings

For a production installation of Apigee hybrid, Google recommends that you add the following storage and heap settings to your overrides file and apply them to the cluster:

Note:All Cassandra storage settings in the overrides file are per pod.See alsoScaling Cassandra.
cassandra:  ...  storage:    capacity: 500Gi  resources:    requests:      cpu: 7      memory: 15Gi  maxHeapSize: 8192M  heapNewSize: 1200M

For more information on these property settings, see the Configuration property reference.

Add SSD storage for production

For the Cassandra database, the hybrid runtime only supports using dynamically created persistent volumes to store data. Usinglocally created persistent volumes is not supported.

To configure Cassandra properly for a hybrid production environment, you must configure aStorageClass definition that is backed by a solid-state drive (SSD) and make it the default class. SeeStorageClass configuration for detailed steps.

Note: The Cassandra database for hybrid should not use persistent volumes provisioned on network file system (NFS) or network-attached storage (NAS) systems.

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2026-02-18 UTC.