[
https://issues.apache.org/jira/browse/CASSANDRA-9018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377620#comment-14377620
]
Maxim Podkolzine commented on CASSANDRA-9018:
---------------------------------------------
It's 2.1.1.
No, I can't be sure of that, maybe the files are kept for a reason. But I
didn't do anything specific using a command line, and as I said the log does
not explain much.
Essentially the keyspace was created along with the tables, some data was
inserted, and then it was dropped.
According to the yaml data is not incrementally backed up:
"incremental_backups: false"
I do see "auto_snapshot: true", but that only reason for that is because the
doc STRONGLY advised 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)
