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
auto_snapshot=true & auto_snapshot_ttl: '30d' are default values of cassandra.yaml file that is getting installed with this helm chart.
This creating excessive burden on Cassandra cluster even failing jobs that run 3-4 times in a hr. Also on storage too when combined occupying space of snapshots of all nodes in cassandra cluster.
In our case, we temporary put data on cassandra for instant processing & truncate everything after each job successful. So we do not need snapshots at all & data loss is not a worry.
What is the feature you are proposing to solve the problem?
Can we please have a feature in values.yaml file to disable/control auto_snapshots & TTL values?
What alternatives have you considered?
We cannot just use custom cassandra.yaml disabling auto_snapshots through existingConfiguration from values.yaml using configmap .
It collides with seed_provider, listen_address, broadcast_rpc_address in cassandra.yaml which has values that are binded to each cassandra node hostname which failing cassandra deployment. Leaving these values blank also had unsuccessful deployment. Correct me if I'm wrong if there's a way to have customconfiguration with configmap & have successful deployment of helm chart. Thanks.
The text was updated successfully, but these errors were encountered:
Name and Version
chart version: 10.12.1
What is the problem this feature will solve?
auto_snapshot=true & auto_snapshot_ttl: '30d' are default values of cassandra.yaml file that is getting installed with this helm chart.
This creating excessive burden on Cassandra cluster even failing jobs that run 3-4 times in a hr. Also on storage too when combined occupying space of snapshots of all nodes in cassandra cluster.
In our case, we temporary put data on cassandra for instant processing & truncate everything after each job successful. So we do not need snapshots at all & data loss is not a worry.
What is the feature you are proposing to solve the problem?
Can we please have a feature in values.yaml file to disable/control auto_snapshots & TTL values?
What alternatives have you considered?
We cannot just use custom cassandra.yaml disabling auto_snapshots through existingConfiguration from values.yaml using configmap .
It collides with seed_provider, listen_address, broadcast_rpc_address in cassandra.yaml which has values that are binded to each cassandra node hostname which failing cassandra deployment. Leaving these values blank also had unsuccessful deployment. Correct me if I'm wrong if there's a way to have customconfiguration with configmap & have successful deployment of helm chart. Thanks.
The text was updated successfully, but these errors were encountered: