cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Thompson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9018) Dropped keyspace is not collected
Date Tue, 24 Mar 2015 14:23:53 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-9018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377921#comment-14377921
] 

Philip Thompson commented on CASSANDRA-9018:
--------------------------------------------

[~maximp], for advice on better settings, try asking the cassandra user mailing list, unfortunately
I'm not sure what would be the best settings in your case. For discussions on changing or
improving the existing behavior, either open a new ticket labeled "improvement" or start a
discussion on the cassandra dev mailing list.

> 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)

Mime
View raw message