You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Philip Thompson (JIRA)" <ji...@apache.org> on 2015/06/22 18:11:00 UTC
[jira] [Commented] (CASSANDRA-9628) "Unknown keyspace
system_traces" exception when using nodetool on a new cluster
[ https://issues.apache.org/jira/browse/CASSANDRA-9628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14596133#comment-14596133 ]
Philip Thompson commented on CASSANDRA-9628:
--------------------------------------------
I'm unable to reproduce this with 2.1.2. Are you running into the issue on a newer version (2.1.5 or 2.1.6)?
> "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: Core
> Reporter: tzach
> 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)