[FOLLOW UP QUESTION TO #6379]
okay. What I want to know actually, there is a field called "size", where it indicates number of nodes. It is a way of horizontal scaling. Is there any way for vertical scaling (increase of CPU/memory).
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
okay. What I want to know actually, there is a field called "size", where it indicates number of nodes. It is a way of horizontal scaling. Is there any way for vertical scaling (increase of CPU/memory).
To add to Saravanan's answer, you need to edit the configuration of your cluster using the kubectl edit
command. For example:
$ kubectl -n cass-operator edit cassdc dc1
You will need to reconfigure the resources
allocated to the nodes. Here is an example allocation in the cassandra-3.11.6/example-cassdc-full.yaml
YAML on GitHub:
resources: requests: memory: 24Gi cpu: 6000m limits: memory: 24Gi cpu: 6000m
When you save the configuration, the cass-operator will apply the changes and perform a rolling restart. Cheers!
Please see the Resources section in the cass-operator yaml
You have the ability to control how much cpu and memory you can allot to each pod. In our case each pod is like a node.
6 People are following this question.
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