cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8487) system.schema_columns sometimes missing for 'system' keyspace
Date Wed, 03 Jun 2015 22:19:38 GMT


Aleksey Yeschenko commented on CASSANDRA-8487:

The tables will always be there - they are hardcoded. You will always be able to query all
system tables.

Persistence of them into the on-disk data dictionary, though, for some reason seems to not
work sometimes.

Seems like all system.* tables are sometimes missing from columnfamilies/columns, which probably
means some timestamp related issue.

> system.schema_columns sometimes missing for 'system' keyspace
> -------------------------------------------------------------
>                 Key: CASSANDRA-8487
>                 URL:
>             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

View raw message