Configure Cassandra for production

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

Version 1.5 (unsupported)

   Supported versions:

• v1.13 (latest)                        
• v1.12                         
• v1.11                         
• List of supported versions

   Unsupported versions:

• v1.10                                      
• v1.9                                         
• v1.8                                         
• v1.7                                         
• v1.6                                         
• v1.5                                         
• v1.4                                         
• v1.3                                         
• v1.2                                         
• v1.1                                         

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 also Scaling 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, hybrid runtime uses dynamically created persistent volumes to store data. To configure Cassandra properly for a 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.