[
https://issues.apache.org/jira/browse/CASSANDRA-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-3116:
--------------------------------------
Attachment: 3116-v2.txt
bq. only remove the one that are not compacting
done. (renamed removeAllSSTables to unreferenceSSTables, which could still
stand improvement...)
bq. removing any flushed memtable ... also that replacements are directly
marked as compacted too
done (both by ultimately funneling through the replace method)
bq. we could make sure no new compaction is automatically triggered on an
invalidated CF
this shouldn't be a problem, if it happens. I'd rather not go to extra effort
to prevent something harmless.
v2 also gets rid of CFS.flushlock (we already flush for the drop snapshot) and
removes CFS.isDropped in favor of isValid.
> Compactions can (seriously) delay schema migrations
> ---------------------------------------------------
>
> Key: CASSANDRA-3116
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3116
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7.0
> Reporter: Eric Evans
> Assignee: Jonathan Ellis
> Labels: compaction
> Fix For: 1.1
>
> Attachments: 3116-v2.txt, 3116.txt
>
>
> A compaction lock is acquired when dropping keyspaces or column families
> which will cause the schema migration to block if a compaction is in progress.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
