Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 3 Jun 2015 22:19:38 +0000 (UTC)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12761851.1418676131000.4991.1433369978662@Atlassian.JIRA>
In-Reply-To: <JIRA.12761851.1418676131000@Atlassian.JIRA>
References: <JIRA.12761851.1418676131000@Atlassian.JIRA>
 <JIRA.12761851.1418676131545@arcas>
Subject: [jira] [Commented] (CASSANDRA-8487) system.schema_columns sometimes
 missing for 'system' keyspace
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-8487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14571751#comment-14571751 ] 

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