[
https://issues.apache.org/jira/browse/CASSANDRA-9628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15022940#comment-15022940
]
Carl Yeksigian commented on CASSANDRA-9628:
-------------------------------------------
I'm not sure how else we would not have a {{system_traces}} keyspace, as we
will always either stream it during bootstrap or add it when we are ready to
join the cluster, so I think it is. Unfortunately, I haven't been able to
reproduce this issue, so I can't verify that is the issue.
> "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
> 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)
