O banco de dados do Cassandra usa volumes permanentes
criados dinamicamente para armazenar dados. Para o funcionamento adequado do banco de dados, a Apigee exige que você configure uma definição de StorageClass que seja baseada em uma unidade de estado sólido (SSD).
Se você não tiver o SSD configurado para o Cassandra, este tópico explica como criar um novo StorageClass que usa o SSD e torná-lo a classe padrão. Quando o Cassandra é iniciado, ele usa essa StorageClass padrão.
As etapas descritas neste tópico para a configuração do StorageClass são aplicáveis somente a uma nova
instalação do Cassandra. Se você já tiver uma classe do Cassandra instalada, precisará desativar o cluster
existente para configurar a definição do StorageClass. Não há suporte para alterações na definição do StorageClass de um
cluster existente do Cassandra após a instalação.
A Apigee recomenda implantar o modelo híbrido em duas ou mais regiões,
para desativar e reinstalar uma região,
preservando os dados na região secundária. Como alternativa, é possível usar um backup híbrido não CSI para restaurar
dados em uma instalação de região única, após a desativação e a configuração da definição do StorageClass necessária.
Alterar o StorageClass padrão
As etapas a seguir explicam como criar uma StorageClass e torná-la a classe padrão. Para mais informações, consulte
Alterar a classe de armazenamento padrão na documentação do Kubernetes.
Consiga o nome da StorageClass padrão atual:
kubectl get sc
Exemplo:
kubectl get sc
NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE
premium-rwo pd.csi.storage.gke.io Delete WaitForFirstConsumer true 15h
standard kubernetes.io/gce-pd Delete Immediate true 15h
standard-rwo (default) pd.csi.storage.gke.io Delete WaitForFirstConsumer true 15h
Descreva a StorageClass chamada standard-rwo. Observe que o tipo dela é pd-balanced:
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-08-18 UTC."],[],[],null,["# StorageClass configuration\n\nThe Cassandra database uses\n[dynamically created](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#dynamic) persistent volumes to store data. For proper database functioning,\nApigee requires you to configure a [StorageClass](https://kubernetes.io/docs/concepts/storage/storage-classes)\ndefinition that is backed by a solid-state drive (SSD).\n\n\nIf you do not currently have SSD configured for Cassandra, this topic explains how to create a\nnew StorageClass that uses SSD and make it the\ndefault class. When Cassandra starts, it will use this default StorageClass.\n| **KEY POINT:** Apigee requires the use of SSD for Cassandra.\n\nThe steps outlined in this topic for StorageClass configuration are only applicable to a *new*\nCassandra installation. If you already have a Cassandra class installed, you must decommission the existing\ncluster in order to configure the StorageClass definition. Changes to the StorageClass definition of an\nexisting Cassandra cluster after installation are not supported.\n\nApigee recommends deploying hybrid in [two or more regions](/apigee/docs/hybrid/v1.15/multi-region),\nin order to decommission and re-install one region\nwhile preserving data in the secondary region. Alternatively, you can use a [non-CSI hybrid backup](/apigee/docs/hybrid/v1.15/cassandra-backup-overview#how-to-take-backups) to restore\ndata in a single-region installation, after decommissioning and configuring the required StorageClass definition.\n\n\u003cbr /\u003e\n\nChange the default StorageClass\n-------------------------------\n\n\nThe following steps explain how to create a StorageClass and make it the default class. For more\ninformation, see [Change the default storage class](https://kubernetes.io/docs/tasks/administer-cluster/change-default-storage-class/) in the Kubernetes documentation.\n\n1. Get the name of the current default StorageClass: \n\n ```\n kubectl get sc\n ```\n\n\n For example: \n\n kubectl get sc\n NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE\n premium-rwo pd.csi.storage.gke.io Delete WaitForFirstConsumer true 15h\n standard kubernetes.io/gce-pd Delete Immediate true 15h\n standard-rwo (default) pd.csi.storage.gke.io Delete WaitForFirstConsumer true 15h\n \n2. Describe the StorageClass named `standard-rwo`. Note that its type is `pd-balanced`: \n\n ```\n kubectl describe sc standard-rwo\n ```\n\n\n For example: \n\n ```text\n kubectl describe sc standard-rwo\n ``` \n\n ```\n Name: standard-rwo\n IsDefaultClass: Yes\n Annotations: components.gke.io/layer=addon,storageclass.kubernetes.io/is-default-class=false\n Provisioner: pd.csi.storage.gke.io\n Parameters: type=pd-balanced\n AllowVolumeExpansion: True\n MountOptions: \u003cnone\u003e\n ReclaimPolicy: Delete\n VolumeBindingMode: WaitForFirstConsumer\n Events: \u003cnone\u003e\n ```\n3. Create a new file called `storageclass.yaml`.\n4. Add this code to the file. Note that the name of the new class is `apigee-sc`. You can use any name you like. Also, note that the storage type is `pd-ssd`: \n\n ```carbon\n ---\n kind: StorageClass\n apiVersion: storage.k8s.io/v1\n metadata:\n name: \"apigee-sc\"\n provisioner: pd.csi.storage.gke.io\n parameters:\n type: pd-ssd\n replication-type: none\n volumeBindingMode: WaitForFirstConsumer\n allowVolumeExpansion: true\n ```\n5. Apply the new StorageClass to your Kubernetes cluster: \n\n ```\n kubectl apply -f storageclass.yaml\n ```\n6. Execute the following two commands to change the default StorageClass: \n\n ```\n kubectl patch storageclass standard-rwo \\\n -p '{\"metadata\": {\"annotations\":{\"storageclass.kubernetes.io/is-default-class\":\"false\"}}}'\n ``` \n\n ```\n kubectl patch storageclass apigee-sc \\\n -p '{\"metadata\": {\"annotations\":{\"storageclass.kubernetes.io/is-default-class\":\"true\"}}}'\n ```\n7. Execute this command to verify that the new default StorageClass is called `apigee-sc`: \n\n ```\n kubectl get sc\n ```\n\n\n For example: \n\n kubectl get sc\n\n ```\n NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE\n apigee-sc (default) pd.csi.storage.gke.io Delete WaitForFirstConsumer true 14h\n premium-rwo pd.csi.storage.gke.io Delete WaitForFirstConsumer true 15h\n standard kubernetes.io/gce-pd Delete Immediate true 15h\n standard-rwo pd.csi.storage.gke.io Delete WaitForFirstConsumer true 15h\n \n ```\n8. Describe both the StorageClass to verify the value of **IsDefaultClass** . \n\n ```\n kubectl describe sc apigee-sc\n ``` \n\n ```\n Name: apigee-sc\n IsDefaultClass: Yes\n Annotations: kubectl.kubernetes.io/last-applied-configuration={\"allowVolumeExpansion\":true,\"apiVersion\":\"storage.k8s.io/v1\",\"kind\":\"StorageClass\",\"metadata\":{\"annotations\":{},\"name\":\"apigee-sc\"},\"parameters\":{\"replication-type\":\"none\",\"type\":\"pd-ssd\"},\"provisioner\":\"pd.csi.storage.gke.io\",\"volumeBindingMode\":\"WaitForFirstConsumer\"}\n ,storageclass.kubernetes.io/is-default-class=true\n Provisioner: pd.csi.storage.gke.io\n Parameters: replication-type=none,type=pd-ssd\n AllowVolumeExpansion: True\n MountOptions: \n ReclaimPolicy: Delete\n VolumeBindingMode: WaitForFirstConsumer\n Events: \n \n ``` \n\n ```\n kubectl describe sc standard-rwo\n ``` \n\n ```\n Name: standard-rwo\n IsDefaultClass: No\n Annotations: components.gke.io/layer=addon,storageclass.kubernetes.io/is-default-class=false\n Provisioner: pd.csi.storage.gke.io\n Parameters: type=pd-balanced\n AllowVolumeExpansion: True\n MountOptions: \n ReclaimPolicy: Delete\n VolumeBindingMode: WaitForFirstConsumer\n Events: \n \n ```"]]
