You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Benedict (JIRA)" <ji...@apache.org> on 2014/08/15 19:45:20 UTC

[jira] [Commented] (CASSANDRA-7561) On DROP we should invalidate CounterKeyCache as well as Key/Row cache

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

Benedict commented on CASSANDRA-7561:
-------------------------------------

bq. Well. It shouldn't be throwing any exceptions, AFAIK

CounterCacheKey.getPathInfo() is called during serialization, which is not safe if the CF has been dropped (since it will get a null cf back). So we still need to address preventing an autosave happening whilst the map contains keys that are in a dropped CF, or we need getPathInfo() at least to be safe during this (and return a result that is valid for all use cases), whichever is easiest.

> On DROP we should invalidate CounterKeyCache as well as Key/Row cache
> ---------------------------------------------------------------------
>
>                 Key: CASSANDRA-7561
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7561
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Benedict
>            Assignee: Aleksey Yeschenko
>            Priority: Minor
>             Fix For: 2.1.0
>
>         Attachments: 7561.txt
>
>
> We should also probably ensure we don't attempt to auto save _any_ of the caches while they are in an inconsistent state (i.e. there are keys present to be saved that should not be restored, or that would throw exceptions when we save (e.g. CounterCacheKey))



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