[
https://issues.apache.org/jira/browse/CASSANDRA-9018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377828#comment-14377828
]
Philip Thompson commented on CASSANDRA-9018:
--------------------------------------------
So your expected behavior is not quite the actual expected behavior. When you
call {{DROP KEYSPACE}}, the data is snapshotted automatically. There are no
tombstones or gcgs to deal with. That snapshot will remain until you, the
operator deletes it.
> Dropped keyspace is not collected
> ---------------------------------
>
> Key: CASSANDRA-9018
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9018
> Project: Cassandra
> Issue Type: Bug
> Reporter: Maxim Podkolzine
> Attachments: cassandra-log.zip
>
>
> As far as I understand when a keyspace is dropped, the data is marked as
> tombstone. We expect that after the grace period (all tables are created with
> gc_grace_seconds=7200), this data is automatically removed during the
> compaction process, which means that keyspace no longer takes any space on
> disk.
> This is not happening (not after 2 or 24 hours). The log keeps saying "No
> files to compact for user defined compaction", keyspace files remain on disk.
> It's not clear whether Cassandra is still waiting for certain event, or
> decided not to collect the data.
> Is there any setting that I missed? Any clues to figure out from the log,
> what's the current state.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
