cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-7233) Dropping a keyspace fails to purge the Key Cache resulting in SSTable Corruption during searches
Date Wed, 14 May 2014 20:55:50 GMT

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

Brandon Williams resolved CASSANDRA-7233.
-----------------------------------------

    Resolution: Won't Fix

bq. One of our workflows involves dropping a full keyspace (with column families) and re-creating
it

The answer here is "don't do that" before CASSANDRA-5202

> Dropping a keyspace fails to purge the Key Cache resulting in SSTable Corruption during
searches
> ------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-7233
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7233
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Vinoo Ganesh
>             Fix For: 1.2.17
>
>
> Dropping a keyspace fails to purge the Key Cache resulting in SSTable corruption during
searches.
> Dropping a full keyspace (with column families) and re-creating that same keyspace (with
column families) without restarting Cassandra causes searches to print out CorruptSSTable
messages. This has to do with the fact that keys that reference the deleted data persist in
the key cache after the data has been deleted. Could we have the key cache automatically invalidated
when for data that is dropped? 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message