John Sanda
John Sanda
@jpicara Were you able to upgrade the management-api and apply the filters? If so, did it resolve your issue?
@Miles-Garnsey Can you look into this? The collectd log reports that metrics were dropped after the low water mark was reached. I am curious as to whether this is related...
@emerkle826 can you please provide a planning poker estimate.
@sri-postgres-cassandra What OS/arch are you running on?
What in particular are you looking for?
Thanks for creating the issue. I actually did some work a while back to support using a read-only root file system. It's at https://github.com/k8ssandra/cass-operator/pull/218. We are definitely going to revisit...
I'll try to write something up. It shouldn't take very long. It'll make me feel productive 😄
It does require a rolling restart. Can't we add additional seeds up front if we are dealing with a K8ssandraCluster deployment so as to avoid rolling restarts? Then don't add...
After further investigation, it is appear that this behavior is caused from having auth enabled. With auth enabled there is a StatefulSet update that happens after the C* pod is...
The problem stems from this part of the `cassdc.yaml` template: ``` additional-jvm-opts: {{- if .Values.cassandra.auth.enabled }} - "-Dcassandra.system_distributed_replication_dc_names={{ $datacenter.name }}" - "-Dcassandra.system_distributed_replication_per_dc={{ min 5 $datacenter.size }}" {{- end }} ```...