cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Adamson (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-11071) Invalidate legacy schema CFSs at startup
Date Wed, 27 Jan 2016 13:16:39 GMT


Mike Adamson commented on CASSANDRA-11071:

[~iamaleksey] Yes, it fixes an inconsistency between the tables returned by {{cqlsh> describe
tables;}} and {{nodetool tablesstats}}.

> Invalidate legacy schema CFSs at startup
> ----------------------------------------
>                 Key: CASSANDRA-11071
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Distributed Metadata, Lifecycle
>            Reporter: Sam Tunnicliffe
>            Assignee: Mike Adamson
>            Priority: Minor
>             Fix For: 3.0.x, 3.x
> {{ColumnFamilyStore}} instances are created for legacy schema tables at startup when
{{SystemKeyspace}} is initialized as they may be required for schema migration during upgrade.
Before startup completes, the schema info for these is expunged from {{system_schema}}, but
the {{CFS}} instances are not invalidated, which leaves their mbeans registered and visible
via nodetool & JMX.

This message was sent by Atlassian JIRA

View raw message