cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Tunnicliffe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-11071) Invalidate legacy schema CFSs at startup
Date Mon, 01 Feb 2016 08:33:39 GMT

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

Sam Tunnicliffe updated CASSANDRA-11071:
----------------------------------------
    Reviewer: Sam Tunnicliffe

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

Mime
View raw message