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:
For the Cassandra database, the hybrid runtime only supports using
dynamically created persistent volumes to store data. Using locally created persistent
volumes is not supported.
To configure Cassandra properly for a hybrid production environment, you must configure a
StorageClass
definition that is backed by a solid-state drive (SSD) and make it the default
class. See StorageClass configuration for detailed steps.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[[["\u003cp\u003eVersion 1.8 of the Apigee hybrid documentation is end of life, and users should upgrade to a newer version.\u003c/p\u003e\n"],["\u003cp\u003eFor production installations, specific storage and heap settings are recommended for the Cassandra component, and these settings must be added to the overrides file and applied to the cluster.\u003c/p\u003e\n"],["\u003cp\u003eCassandra database storage in Apigee hybrid production environments must use dynamically created persistent volumes, not locally created ones.\u003c/p\u003e\n"],["\u003cp\u003eThe Cassandra database must be backed by a solid-state drive (SSD) and use a StorageClass definition as its default, while network file systems (NFS) or network-attached storage (NAS) systems are not supported.\u003c/p\u003e\n"]]],[],null,["# Configure Cassandra for production\n\n| 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, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\n\nThis topic describes steps you must take to configure the Cassandra database\ncomponent for an Apigee hybrid production installation.\n\nConfigure storage and heap settings\n-----------------------------------\n\n\nFor a production installation of Apigee hybrid, Google recommends that you add the\nfollowing storage and heap settings to your overrides file and apply them to the cluster:\n**Note:** All Cassandra storage settings in the overrides file are per pod. See also [Scaling Cassandra](/apigee/docs/hybrid/v1.8/cassandra-scaling). \n\n```text\ncassandra:\n ...\n storage:\n capacity: 500Gi\n resources:\n requests:\n cpu: 7\n memory: 15Gi\n maxHeapSize: 8192M\n heapNewSize: 1200M\n```\n\n\nFor more information on these property settings, see the [Configuration property reference](/apigee/docs/hybrid/v1.8/config-prop-ref).\n\nAdd SSD storage for production\n------------------------------\n\nFor the Cassandra database, the hybrid runtime only supports using\n[dynamically created](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#dynamic) persistent volumes to store data. Using *locally created* persistent\nvolumes is not supported.\n\nTo configure Cassandra properly for a hybrid production environment, you must configure a\n[StorageClass](https://kubernetes.io/docs/concepts/storage/storage-classes)\ndefinition that is backed by a solid-state drive (SSD) and make it the default\nclass. See [StorageClass configuration](/apigee/docs/hybrid/v1.8/cassandra-config) for detailed steps.\n| **Note**: The Cassandra database for hybrid should not use persistent volumes provisioned on network file system (NFS) or network-attached storage (NAS) systems."]]
