From user-return-37924-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Sun Dec 8 19:40:51 2013 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 344CF10F93 for ; Sun, 8 Dec 2013 19:40:51 +0000 (UTC) Received: (qmail 33382 invoked by uid 500); 8 Dec 2013 19:40:48 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 33318 invoked by uid 500); 8 Dec 2013 19:40:48 -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 33310 invoked by uid 99); 8 Dec 2013 19:40:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 08 Dec 2013 19:40:48 +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 (nike.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [209.85.160.41] (HELO mail-pb0-f41.google.com) (209.85.160.41) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 08 Dec 2013 19:40:42 +0000 Received: by mail-pb0-f41.google.com with SMTP id jt11so4069816pbb.28 for ; Sun, 08 Dec 2013 11:40:20 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:message-id:mime-version :subject:date:references:to:in-reply-to; bh=UmF2ymaSbL06aHaDUn8ougg1T5oPl4XjI7/f2OrNVmc=; b=Cwse+Nv5AGTSCrYr328Z5HBPGU0weIu1hoGoEFy9d+6H7mUr5HLPeEvPpu6aQkia8F MnbgXlF57adyCgHwC6r2S/RLtm6BCZNpRZiKVv2GMtmRXoQSb3S8xVs9hRgnRfUw/FdU uUeR+kkqmUylcDDXUjxqmLE4VU4AgN8y4DsS+Gbm6SmrwQAL09mdNO/BKl9ded7VTZmi 1KcMx9F7qD0H/FxbbjLlklotL+lUGlMRoSHG+I/Rf647wklo8tQnQcrKlfGwIbl8SGhv 6XSqmBdiwVq5eiUptXAEn3ujNr3dHz6L/QcjI+3CL+XNTgK6mizXvE33nwAmiSA55BLc X2Og== X-Gm-Message-State: ALoCoQkVwpZxt5G79r3SVtbkBdCNH6ov8SsywvC9zzxD8SJR5DLqb9W8PRTWXzKkLs0MhSoC5Wij X-Received: by 10.66.146.199 with SMTP id te7mr16844202pab.106.1386531620351; Sun, 08 Dec 2013 11:40:20 -0800 (PST) Received: from [172.16.1.18] ([203.86.207.101]) by mx.google.com with ESMTPSA id er3sm12656501pbb.40.2013.12.08.11.40.18 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 08 Dec 2013 11:40:19 -0800 (PST) From: Aaron Morton Content-Type: multipart/alternative; boundary="Apple-Mail=_D0575DE2-6294-483C-8735-B929EA78627E" Message-Id: <2EB67F4B-43C1-418D-870D-156B32ECD178@thelastpickle.com> Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\)) Subject: Re: Commitlog replay makes dropped and recreated keyspace and column family rows reappear Date: Mon, 9 Dec 2013 08:40:16 +1300 References: To: Cassandra User In-Reply-To: X-Mailer: Apple Mail (2.1822) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_D0575DE2-6294-483C-8735-B929EA78627E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Do you have the logs from after the restart ?=20 Did it include a "Drop Keyspace=85=94 INFO level message ?=20 Cheers ----------------- Aaron Morton New Zealand @aaronmorton Co-Founder & Principal Consultant Apache Cassandra Consulting http://www.thelastpickle.com On 4/12/2013, at 2:44 am, Desimpel, Ignace = wrote: > Hi, > =20 > I have the impression that there is an issue with dropping a keyspace = and then recreating the keyspace (and column families), combined with a = restart of the database > =20 > My test goes as follows: > =20 > Create keyspace K and column families C. > Insert rows X0 column family C0 > Query for X0 : found rows : OK > Drop keyspace K > Query for X0 : found no rows : OK > =20 > Create keyspace K and column families C. > Insert rows X1 column family C1 > Query for X0 : not found : OK > Query for X1 : found : OK > =20 > Stop the Cassandra database > Start the Cassandra database > Query for X1 : found : OK > Query for X0 : found : NOT OK ! > =20 > Did someone tested this scenario? > =20 > Using : CASSANDRA VERSION 2.02, thrift, java 1.7.x, centos > =20 > Ignace Desimpel --Apple-Mail=_D0575DE2-6294-483C-8735-B929EA78627E Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252
Do you have the logs from after the restart = ? 
Did it include a "Drop Keyspace=85=94 INFO level = message = ? 

Cheers


http://www.thelastpickle.com

On 4/12/2013, at 2:44 am, Desimpel, Ignace <Ignace.Desimpel@nuance.com&= gt; wrote:

Hi,
 
I have the = impression that there is an issue with dropping a keyspace and then = recreating the keyspace (and column families), combined with a restart = of the database
 
My test = goes as follows:
 
Create = keyspace K and column families C.
Insert rows X0 column family  C0
Query for X0 : found rows : = OK
Drop keyspace = K
Query for X0 : found no rows : = OK
 
Create keyspace K and column families = C.
Insert rows X1 column family =  C1
Query for X0 : not = found : OK
Query for X1 : found = : OK
 
Stop the Cassandra database
Start the Cassandra database
Query for X1 : found : OK
Query for X0 : found : NOT OK = !
 
Did someone tested this = scenario?
 
Using : = CASSANDRA VERSION 2.02, thrift, java 1.7.x, centos
 
Ignace = Desimpel

= --Apple-Mail=_D0575DE2-6294-483C-8735-B929EA78627E--