CODEWITHSUNDEEP
kubernetescassandrakubernetes-statefulsetkubernetes-pvccass-operator
user9607927
user9607927

Reputation:

Why is expanding/reducing StorageConfig volume size retricted in cass-operator?

Why there is restriction while expanding and reducing the storage config size in cassandra operator- Datastax

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

Why there is a validation/restriction in statefulset for expanding storage config?

Upvotes: 1

Views: 297

Answers (1)

Erick Ramirez
Erick Ramirez

Reputation: 16353

The exact same question was asked on https://community.datastax.com/questions/12269/ so I'm reposting my answer here.

Jim Dickinson already answered this question in issue #390 you referenced.

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.

Note that we aim to document a workaround for the cass-operator in K8ssandra.io. Cheers!

Upvotes: 2

Related Questions