Bringing together the Apache Cassandra experts from the community and DataStax.

Want to learn? Have a question? Want to share your expertise? You are in the right place!

Not sure where to begin? Getting Started

 

question

Ckn avatar image
Ckn asked Erick Ramirez answered

Why does the cass-operator not support storage expansion?

ref Issue: https://github.com/datastax/cass-operator/issues/390

Why it is not supported?

cass-operator
10 |1000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

1 Answer

Erick Ramirez avatar image
Erick Ramirez answered

Jim Dickinson already answered this question in issue #390 you referenced so I'm going to re-post his answer here.

Attempts to change StorageConfig is blocked because the StatefulSet also doesn't allow changes to the PersistentVolumeClaim.

If a pod has run out of disk space, it is possible to workaround it by resizing the underlying volume provided it is supported in your environment. For example, public cloud providers allow volumes to be resized in certain configurations. You will need to consult the documentation of the relevant cloud provider for details.

Be aware that this workaround can be risky since it means that the underlying volume will be out of sync with the CassandraDatacenter, StatefulSet and/or PersistentVolumeClaim definitions. When you scale up the DC at a later date, the volume will be the originally defined size. Cheers!

Share
10 |1000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.