[
https://issues.apache.org/jira/browse/CASSANDRA-7784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14135100#comment-14135100
]
Benedict commented on CASSANDRA-7784:
-------------------------------------
Ah, yes, I see the confusing part is that it hasn't been replaced in a place
where it could have been, but the second usage is a place where it _couldn't_
be. It would be clearer if the first usage was replaced, so it were more
obvious. Possibly also dropping the UUID from the parameter list. But no biggy
> DROP table leaves the counter and row cache in a temporarily inconsistent
> state that, if saved during, will cause an exception to be thrown
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-7784
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7784
> Project: Cassandra
> Issue Type: Bug
> Reporter: Benedict
> Assignee: Aleksey Yeschenko
> Priority: Minor
> Fix For: 2.1.1
>
> Attachments: 7784.txt
>
>
> It looks like this is quite a realistic race to hit reasonably often, since
> we forceBlockingFlush after removing from Schema.cfIdMap, so there could be a
> lengthy window to overlap with an auto-save
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
