cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-6280) Snapshots for dropped column families management
Date Thu, 31 Oct 2013 17:07:22 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-6280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis resolved CASSANDRA-6280.
---------------------------------------

    Resolution: Not A Problem

look at {{auto_snapshot}} in cassandra.yaml

> Snapshots for dropped column families management
> ------------------------------------------------
>
>                 Key: CASSANDRA-6280
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6280
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Stephen Johnson
>            Priority: Minor
>
> Currently the only option for removing snapshots of dropped column families is to delete
them manually from the file system.  We have a user that creates column families dynamically
and deletes them when they are no longer needed.  The result is snapshots of these tables
build up quickly and disk space can only be reclaimed when they are manually deleted.
> A potential solution for this might be to add a flag to the nodetool clearsnaphot command
that removes snapshots that no longer exist in the keyspace because they have been dropped.
> Another possibility might be to add a flag on cql delete query that ignores the auto_snapshot
in the cassandra.yaml and does not create a snapshot for the deleted column family or keyspace.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message