[
https://issues.apache.org/jira/browse/CASSANDRA-8487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14571775#comment-14571775
]
Kishan Karunaratne commented on CASSANDRA-8487:
-----------------------------------------------
I'm able to repro the issue about 50% of the time on Windows when I start up a
CCM cluster. Checking the system tables metadata in the python driver just
outputs an empty dict:
{noformat}
print cluster.metadata.keyspaces['system'].tables
{}
{noformat}
> system.schema_columns sometimes missing for 'system' keyspace
> -------------------------------------------------------------
>
> Key: CASSANDRA-8487
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8487
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Adam Holmberg
> Assignee: Aleksey Yeschenko
> Priority: Minor
>
> Occasionally a Cassandra node will have missing schema_columns information
> where keyspace_name='system'.
> {code}
> cqlsh> select * from system.schema_columns where keyspace_name='system';
> keyspace_name | columnfamily_name | column_name
> ---------------+-------------------+-------------
> (0 rows)
> {code}
> All keyspace and column family schema info is present for 'system' -- it's
> only the column information missing.
> This can occur on an existing cluster following node restart. The data
> usually appears again after bouncing the node.
> This is impactful to client drivers that expect column meta for configured
> tables.
> Reproducible in 2.1.2. Have not seen it crop up in 2.0.11.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
