[ 
https://issues.apache.org/jira/browse/CASSANDRA-9628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057240#comment-15057240
 ] 

David Wood commented on CASSANDRA-9628:
---------------------------------------

Hello,

I'm using Cassandra v2.1.8.  I can re-create this problem if I include the 
following settings in cassandra.yaml:

{code}
authenticator: AllowAllAuthenticator
authorizer: AllowAllAuthorizer
{code}

If I comment them out and re-start Cassandra then the problem goes away.  
Strangely, the above settings are supposedly the defaults:

https://docs.datastax.com/en/cassandra/2.1/cassandra/configuration/configCassandra_yaml_r.html

David


> "Unknown keyspace system_traces" exception when using nodetool on a new 
> cluster
> -------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-9628
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9628
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>            Reporter: tzach
>            Assignee: Carl Yeksigian
>            Priority: Minor
>
> When creating a new cluster from scratch,  nodetool status fails on 
> system_traces as follow
> {code}
> $ nodetool status
> error: Unknown keyspace system_traces
> -- StackTrace --
> java.lang.AssertionError: Unknown keyspace system_traces
>       at org.apache.cassandra.db.Keyspace.<init>(Keyspace.java:270)
>       at org.apache.cassandra.db.Keyspace.open(Keyspace.java:119)
>       at org.apache.cassandra.db.Keyspace.open(Keyspace.java:96)
> ...
> {code}
> the problem disappear when creating an empty keyspace
> {code}
> cqlsh> create keyspace temp WITH REPLICATION = { 'class' : 'SimpleStrategy', 
> 'replication_factor' : 2 };
> {code}
> My guess is system_traces initialization complete only after any data 
> insertion.
> Before it does, any attempt to read  from it either from nodetool, cqlsh or 
> streaming to a new node will fail.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to