I'm a running cassandra in kuberentes and I have used the cassandra operator 1.0 provided by datastax.
Are you aware of any issue about superuser after some time not being to connect using the usual password?
I'm a running cassandra in kuberentes and I have used the cassandra operator 1.0 provided by datastax.
Are you aware of any issue about superuser after some time not being to connect using the usual password?
it's not a behaviour I would expect. Can you give more details about the connection failure? Are you connecting via cqlsh? Are the pods fully up and running?
Hi @acucciarre_144605, are the security keyspaces data fully repaired and having enough replication? Could you provide the commands and the stack trace (from the console as well as from the logs files) here that could help identify the problem?
This isn't normal behaviour for nodes built with the cass-operator so I suspect that the STS ran into some problems and got terminated.
You should check the pods to see if they got replaced. The quickest way to tell is by checking the running time on the pods:
$ kubectl -n cass-operator get pods
Otherwise, confirm that the secret you have is valid and correct. Cheers!
7 People are following this question.
DataStax Enterprise is powered by the best distribution of Apache Cassandra ™
© 2023 DataStax, Titan, and TitanDB are registered trademarks of DataStax, Inc. and its subsidiaries in the United States and/or other countries.
Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries.
Privacy Policy Terms of Use