Hi! Is it possible to place pods in different storage locations using different SCs? And keep it that way on a rack level?
Example:
rack1 - sc1
rack2 - sc2
rack3 - sc3
Thanks,
Vladimir
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
Hi! Is it possible to place pods in different storage locations using different SCs? And keep it that way on a rack level?
Example:
rack1 - sc1
rack2 - sc2
rack3 - sc3
Thanks,
Vladimir
Hi @mzv
You can configure the storage class but it applies to all Cassandra pods. Here is an example:
apiVersion: cassandra.datastax.com/v1beta1 kind: CassandraDatacenter metadata: name: dc2 spec: clusterName: example serverType: cassandra serverVersion: "3.11.7" managementApiAuth: insecure: {} size: 9 storageConfig: cassandraDataVolumeClaimSpec: storageClassName: server-storage accessModes: - ReadWriteOnce resources: requests: storage: 500Gi racks: - name: r1 nodeAffinityLabels: topology.kubernetes.io/zone: us-east1-a - name: r2 nodeAffinityLabels: topology.kubernetes.io/zone: us-east1-b - name: r3 nodeAffinityLabels: topology.kubernetes.io/zone: us-east1-c
In general I would advise against using different settings across nodes within a single DC. You will have replicas in each rack. Let's say you used faster storage in r1 and in r2. This could lead to performance problems with replicas in r3.
If you want to use different resources for some nodes, then I would consider putting those nodes into a separate DC.
Cheers
John
5 People are following this question.
Are there plans to support multi-region with the Cassandra operator?
Does the cass-operator support rolling upgrade?
How can we connect to Cassandra from outside the Kubernetes cluster?
How do I revert changes to a pod in CrashLoopBackOff status?
Error installing K8ssandra with Helm: CassandraDatacenter "dc1" in namespace "default" exists
DataStax Enterprise is powered by the best distribution of Apache Cassandra ™
© 2022 DataStax, Titan, and TitanDB are registered trademarks of DataStax, Inc. and its subsidiaries in the United States and/or other countries.
Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries.
Privacy Policy Terms of Use