cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-7233) Dropping a keyspace fails to purge the Key Cache resulting in SSTable Corruption during searches
Date Tue, 20 May 2014 21:17:38 GMT

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

Tyler Hobbs edited comment on CASSANDRA-7233 at 5/20/14 9:17 PM:
-----------------------------------------------------------------

CASSANDRA-6525 will help with this in 2.0.


was (Author: thobbs):
CASSANDRA-6525 will help will this in 2.0.

> 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