Proses ini memungkinkan Anda memperluas volume persisten yang digunakan oleh database Cassandra hibrida Apigee untuk mengakomodasi kebutuhan penyimpanan yang lebih besar tanpa perlu membuat node baru hanya untuk menyediakan penyimpanan yang lebih besar.
Komponen cassandra campuran Apigee menggunakan volume persisten untuk menyimpan data. Ukuran
volume persisten ditentukan selama penginstalan dan konfigurasi awal. Ukuran penyimpanan awal ini adalah nilai yang tidak dapat diubah dan tidak dapat diubah. Oleh karena itu, setiap node baru yang ditambahkan ke cluster
akan menggunakan ukuran volume persisten yang sama.
Anda dapat meningkatkan ukuran volume persisten yang ada dengan melakukan perubahan langsung pada
Klaim volume persisten, tetapi node baru akan tetap menggunakan ukuran volume persisten awal yang lebih kecil.
Jika database Cassandra hibrida Anda mendekati kapasitas penyimpanannya, Anda dapat menggunakan prosedur ini
untuk memperluas volume persisten yang ada dan mengizinkan node baru untuk memperluas volume persistennya juga.
Proses
Sebelum melanjutkan ekspansi volume Persistent, pastikan "allowVolumeExpansion: true"
disetel di StorageClass saat dibuat:
kubectl get sc standard -o json | jq .allowVolumeExpansion true
Perbarui Ukuran volume untuk Konfigurasi Volume Persisten (PVC) yang ada:
Mulai ulang pod Cassandra secara bertahap untuk mencerminkan ukuran baru. Hapus pod Cassandra satu per satu. Pastikan statefulset berfungsi dengan baik sebelum melanjutkan ke node berikutnya:
kubectl -n apigee delete pod apigee-cassandra-2
kubectl -n apigee get sts
NAME READY AGE
apigee-cassandra 3/3 64s
Pastikan pod Cassandra muncul dengan ukuran volume baru:
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-21 UTC."],[[["\u003cp\u003eThe Apigee hybrid documentation version 1.2 is end-of-life, and users should upgrade to a newer version for continued support and updates, as detailed in the supported versions documentation.\u003c/p\u003e\n"],["\u003cp\u003eYou can expand the storage capacity of the Apigee hybrid Cassandra database by increasing the size of existing persistent volumes without needing to create new nodes for storage alone.\u003c/p\u003e\n"],["\u003cp\u003eTo expand the persistent volume, ensure \u003ccode\u003eallowVolumeExpansion\u003c/code\u003e is set to true in the StorageClass, update the Persistent Volume Claim (PVC) size, and then update the overrides.yaml file with the new capacity.\u003c/p\u003e\n"],["\u003cp\u003eAfter updating the PVC and \u003ccode\u003eoverrides.yaml\u003c/code\u003e, delete the Cassandra statefulset without cascading, apply the updated configuration, and then perform a rolling restart of the Cassandra pods to apply the changes.\u003c/p\u003e\n"],["\u003cp\u003eAfter all the changes are applied, verify the pods are correctly initialized and the new volume size is visible in the persistent volume claims.\u003c/p\u003e\n"]]],[],null,["# Expand Cassandra persistent volumes\n\n| You are currently viewing version 1.2 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\nThis process allows you to expand the persistent volumes used by the Apigee hybrid Cassandra\ndatabase to accommodate greater storage needs without needing to create new nodes just to provide\nmore storage.\n\nThe Apigee hybrid `cassandra` component uses persistent volumes to store data. The size\nof the persistent volume is defined during installation and initial configuration. This initial\nstorage size is an immutable value and cannot be changed. Therefore, any new node added to the cluster\nwill use the same persistent volume size.\n\nIt is possible to increase the size of the existing persistent volume by making the changes directly on\nthe Persistent volume Claim, but new nodes will still use the smaller initial persistent volume size.\n\nIf your hybrid Cassandra database is nearing its storage capacity, you can use this procedure\nto expand the existing persistent volumes and allow new nodes to expand their persistent volumes as\nwell.\n\nProcess\n-------\n\n1. Before proceeding with the Persistent volume expansion, make sure \"`allowVolumeExpansion: true`\" is set on the StorageClass when it is created: \n\n ```\n kubectl get sc standard -o json | jq .allowVolumeExpansion true\n ```\n2. Update the Volume size for the existing Persistent Volume Configuration (PVC): \n\n ```\n kubectl -n apigee edit pvc \n ```\n3. Delete the statefulset without cascading deletion: \n\n ```\n kubectl -n apigee delete sts --cascade=false apigee-cassandra\n ```\n4. Update the overrides.yaml and apply the changes: \n\n ```actionscript-3\n cassandra:\n storage:\n capacity: 20Gi\n ``` \n\n ```\n ./apigeectl apply -c cassandra -f overrides.yaml\n ```\n5. Rolling restart the Cassandra pods to reflect the new size. Delete the Cassandra pods one at a time. Verify that the statefulset is healthy before proceeding to the next nodes: \n\n kubectl -n apigee delete pod apigee-cassandra-2\n kubectl -n apigee get sts\n NAME READY AGE\n apigee-cassandra \u003cvar translate=\"no\"\u003e3/3\u003c/var\u003e 64s\n\n6. Verify the Cassandra pods are coming up with the new volume size: \n\n ```\n kubectl -n apigee get pvc\n ```"]]
