[jira] [Commented] (CASSANDRA-11071) Invalidate legacy schema CFSs at startup

["Mike Adamson (JIRA)" <ji...@apache.org>]

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

Mike Adamson commented on CASSANDRA-11071:
------------------------------------------

Here is a patch for this:
||cassandra-3.0||
|[branch|https://github.com/mike-tr-adamson/cassandra/tree/11071-cassandra-3.0]|
|[testall|http://cassci.datastax.com/view/Dev/view/madamson/job/mike-tr-adamson-11071-cassandra-3.0-testall/]|
|[dtests|http://cassci.datastax.com/view/Dev/view/madamson/job/mike-tr-adamson-11071-cassandra-3.0-dtest/]|
cc/ [~iamaleksey] was there a reason for not doing this?

> Invalidate legacy schema CFSs at startup
> ----------------------------------------
>
>                 Key: CASSANDRA-11071
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11071
>             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
(v6.3.4#6332)