[
https://issues.apache.org/jira/browse/CASSANDRA-9628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15045766#comment-15045766
]
Ariel Weisberg commented on CASSANDRA-9628:
-------------------------------------------
OK. I am +1 to close as not reproducible and reopen if it comes up again. It's
not that I think it's gone, but as an investment of developer time it doesn't
seem worth it if it can't be reproduced when compared to all the other bugs we
could make progress on that may be reproducible and higher impact.
> "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
> Fix For: 2.1.x
>
>
> 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)
