You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How can I disable casskop cassandra reconcilation to be able to set the cassandra statefulset debuglog to true ?
Question
What did you do?
I have a running setup with cassandra and casskop. I want to debug cassandra by activating the debug logs.
I edited the cassandra statefulset. Set "logback-xml":{"debuglog-enabled":true}}.
What did you expect to see?
I expected cassandra statefulset to remain with the setting I edited.
What did you see instead? Under which circumstances?
After updating "logback-xml":{"debuglog-enabled":true}}. the statefulset restarted. It came back up. But then it restarted again and debuglog was set back to false: "logback-xml":{"debuglog-enabled":false}}.
I saw in the casskop logs that it started some reconciliation logic and restarted the cassandra statefulset.
You can't disable the reconcile loop. The only way for you is to update your cluster's configuration in order to take that change into account. Nodes' configuration can be updated at different levels:
cluster
datacenter
rack
If it's a production cluster, I would change it only in one of your racks by doing something like this:
Type of question
How can I disable casskop cassandra reconcilation to be able to set the cassandra statefulset debuglog to true ?
Question
What did you do?
I have a running setup with cassandra and casskop. I want to debug cassandra by activating the debug logs.
I edited the cassandra statefulset. Set "logback-xml":{"debuglog-enabled":true}}.
What did you expect to see?
I expected cassandra statefulset to remain with the setting I edited.
What did you see instead? Under which circumstances?
After updating "logback-xml":{"debuglog-enabled":true}}. the statefulset restarted. It came back up. But then it restarted again and debuglog was set back to false: "logback-xml":{"debuglog-enabled":false}}.
I saw in the casskop logs that it started some reconciliation logic and restarted the cassandra statefulset.
Environment
casskop version:
ghcr.io/cscetbon/casskop:2.2.4
Kubernetes version information:
kubectl version
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.4", GitCommit:"b695d79d4f967c403a96986f1750a35eb75e75f1", GitTreeState:"clean", BuildDate:"2021-11-17T15:48:33Z", GoVersion:"go1.16.10", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.4", GitCommit:"b695d79d4f967c403a96986f1750a35eb75e75f1", GitTreeState:"archive", BuildDate:"2024-08-16T07:55:20Z", GoVersion:"go1.16.10", Compiler:"gc", Platform:"linux/amd64"}
Kubernetes cluster kind:
Cassandra version:
ReleaseVersion: 4.1.5
Additional context
Add any other context about the question here.
The text was updated successfully, but these errors were encountered: