cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CASSANDRA-8487) system.schema_columns sometimes missing for 'system' keyspace
Date Mon, 15 Dec 2014 21:58:14 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-8487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Aleksey Yeschenko reassigned CASSANDRA-8487:
--------------------------------------------

    Assignee: Aleksey Yeschenko

> 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)

Mime
View raw message