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

nagasree963_193876 avatar image
nagasree963_193876 asked ·

Does the cass-operator support cluster shutdown and startup?

Is cassandra-operator support on demand cluster shutdown and startup. If supports, how to achieve that one. I am using operator version: 1.3 and application version:3.11.6

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.

bradfordcp avatar image
bradfordcp answered ·

The CassandraDatacenter CRD has a stopped field which can scale your statefulsets down to 0 while keeping the data safe.


See the sample Custom Resource at https://github.com/datastax/cass-operator/blob/master/operator/example-cassdc-yaml/cassandra-3.11.6/example-cassdc-full.yaml#L62-L65

2 comments 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.

Thank you, It worked for me

0 Likes 0 · ·

Good to hear. For what it's worth, Chris Bradford is one of the authors of the cass-operator. Cheers!

0 Likes 0 · ·
Erick Ramirez avatar image
Erick Ramirez answered ·

The operation of the Cassandra pods is completely managed in a Kubernetes cluster. For example, if a C* instance goes down then it will be brought back online automatically.

In case I misunderstood your question, perhaps if you give us additional information on what you're trying to achieve then I'll update my answer accordingly. Cheers!

[UPDATE] Chris Bradford has provided instructions for stopping the statefulsets.

1 comment 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.

You misunderstand my question, You are telling about when pod goes down. I will explain it again. Does the operator support on demand shutdown or startup? I am working on a scenario where the db cluster needs to stop and start up as required.I know there is always kubectl delete cr.yaml command, which would obviously destroy all the pods. But then to start them up again, I would have to use kubectl apply command again right? Is there a functionality by which the cluster can be stopped (in place of getting completely destroyed) and then started up again?

0 Likes 0 · ·