Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E0C0D10494 for ; Thu, 31 Oct 2013 17:07:31 +0000 (UTC) Received: (qmail 20933 invoked by uid 500); 31 Oct 2013 17:07:31 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 20657 invoked by uid 500); 31 Oct 2013 17:07:25 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 20526 invoked by uid 99); 31 Oct 2013 17:07:22 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Oct 2013 17:07:22 +0000 Date: Thu, 31 Oct 2013 17:07:22 +0000 (UTC) From: "Jonathan Ellis (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (CASSANDRA-6280) Snapshots for dropped column families management MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)