[ https://issues.apache.org/jira/browse/CASSANDRA-7784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132641#comment-14132641 ]
Benedict commented on CASSANDRA-7784: ------------------------------------- Any news on a patch for this? We should really have got this into 2.1.0, but should definitely fix it for 2.1.1 > 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 > > 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)