Benedict commented on CASSANDRA-7561:

Since this is holding up 2.1-rc6, I'm comfortable splitting the remainder of 
the fix out into a separate ticket. The code as it stands at least reduces the 
bug to a window of risk after DROP rather than a guaranteed failure.

> 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

Reply via email to