Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DC3541091C for ; Wed, 26 Feb 2014 15:59:11 +0000 (UTC) Received: (qmail 81978 invoked by uid 500); 26 Feb 2014 15:59:08 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 81932 invoked by uid 500); 26 Feb 2014 15:59:07 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 81922 invoked by uid 99); 26 Feb 2014 15:59:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Feb 2014 15:59:06 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of doanduyhai@gmail.com designates 209.85.219.54 as permitted sender) Received: from [209.85.219.54] (HELO mail-oa0-f54.google.com) (209.85.219.54) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Feb 2014 15:59:01 +0000 Received: by mail-oa0-f54.google.com with SMTP id n16so1040816oag.27 for ; Wed, 26 Feb 2014 07:58:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=OPY9goKZebtqYCZRkpiR0Xx5oLEJL3b1R+gnx3whK8c=; b=R9DoIs+hBYPFNZ7asHy4rJ3bF1ep0cF+4LuC1JgWsoZbS/brtVGfh99h3waFF2vkW/ q6Ekobi20uDRVZecAOPhUlbwZFlHnV3/RA6W7WN04VQu+tR+lZ0AYJg0oWrPpzYIhBmZ jnu14Pt8kUxQU75DZ5iexyuw4BB2445m6symoyblvaATkZQQmIzTPRF6a18phALQX6GR FxCGBPs0ZNkNjoBJ5XpTkb/mE1HpLnJ0dNYzbLs46H0P4/j8jaVac6OeCjSmG9ciSEUa 26EamRPMRmkw2+nd8SnhUmPiV5dDYwBpoBDkAWLYkQx+F6titvFq3TkW1bytPf4+pV3K RdAg== MIME-Version: 1.0 X-Received: by 10.182.233.228 with SMTP id tz4mr2788180obc.56.1393430320315; Wed, 26 Feb 2014 07:58:40 -0800 (PST) Received: by 10.76.122.48 with HTTP; Wed, 26 Feb 2014 07:58:40 -0800 (PST) In-Reply-To: References: Date: Wed, 26 Feb 2014 16:58:40 +0100 Message-ID: Subject: Re: Flushing after dropping a column family From: DuyHai Doan To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=001a11c3060043024404f351474f X-Virus-Checked: Checked by ClamAV on apache.org --001a11c3060043024404f351474f Content-Type: text/plain; charset=ISO-8859-1 Try truncate foo instead of drop table foo. About the nodetool clearsnapshot, I've experienced the same behavior also before. Snapshots cleaning is not immediate On Wed, Feb 26, 2014 at 4:53 PM, Ben Hood <0x6e6562@gmail.com> wrote: > On Wed, Feb 26, 2014 at 3:17 PM, DuyHai Doan wrote: > > "I'm noticing that using either TRUNCATE or DROP/CREATE in cqlsh appear > to > > leave the underlying data behind." > > > > --> What do you mean by "underlying data" ? Are you talking about > > "snapshots" ? > > I was referring to all of the state related to the particular column > family I want to set fire to, be it snapshots, parts of commit logs, > sstables, key caches, row caches, or anything else on or off disk that > relates to said column family. > > > If yes, you can wipe them using nodetool clearsnapshots command > > This is what I'm doing: > > cqlsh:bar> drop table foo; > > $ nodetool clearsnapshot bar > Requested clearing snapshot for: bar > > cqlsh:bar> create table foo (....); > cqlsh:bar> select * from foo limit 1; > > This returns nothing (as you would expect). > > But this if I re-run this again after about a minute, the data is back. > > I get the same behavior if I use nodetool cleanup, flush, compact or > repair. > > It's as if there is either a background app process filling the table > up again or if the deletion hasn't taken place. > --001a11c3060043024404f351474f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Try truncate=A0foo instead of drop table foo.
=
About the nodetool clearsnapshot, I've experienced= the same behavior also before. Snapshots cleaning is not immediate=A0


On Wed,= Feb 26, 2014 at 4:53 PM, Ben Hood <0x6e6562@gmail.com> wro= te:
On Wed, Feb 26, 2014 at 3:17= PM, DuyHai Doan <doanduyhai@gma= il.com> wrote:
> "I'm noticing that using either TRUNCATE or DROP/CREATE in cq= lsh appear to
> leave the underlying data behind."
>
> =A0--> What do you mean by "underlying data" ? Are you ta= lking about
> "snapshots" ?

I was referring to all of the state related to the particular column<= br> family I want to set fire to, be it snapshots, parts of commit logs,
sstables, key caches, row caches, or anything else on or off disk that
relates to said column family.

> If yes, you can wipe them using nodetool clearsnapshots command

This is what I'm doing:

cqlsh:bar> drop table foo;

$ nodetool clearsnapshot bar
Requested clearing snapshot for: bar

cqlsh:bar> create table foo (....);
cqlsh:bar> select * from foo limit 1;

This returns nothing (as you would expect).

But this if I re-run this again after about a minute, the data is back.

I get the same behavior if I use nodetool cleanup, flush, compact or repair= .

It's as if there is either a background app process filling the table up again or if the deletion hasn't taken place.

--001a11c3060043024404f351474f--