Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 27 Jan 2016 12:49:39 +0000 (UTC)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12934102.1453813245000.224024.1453898979908@Atlassian.JIRA>
In-Reply-To: <JIRA.12934102.1453813245000@Atlassian.JIRA>
References: <JIRA.12934102.1453813245000@Atlassian.JIRA>
 <JIRA.12934102.1453813245929@arcas>
Subject: [jira] [Commented] (CASSANDRA-11071) Invalidate legacy schema CFSs
 at startup
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Aleksey Yeschenko commented on CASSANDRA-11071:
-----------------------------------------------

[~mikea] This is just cosmetic, right? I don't think there was any reason. It's just a minor oversight.

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