You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "T Jake Luciani (JIRA)" <ji...@apache.org> on 2015/11/24 15:18:10 UTC
[jira] [Updated] (CASSANDRA-9249) Resetting local schema can cause
assertion error
[ https://issues.apache.org/jira/browse/CASSANDRA-9249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
T Jake Luciani updated CASSANDRA-9249:
--------------------------------------
Component/s: Distributed Metadata
> Resetting local schema can cause assertion error
> ------------------------------------------------
>
> Key: CASSANDRA-9249
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9249
> Project: Cassandra
> Issue Type: Bug
> Components: Distributed Metadata
> Reporter: T Jake Luciani
> Assignee: T Jake Luciani
> Priority: Minor
> Fix For: 2.0.15, 2.1.6, 2.2.0 beta 1
>
> Attachments: 9249fix.txt
>
>
> When a user resets their local schema the Schema class purges all CFmetadata and recreates it. If a compaction is going on this can cause an issue similar to CASSANDRA-8332
> The original intent of the assertion was to ensure if the setLiveMetadata was never called with different metadata instances since the schema is managed as a global reference. However I missed this reset method so it's probably just as well to remove this assert.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)