Thanks. I am making a personal project so stopping K8S isn’t an issue for me
personally.
The reason I asked about stopping K8S is because I could run the `kubectl edit`
command on the cass-operator...yaml file but not on example..yaml file. As the
configuration is in the example...yaml file, I
Is it possible you don't have the k8s cluster running?
To answer your question, you can edit your k8s cluster configuration with
the new settings and the cass-operator will apply the changes then it will
perform a rolling restart of the pods for the changes to take effect.
Cheers!
>
Thanks. Would I need to delete and restart the Kubernetes cluster for the
configurations to apply?
Sorry, new to K8S as well so not sure how to go about doing it. It seems I can
edit the cass-oprator-manifests yaml but that is not the file which needs
editing. When I edit the example-cassdc
Yes, you're right -- you need to override the defaults by specifying the
configuration in the operator yaml spec:
spec:
...
config:
cassandra-yaml:
...
commitlog_sync: batch
...
Cheers!
On Mon, 27 Jul 2020 at 03:08, Manu Chadha wrote:
> Hi
>
>
>
> I am using
Hi
I am using cass-operator to run Cassandra in Kubernetes. I am also using
ScalarDB to provide ACID support in Cassandra.
One pre-requisite for ScalarDB is to change the commitlog_sync to batch.
“Change commitlog_sync from periodic to batch in cassandra.yaml not to lose
data when quorum of