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
I've noticed that the k8ssandra-client does not fill the cluster_name field in cassandra.yaml. The ClusterInfo struct contains a field for the cluster name, but it doesn't seem to be used anywhere in the code. This leads to incorrect monitoring metrics from the exporter because it fills the cluster_name label according to the cassandra.yaml parameters.
Example:
❯ cassandra@damir-test-damir-test-dc-rack1-sts-0:/$ cat /etc/cassandra/cassandra.yaml | grep cluster_namecluster_name: Test Cluster❯ k get pods -n mynamespace -o yaml | grep CONFIG_FILE_DATA -A 1
- name: CONFIG_FILE_DATAvalue: '{"cassandra-env-sh":{"___OMITTED:___"cluster-info":{"name":"damir-test","seeds":"damir-test-seed-service,damir-test-damir-test-dc-additional-seed-service"},___OMITTED:___}'
Expected Behavior:
I believe the cluster_name field in cassandra.yaml should be properly filled by the k8ssandra_client.
Additional Information:
k8ssandra-client version: v0.2.0
The text was updated successfully, but these errors were encountered:
Issue Description:
I've noticed that the
k8ssandra-client
does not fill thecluster_name
field incassandra.yaml
. TheClusterInfo
struct contains a field for the cluster name, but it doesn't seem to be used anywhere in the code. This leads to incorrect monitoring metrics from the exporter because it fills thecluster_name
label according to thecassandra.yaml
parameters.Example:
Expected Behavior:
I believe the cluster_name field in cassandra.yaml should be properly filled by the k8ssandra_client.
Additional Information:
k8ssandra-client version: v0.2.0
The text was updated successfully, but these errors were encountered: