Open olim7t opened 7 months ago
I re-created the K8ssandraCluster
with spec.auth: false
to work around the authentication issue and cqlsh into the node:
cqlsh> select data_center from system.local;
data_center
-------------------
Cql_DåtåCenter1
(1 rows)
cqlsh> select * from system_schema.keyspaces;
keyspace_name | durable_writes | replication
--------------------+----------------+-------------------------------------------------------------------------------------------
system_auth | True | {'Cql_DåtåCenter1': '1', 'class': 'org.apache.cassandra.locator.NetworkTopologyStrategy'}
system_schema | True | {'class': 'org.apache.cassandra.locator.LocalStrategy'}
system_distributed | True | {'Cql_DåtåCenter1': '1', 'class': 'org.apache.cassandra.locator.NetworkTopologyStrategy'}
system | True | {'class': 'org.apache.cassandra.locator.LocalStrategy'}
system_traces | True | {'Cql_DåtåCenter1': '1', 'class': 'org.apache.cassandra.locator.NetworkTopologyStrategy'}
(5 rows)
cqlsh> select * from system_auth.roles;
NoHostAvailable:
The replication settings are correctly injected, it's the initial configuration of the DC name that failed. I think what's happening is that Cassandra readscassandra-rackdc.properties
using ISO8859-1 encoding, but we don't properly escape the value when we write that file:
$ cat /config/cassandra-rackdc.properties
dc=Cql_DåtåCenter1 # should be Cql_D\u00e5t\u00e5Center1
rack=Cql_Rack1
This is a cass-config-builder issue: datastax/cass-config-builder#53
EDIT -- and k8ssandra-client probably has the same bug, since this is what we now use for 4.1+ clusters.
(this assumes that #1252 is fixed first)
DC names can contain non-ASCII unicode characters, for example
Cql_DåtåCenter1
. But aK8ssandraCluster
with such a DC name gets stuck waiting for the DC to update:The following error shows up in the cass-operator logs:
And in the Cassandra pod's
server-system-logger
container:Trying to connect to the pod directly with CQLSH yields a similar error:
This suggests a problem with system keyspaces replication settings, although the annotation on the
K8ssandraCluster
looks correct:Note that this works correctly for a standalone
CassandraDatacenter
.┆Issue is synchronized with this Jira Story by Unito ┆Issue Number: K8OP-34